A website redesign or replatform is one of the most valuable investments a business can make — and one of the riskiest moments for its search visibility.
Handled well, a rebuild can improve your rankings. Handled badly, it can erase years of hard-won organic traffic in a single afternoon, often without anyone noticing until the enquiries quietly dry up weeks later.
The frustrating part is that the ranking losses are almost always avoidable. They rarely come from the new design itself. They come from the technical foundations that break underneath it during the move — and from nobody being responsible for protecting them.
This guide explains why migrations lose rankings, and gives you a step-by-step SEO migration checklist to protect your traffic before, during and after launch — whether you are refreshing an existing site, rebuilding it from scratch, or moving to an entirely new CMS.
Can you redesign a website without losing SEO rankings?
Yes. You can redesign or replatform a website without losing SEO rankings, provided the migration is planned properly. The main risks are broken URLs, missing redirects, removed content and a changed site structure. You protect your rankings by benchmarking current performance, mapping every old URL to its new equivalent, preserving your best content and metadata, and putting 301 redirects in place before the new site goes live.
The rest of this guide walks through exactly how to do that.
Why website migrations lose rankings
Most ranking drops after a redesign are not caused by the design. They are caused by what quietly changes beneath it.
When you rebuild a site, you are often changing its URLs, its content, its structure and its underlying technology all at once. Each of those is a signal Google uses to rank you, and each one can break during a move. Here are the causes we see most often.
URLs change and the old ones aren't redirected. This is the single biggest cause of lost traffic. When a page's address changes and the old address isn't redirected to the new one, Google's index still points at a page that no longer exists. The visitor hits a 404, and all the authority that page had built is lost.
Content is removed or trimmed. A redesign is often treated as a chance to "tidy up" and cut wording. But the text on a page is frequently the very thing that ranked it. Strip it out and you strip out the rankings with it.
Site structure and internal linking change. Your navigation, page hierarchy and internal links tell Google which pages matter and how they relate. Rebuild the structure without preserving those signals and Google effectively has to relearn your site from scratch.
Metadata is regenerated or lost. Page titles and meta descriptions that earned clicks over years can be silently overwritten by a new template's defaults during a rebuild.
Technical performance regresses. A new site that loads more slowly, handles mobile worse, or is harder for Google to crawl will rank lower — however good it looks.
The staging site gets indexed. If the in-development version of the site is left open to Google, it can be crawled and indexed, creating duplicate content that competes with your live pages and confuses Google about which version to rank.
In our experience, the businesses that lose rankings after a migration almost never lose them for one dramatic reason. They lose them to several small oversights that add up — each one preventable with the right checklist.
The website migration SEO checklist
Protecting your rankings through a migration comes down to preparation. The work that saves your traffic happens before the new site goes live — not in a panic afterwards.
Here is the process, in order.
1. Benchmark and inventory the current site
Before you change anything, capture the current state of the site so you have something to protect and something to measure against.
- Crawl the existing site and export a full list of live URLs.
- Record your current organic traffic, top-performing pages and keyword rankings in Google Search Console.
- Flag the pages that drive the most traffic and enquiries — these are the ones you protect at all costs.
Many businesses accidentally remove or change pages that were quietly driving valuable traffic, simply because nobody checked first.
2. Map every URL (the most important step)
Create a redirect map: a simple document that pairs every old URL with its new equivalent on the rebuilt site.
| Old URL | New URL | Redirect |
|---|---|---|
| /old-services-page | /new-services-page | 301 |
| /blog/old-article | /knowledge/new-article | 301 |
A few rules that make the difference between a clean migration and a messy one:
- Use 301 (permanent) redirects — they pass on the ranking authority of the old page.
- Redirect one-to-one wherever possible: each old page to its closest new match, not everything bundled to the homepage.
- Avoid redirect chains (a page that redirects to a page that redirects again) — they dilute authority and slow crawling.
- Don't leave any high-value page without a destination.
If a page is genuinely being retired with no equivalent, that's a deliberate decision to make consciously — not an accident to discover later.
3. Preserve your best-performing content
Identify the pages that currently rank and keep the content that made them rank. A rebuild is the right moment to improve content, not to quietly delete it.
If a page needs to change, evolve it rather than gut it — keep the core topic, the depth and the search intent intact.
4. Keep metadata and structured data intact
Carry over your existing page titles, meta descriptions, heading structure and any structured data. If your new CMS auto-generates these from a template, check every important page individually rather than trusting the default.
5. Protect your site structure and internal linking
Keep your URL structure and page hierarchy as close to the original as the new design allows. Where the structure genuinely has to change, make sure your internal links are rebuilt so that your most important pages still receive strong internal signals.
6. Match — or beat — the old site's technical performance
The new build should be at least as fast, as mobile-friendly and as crawlable as the site it replaces. Before launch, confirm that page speed hasn't regressed, that the site works cleanly on mobile, that your XML sitemap is updated, and that your robots file isn't accidentally blocking anything important.
For a broader view of the technical issues that commonly hold sites back, see our guide to technical SEO issues and how to fix them.
7. Keep your staging site out of Google
Your in-development site should never be publicly indexable. Protect it behind a password or an authentication layer so that search engines can't crawl and index it. An indexed staging site creates duplicate content that competes with your real pages and muddies your search presence — a surprisingly common and entirely avoidable problem.
8. Launch carefully
On the day the new site goes live, push all your redirects live at the same time, update and resubmit your XML sitemap in Search Console, and double-check that nothing in your robots file or page settings is blocking Google from crawling the new site. The moment of launch is when redirect gaps do their damage, so this is the point to be most careful.
9. Monitor closely after launch
The migration isn't finished at launch — the first few weeks are when you catch and fix anything that slipped through.
- Watch the Page Indexing report in Search Console for crawl errors and 404s.
- Track your rankings and organic traffic against the benchmark you captured in step one.
- Fix any broken links or missing redirects the moment they appear.
Small issues caught quickly rarely cause lasting damage. The same issues left for a month can.
How long does it take for rankings to recover after a migration?
Some short-term fluctuation is normal. After any significant migration, Google needs to recrawl and reprocess the site, and rankings often wobble for a few weeks while it does.
A well-planned migration typically settles within a few weeks, and frequently ends up performing better than the old site because the rebuild improved speed, structure and content along the way. A poorly planned one — with missing redirects and lost content — can see traffic fall and never fully recover without significant remedial work.
The difference between those two outcomes is almost entirely down to the preparation described above.
Replatforming: moving to a new CMS without losing SEO
Changing your content management system adds an extra layer of risk, because URL structures, templates and the way pages are rendered can all change at once.
The migration principles stay the same — benchmark, map, preserve, redirect, monitor — but the technical execution needs more care. It's also the right moment to choose a platform that supports SEO properly rather than fighting it.
If you're weighing up your options as part of a rebuild, these may help:
- WordPress vs Webflow — comparing two of the most common choices.
- Headless CMS vs traditional CMS — for teams considering a more flexible architecture.
- What is Concrete CMS? — for businesses evaluating it as a platform.
A replatform handled well doesn't just protect your rankings — it removes the technical limitations that were holding your old site back.
The most common and most costly — migration mistake
The single biggest reason redesigns lose rankings isn't technical incompetence. It's organisational.
In most projects, the web team designs and builds the site, and SEO — if it's considered at all — is treated as something to look at after launch. The migration then falls through the gap between the two. Redirects aren't mapped, content is trimmed without checking what ranked, and by the time anyone reviews the traffic, the damage is weeks old and hard to undo.
The fix is straightforward in principle: SEO has to be part of the build, not a phase that follows it. When the same team designs, builds and grows the site, migration planning is baked into the project from the first week — there's simply no handoff for it to fall through. That's the difference between a rebuild that costs you rankings and one that improves them.
It's also why we structure our own web development and SEO work as one joined-up process rather than two separate services.
Final thoughts
A website migration doesn't have to cost you your rankings. The businesses that come through a rebuild stronger are simply the ones that treated their existing search visibility as an asset worth protecting — and planned the move around it.
Benchmark before you touch anything. Map every URL. Preserve what ranks. Redirect everything. Watch closely afterwards. Do those five things well and a redesign becomes what it should be: a step forward for your visibility, not a gamble with it.
If you're planning a redesign or replatform and want to know what you'd be putting at risk, we offer a pre-migration SEO audit — we assess your current site, identify the pages and rankings you can't afford to lose, and map out exactly how to protect them through the rebuild.
For the bigger picture on rebuilding effectively, see our guide to website redesign services, or the signs it's time to redesign your website.
