The question everyone asks wrong
Typed into a search engine, this question gets reinterpreted as a software comparison, not a hiring decision. A search for who should build a site when SEO matters most returns "best website builder for SEO" roundups, WordPress against Webflow against Wix against Squarespace, from sources including AIOSEO and Semrush, not an answer about which kind of person should lead the work. Searched as a direct question instead, "should an SEO or a developer build my website" returns Reddit threads, Quora answers, and forum debate with no single page answering it directly.
The platform comparison is not wrong on its own terms: WordPress, Wix, and Webflow really do differ in what they make easy. But the platform question and the builder question are not the same question, and answering the first one does not answer the second. A capable SEO-literate builder gets a ranking result out of nearly any of the major platforms. An uncoordinated build erases that same result on the best platform available, the evidence below names exactly how.
The evidence the gap is real
Four separate pieces of evidence converge on the same finding: a website build or redesign run without SEO review is a documented, repeatable way to lose rankings, not a rare accident.
A named business lost 97% of its organic traffic to a redesign
A redesign for the painting company Imhoff Painting replaced hundreds of blog articles and dozens of service pages with a six-page brochure site, turning every dropped page into a 404. Organic traffic fell from more than 300 visits a day to fewer than 10. The agency Hog the Web restored the lost pages, redirects, and URLs and recovered full traffic within roughly a month, with a 75% increase in recorded conversion events on top of the recovery. Their own line on it: "A redesign doesn't happen in a vacuum... A prettier website isn't much of an improvement if the pages bringing customers disappear."
Google's own spokesperson calls the divide unresolved
Search Engine Journal writer Rachel Costello named the coordination failure directly in 2019: "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," and cited Google's John Mueller urging SEOs, at a DeepCrawl webinar, to "go out and talk with developers and explain things to them in a way that makes sense." A search engine's own staff naming this as an open problem is a different order of evidence than an agency's marketing claim.
An entire agency category exists to fix this after the fact
Eight separate agencies, including WebFX, Sagapixel, Salt Agency, and Hog the Web, publish dedicated content and sell paid recovery services specifically for traffic that dropped after a redesign. A recovery sub-industry that size does not form around a rare accident. It forms around a common, repeatable failure: pages deleted, redirects missing, URLs changed, internal links lost, and content cut, the exact decisions a developer makes alone during a rebuild, without an SEO review catching them first.
The complaint reaches Google's own support forum
A thread titled "Need help - Lost Organic Traffic After Website Redesign" sits on the Google Search Central Community, a business asking Google directly for help after exactly this pattern. Its existence there, not just on a third-party agency blog with a reason to sell a fix, is its own evidence of how often this happens.
Sources: Hog the Web's case report on the Imhoff Painting recovery, Rachel Costello's 2019 Search Engine Journal report on the SEO-developer divide, and the Google Search Central Community thread on lost redesign traffic.
What an SEO-led build does differently
An SEO-led build changes the order three specific decisions get made in, not the tools used to make them.
Search research happens before wireframes, not after launch. Which pages a site needs, what each page's URL and heading structure looks like, and which existing pages already earn traffic all get decided before a designer draws a single screen, so a redesign preserves what already works instead of discovering the loss afterward.
Entities and schema markup get planned from day one. Which schema.org types apply to which page, and how the site's own facts stay consistent across every page, gets decided as part of the site's structure, not bolted on with a plugin once the build is finished.
Everything gets measured, and the measurements get published. Rankings and traffic recorded before the work starts and checked again after it ships turn a claim into a number a client can verify independently, the same discipline this practice runs on its own technical SEO audits.
The order is the whole method, stated plainly: search first, then design, then code.
What a developer-led build does well, and where it fails
A developer-led build genuinely wins on interaction polish, rendering speed, accessible markup, and code a future maintainer can actually work with, craft an SEO-only consultant rarely matches. Where it fails is narrower than "developers don't know SEO": it fails specifically at the handful of structural decisions, which pages survive, what their URLs become, whether a redirect exists, made once, early, and treated as a design or engineering choice instead of a ranking-affecting one.
Those decisions are exactly the ones the evidence above names as the repeated cause behind a redesign traffic collapse: deleted pages, changed URLs, missing redirects, altered canonical tags, lost internal links, and content cut without checking which of it was actually earning traffic. None of that requires a developer who is bad at their job. It requires nobody on the build to have flagged those specific decisions before launch.
How to evaluate any builder
Five checkable items separate a builder worth trusting with a redesign from one who only sounds confident about it, and none of the five requires SEO knowledge of your own to verify.
- Search research that happened before the first wireframe, on a real past project, not after launch as a fix.
- A stated policy for preserving URLs and redirects through a redesign, not a promise to "be careful."
- The specific schema.org types that fit your page types, named, not a generic "we add schema markup" line.
- Rankings and traffic measured before the work and kept after it, not just a claim that it went well.
- Real, checkable sites built years ago that still rank today, named, not a vague "years of experience."
Ask for evidence on each one, not an assurance. A builder who says "we're always careful with SEO" and cannot point to a stated policy, a named schema type, or a real site built years ago that still ranks has given an answer with nothing behind it to check.
Where I fit against these criteria
I wrote the five criteria above, and I run this practice through the same five, not a separate standard for myself.
Search research before wireframes and measurement kept front to back: the process itself, audit first, fixed scope agreed before anything starts, is on the how I work page.
Named schema types: which schema.org types apply to which page family, and a working JSON-LD example pulled from this site's own source, sits on the schema markup page, not asserted here as a bare claim.
Real, checkable work: three engagements are written up in full on the case studies, two named with the client's consent and one anonymized at the client's request, each result carrying the date it was true. The same discipline is public in open-source form too: four shipped, checkable projects on GitHub and npm, versioned and licensed, not a client-count claim with nothing behind it.
Consulting since 2014, in this order, search first, then design, then code: checkable against the criteria above, not a claim to take on its own.
Questions
Should an SEO or a developer build my website?
Neither title alone answers it. A build needs a developer's execution and someone who understands how structure, URLs, and content decisions affect rankings before the first wireframe gets drawn, so the real question is who leads: a developer who has studied SEO deeply, or an SEO who can also build. Either can work. What fails is a build where nobody in the room owns both halves.
Is WordPress, Wix, or Webflow better for SEO?
The platform is rarely the deciding factor. Each of the major platforms can produce a site that ranks well and a site that ranks badly, depending entirely on how it gets built: URL structure, page speed, structured data, and content decisions matter more than the software underneath them. Choosing a platform before choosing who leads the build answers the wrong question first.
Why did my traffic drop after a website redesign?
The named causes repeat across nearly every documented case: deleted pages with no redirect, changed URL structures, lost internal links, altered canonical tags, and content cut without checking which pages were actually earning traffic. Every one of these is a decision made during the build, not an accident that happens afterward, which is why the fix is reviewing those decisions before launch, not recovering from them after.
Can a developer learn enough SEO to build a site that ranks?
Yes, and some do. The evidence above does not say developers cannot learn SEO; it says a build where nobody involved has studied it deeply enough to catch a redirect, a canonical tag, or a content-pruning decision before it ships is the pattern behind nearly every documented traffic collapse. The skill is learnable. The failure happens when nobody on the build owns it.
How long does it take to recover rankings after a bad redesign?
The documented Imhoff Painting recovery took roughly a month once the missing pages, redirects, and URLs were restored, but that timeline depends on how much was actually broken and how quickly a search engine recrawls the fixed pages. A site that loses rankings from a redesign is not recovering on a fixed schedule; it is recovering once the specific technical causes are found and reversed.
What should I ask before hiring anyone to build my website?
Ask for the five things in the evaluation section above: search research from before the first wireframe, a stated URL and redirect policy, named schema types for your page types, kept rankings measurements from before and after, and real sites they built years ago that still rank. A builder who cannot answer one of the five is not disqualified on that alone, but the gap is worth naming before the contract is signed, not after the site launches.
What does an SEO-led build actually do differently from a standard build?
Three things, in order: search research happens before the first wireframe rather than after launch, entities and schema markup get planned from day one instead of added as an afterthought, and measurement is built into the process from the start so the before-and-after numbers exist to check, not just to promise.