Ground-up builds
I build websites the way an SEO thinks: search first, then design, then code.
Customers ask Google and ChatGPT before they ask a person, and a business a search engine cannot find loses that customer to whichever competitor it did find. Every build on this page starts with the query someone actually types, not a homepage mockup. I'm Nipun Arora, building SEO-first websites since 2014, and the order below runs on every engagement, including this site's own build.
How this works
Five steps, in this order, for every ground-up build
Search research happens first because it decides everything downstream: what the site's pages are even about, and in what order a visitor reaches them. Design and code follow the structure that research produces, not the other way around.
Search research before wireframes. Every build starts with the same research an audit runs: what people actually search for, what already ranks for it, and which page on the new site should own which query. A wireframe drawn before that research exists gets redrawn later, at your expense.
Site structure built from that research. The pages that exist, how they link, and what each one owns get set from step one's findings, not from a generic five-page template. A structure built around search intent survives a redesign. A structure copied from a template fights the next one.
Entities and schema from day one. Person, Organization, Service, and FAQ schema get written into the build from the first commit, not bolted on before launch. A site that describes itself correctly to a crawler from day one skips the schema retrofit a later migration has to pay for.
Design and code inside that structure. Visual design and the actual code get built inside the structure steps one and two already set. A design decision never quietly breaks a URL or flattens a heading hierarchy the research called for.
A measurement published at launch. Every build ships with a baseline: what's indexed, what ranks, what Core Web Vitals score, before a customer ever sees the site. The same questions get asked again after launch, and the answer gets written down whether it flatters the build or not.
Who this is for
Four situations that lead to a ground-up build
A ground-up build fits a business that needs a site to exist, to replace one that never worked for search, or to finally start pulling its weight in AI answers.
You're building a first real site, or leaving a website builder that never once touched a search ranking. SEO decisions get made before a single page exists, not stapled on after launch.
Your company is funded and wants to rank, including inside ChatGPT and Google AI Mode, not just the ten blue links. Search research and AI-answer visibility get planned into the same build instead of split across two separate hires.
Your current site works, mostly, but a redesign feels too risky to hand to a developer who has never run a migration through a ranking check. That specific job has its own page: Website Migration SEO Services.
Your current site is past the point an audit can fix: years of plugin damage, structural SEO debt, and no realistic patch. A full rebuild is the only real option left. A small number of rebuilds for already-earning businesses run as a revenue-share arrangement instead of a fee, decided case by case against four criteria: Growth Partnerships.
Choosing who leads a ground-up build matters as much as the platform: see who should build your website when SEO matters for the criteria. If Dubai is the specific market you're hiring for, start at SEO consultant in Dubai instead.
Send your domain and I'll scope the build.
Start a buildProof, not a promise
The build that already proves the method: this site
This site is itself a ground-up SEO-first build: Astro, JSON-LD written from the first commit, Core Web Vitals measured before launch. Two of the four public open-source projects extend the same discipline into shipped software you can inspect yourself. Client work is published the same way: BookMySafari and Saramis Global are two named, consented ground-up builds, alongside an anonymized recovery; every result is dated, and a client's name appears only once that client has cleared it.
- cool-astro-forms
- MIT, v0.1.11, 11 releases on npm.
- semantic-seo-geek
- Apache 2.0, v1.0.0, 1 release.
What's missing in the market
Why one person does search and code
A developer who treats SEO as an afterthought ships a site that looks right and ranks wrong. An SEO consultant who doesn't build hands the actual construction to someone they don't control. Search Engine Journal's Rachel Costello named the cost of that gap directly: "We are currently wasting a lot of time and costing businesses a lot of money through this lack of communication between SEO and development teams." Google's own John Mueller has told SEOs plainly to go talk to their developers in person, years before this was written and still true today.
Even the strongest personal-brand technical SEO practitioners stop at the same line. Patrick Stox runs one of the most credentialed independent SEO practices online, with testimonials from Ahrefs and IBM and a service menu covering audits, migrations, and AI search consulting. No line on that menu is "I will build your website." That's the open lane this page occupies.
The other end of that market is priced by the package, not the specialist: providers in the seo web design category advertise flat-fee bundles instead of a scoped engagement. This page isn't that. Search research, entity mapping, and a decade of shipping happen before a line of code, not as an add-on line item after one.
A ranking or a specific AI-assistant answer is outside anyone's control, mine included, so none is promised here. What's committed is the five-step order above, run in full, and a published measurement of what it produced. The full engagement process, and how this build fits next to an existing site's audit or migration, sits on the approach page and the services index.
Questions
Six questions before you start a build
What does SEO website development actually include?
Search and entity research before any wireframe, information architecture built from that research, schema written in from the first commit, then design and code inside that structure. The same five-step order runs on every build, including this one.
Should an SEO consultant or a web developer build my website?
Neither alone is the complete answer, and that gap is exactly what leaves most sites exposed: a developer who treats SEO as an afterthought and an SEO consultant who hands the build to someone else are both handing off the one decision that decides whether the finished site ranks. One person doing both, accountable for both, closes that gap.
How is this different from a generic seo web design package?
Most providers in that category sell a bundle, a developer and an SEO checklist stapled together after the fact, often priced by the package rather than the specialist. This is one person running search research first, since 2014, not a checklist applied to a finished site.
Do you do keyword research before or after the design?
Before. Wireframes get drawn from what the research finds, which pages should exist and what each one needs to rank for, not the other way around.
What do you build the site in?
Astro, the same framework this site runs on. It ships static HTML by default, which keeps Core Web Vitals fast and keeps the page crawlable without the JavaScript-rendering problems a heavier framework can introduce.
Do you take on every project that asks?
No. A build gets scoped after a conversation about your market and what's already been tried, the same intake process every engagement on this site starts with, on the contact page.
The same build order is documented on real projects, with dated numbers, in the case studies.
Send your site brief, or a description of the one you want built, and I'll scope the SEO-first build before any code gets written.
Start a build