An SEO migration strategy is the plan that keeps your rankings and organic traffic intact while you change something structural about your site, whether that is the domain, the URL structure, the platform, or the design. The heart of it is simple to state and easy to get wrong: map every old URL to its closest new location, redirect each one with a 301, then watch recovery in Google Search Console. Do that carefully and a move is a routine project. Skip a step and you can lose years of earned rankings in a weekend.
An SEO migration strategy is a documented plan that preserves search performance through a structural website change. It answers three questions in advance: what is moving, where each thing lands, and how you will confirm search engines followed the move. The plan exists because Google treats a changed URL as a new address that has to relearn its authority, so your job is to make that relearning as fast and lossless as possible.
People use the word migration for very different projects. Grouping them helps, because each type carries a different risk profile and a slightly different checklist.
| Migration type | What changes | Main SEO risk |
|---|---|---|
| Domain change | A new domain name, usually a rebrand | Highest risk: all authority must transfer to a brand-new domain |
| HTTP to HTTPS | The protocol, adding a security certificate | Mixed content and canonical or redirect loops if done loosely |
| URL structure change | New paths, folders, or slugs on the same domain | Broken internal links and unmapped old URLs |
| Platform or CMS replatform | A new system, for example moving to WordPress or Shopify | Template and URL changes plus lost on-page elements |
| Site consolidation | Merging several sites or subdomains into one | Duplicate content and many-to-one redirect decisions |
| Redesign | New templates, content, or navigation | Lost content, changed headings, and slower Core Web Vitals |
Most real projects combine two or three of these at once. A rebrand often means a new domain, a new platform, and a redesign in the same launch, which is exactly why the risk stacks up and why a written plan matters. Semrush groups migrations into a similar set of scenarios, including domain changes, platform switches, HTTP to HTTPS, and architecture restructures. Before you touch anything, it helps to know your current baseline, and a full SEO audit checklist is the fastest way to document what you have today.
A short-term dip is normal, but permanent loss is a choice you make through poor execution. Google states plainly that with any significant change to a site you may see ranking fluctuations while it recrawls and reindexes your pages. That volatility usually settles. The migrations that never recover are the ones with broken redirects, unmapped URLs, or content that quietly disappeared in the move.
The data on how long recovery takes is sobering, and it is the strongest argument for planning carefully. SALT.agency analyzed 1,052 domain migrations and found that only 22.8% recovered their previous organic traffic within 90 days. The median recovery took 304 days, and 13.9% of the sites in the study had still not fully recovered after three years.
That number is not a reason to avoid migrating. Sites move for good reasons: a rebrand, a faster platform, a cleaner architecture. The point is that the outcome depends almost entirely on preparation, and the biggest preparation gap is always redirects. If your goal is to move without the traffic hole, treat the phases below as non-negotiable rather than nice-to-have.
A clean SEO migration runs through six phases: a pre-migration audit and benchmark, URL mapping, the 301 redirect build, a staging crawl and QA, the launch-day switch, and post-launch monitoring in Search Console. Each phase has a clear exit condition, and you should not start the next one until the current one is signed off. Rushing the order is how important pages slip through unmapped.
Here is what each phase actually involves.
If any phase feels heavy for your team, a structured complete SEO site audit before you migrate will surface the pages, redirects, and technical issues that most often break a move.
Redirect mapping is the biggest risk because it is the one step that permanently transfers or destroys your earned authority. Every old URL that ranked, held backlinks, or received internal links needs a 301 to its closest equivalent on the new site. Miss an important page and the ranking signals it accumulated have nowhere to go, so they are simply lost. This is the difference between a migration that dips for a few weeks and one that never comes back.
Two rules from Google shape how you build the map. First, use permanent redirects: Google recommends server-side permanent redirects such as 301 and 308, because they tell search engines the move is permanent and pass ranking signals along. Second, keep them live: Google's John Mueller advises leaving migration redirects in place for at least one year, because Google's systems need to see the redirect several times before they record the change permanently.
Beyond the redirect type, a few practices keep the map clean and the equity flowing. Use them as a working standard while you build the spreadsheet.
| Best practice | Why it matters |
|---|---|
| Redirect one-to-one where possible | Point each old URL at the single most relevant new page, not a blanket redirect to the homepage, which Google can treat as a soft 404 |
| Prioritise by value | Map your highest-traffic and most-linked URLs first so the pages that matter most are never left unmapped |
| Avoid redirect chains | A redirect should hit its final destination in one hop; chains waste crawl budget and dilute signals |
| Redirect to the canonical URL | Always send traffic to the final, canonical version so you are not redirecting into another redirect or a non-preferred URL |
| Keep 301s for at least a year | Google needs repeated visits to record the move permanently, per John Mueller |
| Update internal links, do not rely on redirects | Change on-site links to point at the new URLs directly, so crawlers and users skip the redirect entirely |
Redirect mapping sits inside the broader world of technical SEO, and if the distinction between the on-page and the technical side is fuzzy, our explainer on on-page SEO vs technical SEO puts each in context.
Launch day is where the plan meets reality, and a tight checklist stops small oversights from becoming ranking losses. Work through these in order once the new site goes live.
If Search Console starts flagging problems in the days after launch, our guide on how to fix Google Search Console errors walks through the coverage and indexing issues that surface most often after a move.
You monitor a migration by watching Search Console for the crawl, indexing, and ranking signals that confirm Google is following your redirects. The Page indexing report is the primary tool: Google says it will reflect the move as a drop in indexed URLs on the old site and a matching rise on the new one. If the new URLs are not getting indexed, or the old ones are not dropping out, your redirects are the first place to look.
In the first few weeks, check these signals daily and act on anything unexpected:
Old URLs that no longer belong on the new site sometimes cling to the index for weeks. If a removed URL keeps appearing and you need it gone quickly, our walkthrough on how to remove a URL from Google Search Console covers the removal tool and when to use it.
Google says a small to medium-sized site can take a few weeks for most pages to move, with rankings fluctuating and then settling over the following months as it recrawls and reindexes. That is the optimistic, well-executed case. The independent data is slower: SALT.agency's study of 1,052 domain migrations put the median full recovery at 304 days, with only 22.8% back to baseline inside 90 days. Even a clean migration commonly sees a temporary performance dip in the first weeks.
What separates the fast recoveries from the slow ones is almost always execution quality, not luck. Complete redirect coverage, a one-hop redirect path, unchanged or improved content, and quick fixes to crawl errors pull recovery toward the fast end. Missing redirects, thin or deleted content, and slow templates push it toward the long tail. Set the expectation with stakeholders early: plan for a dip, budget several months for full recovery, and keep the redirects live for at least a year so Google can finish transferring signals. The teams that treat recovery as a monitored phase, not a launch-day finish line, are the ones that come back fastest.
What is an SEO migration strategy? It is the plan that keeps your search rankings and organic traffic intact while you change something structural about your site, such as the domain, the URL structure, the platform, or the design. The core of it is mapping every old URL to its new location with a 301 redirect, then monitoring recovery in Search Console.
Do I really lose traffic during a site migration? A temporary dip is normal even on a clean migration. Google says ranking fluctuations happen while it recrawls and reindexes the new URLs. The lasting damage comes from mistakes, mainly broken or missing redirects, not from the move itself.
Should I use 301 or 302 redirects for a migration? Use 301 permanent redirects. Google recommends server-side permanent redirects such as 301 and 308 for a site move, because they tell search engines the change is permanent and pass ranking signals to the new URL. A 302 signals a temporary move and can stall that transfer.
How long should I keep 301 redirects in place after a migration? At least one year. Google's John Mueller advises keeping migration redirects live for a minimum of one year, because Google's systems need to see the redirect several times before they permanently record the move and transfer signals to the new URL.
How long does traffic take to recover after a migration? Google says a small to medium site can take a few weeks for most pages to move, with rankings settling over the following months. Real-world data is slower: SALT.agency studied 1,052 domain migrations and found the median recovery took 304 days, and only 22.8% recovered within 90 days.
Do I need the Change of Address tool in Search Console? Yes, for a domain change. Google says to submit a Change of Address in Search Console for the old site when you move to a new domain. It is not needed for an HTTP to HTTPS move or a URL-structure change on the same domain.
Should I migrate the whole site at once or in sections? For small and medium sites, move everything at once. Google recommends moving all URLs simultaneously rather than one section at a time, because it helps their algorithms detect the move and update the index faster. Only very large sites benefit from moving in chunks.
What is the single biggest mistake in an SEO migration? Broken or missing redirect mapping. Every old URL needs a 301 to its closest new equivalent. Miss even a handful of important pages and you lose the link equity they held, often permanently, which is why redirect mapping is the part to get right before launch.
Can I run an SEO migration myself or do I need an agency? A small, single-change migration is manageable in-house with a full crawl, a redirect map, and Search Console. A domain change, a replatform, or a site consolidation carries far more risk, and that is where experienced technical SEO help pays for itself by preventing permanent traffic loss.
Start with the baseline. Before you change a single URL, crawl your current site, export 12 months of Search Console data, and build the redirect map. Those three artifacts prevent most migration disasters on their own. From there, work the six phases in order and keep monitoring live well past launch day. If you have a move coming up and want a second set of eyes on the redirect plan before you commit, book a free audit with Rankite and we will pressure-test your migration strategy against the pages that carry your rankings.
Get a free, no-obligation SEO audit and a 30-minute strategy session. We'll show you exactly where the growth is hiding.
Fill out the form and we'll get back to you within one business day. Prefer email? Write to us directly at contact@rankite.com.
