SEO Site Migration: Migrate Without Losing Traffic

An SEO site migration is the process of making significant changes to your website — a new domain, new URLs, a new platform, or a redesign — while preserving the organic traffic and rankings you already have. Done correctly, search visibility stays flat or improves. Done carelessly, you can lose 20–50% of your organic traffic overnight, and recovery can take well over a year.

The frustrating part is that almost none of that loss is inevitable. Migrations rarely fail because Google penalises change. They fail because someone skipped a redirect, shipped a noindex tag from staging, or launched on a Friday with no plan to monitor. This guide walks through exactly how to run an SEO site migration without tanking your traffic.

What Counts as a Site Migration

People assume “migration” means moving to a new domain. It is much broader than that. Any of these is a migration as far as search engines are concerned:

• Domain change — moving from oldbrand.com to newbrand.com
• Protocol or structure change — HTTP to HTTPS, or restructuring your URL paths
• Platform / replatforming — switching CMS or ecommerce platform (WordPress to a headless build, Magento to Shopify)
• Redesign — keeping the domain but changing templates, navigation, and on-page content
• Consolidation — merging several sites or subdomains into one

Each type carries different risk. A pure HTTPS migration is low-risk if redirects are clean. A simultaneous domain change and replatform and redesign is the highest-risk thing you can do in SEO — and people do all three at once constantly. My first recommendation on most projects is to split those changes into separate phases so you can isolate what caused any drop.

Why Migrations Lose Traffic

The data here is sobering. Industry studies suggest 60–80% of site migrations result in measurable traffic loss, only about 1 in 10 end with improved rankings, and the average recovery time across all migrations is roughly 523 days. One large UK retailer reportedly lost around £3.8 million in the first month after IT rejected the redirect recommendations during a redesign.

Across the migrations I have audited, the causes cluster into a short, predictable list:

1. Missing or broken redirects — old URLs return 404s, or redirect chains dilute equity.
2. Redirecting everything to the homepage — the single most damaging “shortcut” there is.
3. Leftover staging blocks — a noindex meta tag or Disallow: / in robots.txt shipped to production.
4. Canonical tags pointing at old URLs — telling Google the new page is a copy of a page that no longer exists.
5. Content and internal links changed at the same time — so you cannot tell what caused the drop.

Notice that none of these are about Google being hostile. They are execution failures. According to analyses of migration outcomes, the pre-launch phase accounts for roughly 60% of whether a migration succeeds — meaning most of the work, and most of the risk, lives before you flip the switch.

The SEO Site Migration Process: A Step-by-Step Framework

Here is the framework I use on every migration. Work through it in order. The phases before launch matter most.

Phase 1 — Benchmark everything (2–4 weeks before)

You cannot prove a migration was successful, or diagnose a drop, without a baseline. Before you touch anything, record:

• A full crawl of the current site (every indexable URL) using Screaming Frog or similar
• Current organic traffic, rankings, and top landing pages from Google Search Console and your analytics
• Your most valuable URLs ranked by traffic, conversions, and backlinks
• Current Core Web Vitals and indexation status — and separately, your crawl efficiency via the Crawl Stats report in Search Console

This benchmark is the reference you will compare against for the next six months. If you are unsure whether your current site is even healthy enough to migrate, a technical SEO audit first will surface problems you do not want to carry over.

Phase 2 — Build redirect mapping (the make-or-break step)

This is where migrations are won or lost. Create a one-to-one map of every valuable old URL to its closest equivalent new URL. Then implement those as 301 redirects — permanent, equity-passing.

Rules that matter:

• Map by relevance, not convenience. The new target should serve the same intent as the old page.
• Never point everything at the homepage. If a specific equivalent does not exist, redirect to the most relevant category or parent page.
• Avoid redirect chains. A → B → C leaks equity and slows crawling. Redirect A → C directly.
• Consolidate deliberately. If you are merging two thin posts, point both old URLs to the single new page.

Redirect mapping is tedious and it is the part clients most want to skip. It is also the part that determines whether you keep your rankings. Treat it as non-negotiable.

Phase 3 — Test in staging

Build and validate the new site in a staging environment that is blocked from indexing (password-protected, not just noindex — you do not want to forget to remove it). In staging, confirm:

• Redirects resolve correctly and return 301, not 302 or 404
• Canonical tags point to live, self-referencing new URLs
• Title tags, meta descriptions, headings, and structured data carried over
• Internal links point to new URLs, not redirected old ones
• The XML sitemap lists only new, indexable URLs

Phase 4 — Launch

Pick your lowest-traffic window. Avoid holidays and peak periods. Then, in this exact order:

