It's a story we hear from new clients more often than any other: the business launched a beautiful new website, everyone celebrated, and six weeks later organic traffic was down forty percent. Nobody changed the marketing. Nobody was penalised. The redesign itself did the damage — because rankings aren't attached to your brand, they're attached to specific URLs, specific content, and a site structure Google has spent years learning to trust.
The good news is that ranking loss during a redesign is almost entirely preventable. It just requires treating the migration as part of the project rather than an afterthought handled the week after launch.
The same handful of mistakes cause most post-launch drops. URLs change without redirects, so years of link equity point at 404 pages. Content gets trimmed because the new design favours short, punchy sections — and the paragraphs that were actually ranking get deleted for aesthetics. New templates quietly drop title tags, meta descriptions, or schema the old site had. A JavaScript-heavy rebuild hides content the old HTML served plainly. And the classic: the staging site's noindex tag ships to production, invisibly deindexing the entire site for weeks.
Before anyone opens a design tool, capture what you're protecting. Crawl the current site to inventory every URL. Export your top pages and queries from Search Console so you know which pages earn the traffic — it's rarely the ones the redesign meeting talks about. Record Core Web Vitals as a performance baseline. Then agree, in writing, which pages must keep their URL, their content, and their internal links. A redesign brief without a "do not break" list is a traffic drop scheduled in advance.
Where URLs must change, redirect each old address to its closest new equivalent — one to one. Redirecting everything to the homepage tells Google those pages no longer exist and forfeits their equity. Where pages rank well, keep their headings and body copy substantially intact; you can restyle content without rewriting it. Rebuild internal links deliberately, because navigation changes silently reshuffle which pages your site declares important. And regenerate the XML sitemap so it reflects the new structure the day you launch.
A redesign should be a change of clothes, not a change of identity — Google needs to recognise the site it already trusts.
One special case deserves its own plan: if the redesign coincides with a domain change or a move to HTTPS-only, use Search Console's change-of-address tool and expect a longer stabilisation period. Combining a redesign, a domain move, and a content rewrite in one launch is possible — but it triples the variables when something dips, so stagger them when you can.
The first fortnight decides how the migration lands. Submit the new sitemap immediately, then crawl the live site the same day to catch broken links, redirect chains, and stray noindex tags. Watch Search Console's coverage and 404 reports daily, and compare traffic page by page against your benchmark — a healthy migration dips slightly for a week or two, then recovers. Problems fixed in days cost little; the same problems discovered in month two are expensive.
A redesign and your rankings are not in conflict — unplanned migrations and your rankings are. Benchmark what works, map every URL, preserve the content that earns your traffic, and monitor launch week like it matters, because it does. Done properly, a redesign is the rare project that leaves you with a better site and stronger search performance at the same time.
We design and rebuild websites with SEO migration baked into the process — so you launch a better site without starting from zero in search.
Talk to us