1. Remove the staging block (noindex / robots.txt Disallow). This is item one for a reason.
2. Deploy redirects and confirm a sample return 301 live.
3. Update and submit the new XML sitemap in Search Console.
4. If changing domains, use the Search Console “Change of Address” tool.
5. Update internal links and any hardcoded references.

Phase 5 — Monitor aggressively (first 30 days)

The first 72 hours are critical, and the first month decides your recovery curve. Monitor daily: crawl errors, indexation, rankings, organic traffic, Core Web Vitals, and that redirects still resolve. Fix problems the moment they appear rather than waiting for a weekly report.

The Pre-Launch Migration Checklist

Run this checklist before you launch any SEO site migration. If you cannot tick all of these, you are not ready:

• Full crawl and traffic benchmark of the old site saved
• One-to-one 301 redirect map for every valuable URL
• No redirect chains in the map
• Canonical tags self-referencing live URLs
• noindex and robots.txt blocks removed from production build
• Title tags, metas, headings, and schema preserved or improved
• Internal links updated to new URLs
• New XML sitemap ready to submit
• Launch scheduled in a low-traffic window
• Monitoring dashboard and team availability arranged for launch week

Common Migration Mistakes I See Repeatedly

In my experience auditing post-migration drops, the same handful of errors come up again and again.

Treating redirects as an afterthought. Redirect mapping gets handed to whoever has spare time the week before launch. It deserves the most senior attention you have, weeks in advance.

Changing too much at once. A domain move, a redesign, and new content shipped together makes diagnosis impossible. Where the timeline allows, phase the changes. Migrate the platform first, optimise content later.

Forgetting backlinks. Your highest-value pages are often the ones with external links. If those URLs change and the redirects fail, you lose the link equity you spent years earning. Prioritise linked pages in your redirect map.

No rollback plan. If launch goes badly, you need to be able to revert quickly. Keep the old environment available until the new one is verified stable.

Google’s own Search Central documentation on site moves is clear that with proper redirects and a change-of-address signal, ranking recovery is the expected outcome — not the exception. The sites that suffer are the ones cutting corners on the steps above.

When to Bring in a Specialist

A small blog moving to HTTPS with clean redirects is something most competent developers can handle. A high-traffic ecommerce replatform, a domain consolidation, or anything where the site is a primary revenue channel is a different category of risk. The cost of getting it wrong — months of lost traffic and revenue — dwarfs the cost of expert oversight.

This is exactly the kind of work where SEO consulting earns its fee: not by doing the developers’ job, but by owning the redirect strategy, signing off the pre-launch checklist, and catching the one missed noindex that would otherwise deindex the site. If a migration is on your roadmap, the pricing for a scoped engagement is trivial next to the revenue a botched launch puts at risk.

A successful SEO site migration is not about luck — it is about discipline. Benchmark first, map every redirect one-to-one, test in staging, launch in a quiet window, and monitor like a hawk. Do that, and the worst case is a brief dip followed by full recovery. Skip it, and you are gambling with traffic you may never get back.

Frequently Asked Questions

How long does it take to recover after an SEO site migration?

A well-executed migration typically recovers 80–90% of its organic traffic within two to three months, with full stabilisation by month four to six. Poorly executed migrations take far longer — industry data shows an average recovery time of around 523 days, and roughly 17% of sites never fully recover. The difference is almost always redirect quality and pre-launch planning, not luck.

Do I need to redirect every single old URL?

You need to redirect every URL that has value: pages that rank, earn traffic, or have backlinks pointing at them. Map each of those one-to-one to its closest equivalent on the new site with a 301 redirect. Genuinely worthless pages — expired parameters, test URLs, duplicate thin pages — can be left to 404 or consolidated, but never redirect everything to the homepage. That tells Google the old page is gone, and you lose its equity.

Should I launch a site migration during a quiet period?

Yes. Migrate during your lowest-traffic window and avoid holidays, sale periods, and peak business cycles. Migrations cause temporary ranking volatility no matter how clean they are, so you want the smallest possible audience exposed to that volatility — and your full team available to fix issues fast in the first 72 hours.

What is the most common cause of traffic loss in a migration?

Broken or missing redirects, by a wide margin. The second most common is launching with a leftover noindex tag or robots.txt block from the staging environment, which deindexes the entire new site. Both are entirely preventable with a launch checklist that puts “remove noindex” and “verify redirects” as the first two items.

Can a site migration actually improve my SEO?

It can, but it is rare — only about 1 in 10 migrations end with better rankings than before. The ones that improve treat migration as an opportunity to fix information architecture, consolidate thin content, improve site speed, and clean up the URL structure. If you migrate without addressing the underlying problems, the best realistic outcome is breaking even.