Site Migration SEO — Move a Site Without Losing Rankings
Learn how to handle site migration SEO correctly and protect your rankings. A complete checklist covering redirects, crawl validation, and post-migration monit
What this lesson covers
This lesson teaches you Site Migration SEO — Move a Site Without Losing Rankings — a critical skill in your Advanced SEO toolkit. Every concept here has been validated against real-world SEO campaigns and directly impacts organic traffic and rankings.
By the end of this lesson you will have a clear understanding of the concept and at least one concrete action you can take on your own website today.
Understanding and correctly applying site migration seo — move a site without losing rankings is one of the highest-leverage activities in Advanced SEO. Sites that get this right consistently outperform those that ignore it.
A full crawl of all indexed URLs using Screaming Frog or a similar crawler
All pages in Google's index, exported from Google Search Console via the Coverage report
Your current rankings for all tracked keywords, exported from your rank tracking tool
Your current organic traffic levels by page, from Google Analytics 4
Your top linked pages and their referring domain counts, from Ahrefs or Semrush
Any existing crawl errors, redirect chains, or duplicate content issues to address during migration
Every URL that changes must have a corresponding 301 redirect — no exceptions
Redirects should be direct single-hop — old URL points directly to new URL with no intermediate redirects
If a page is being consolidated or removed, redirect to the most topically relevant page on the new site, not to the homepage
Do not redirect all 404s to the homepage — this is a soft 404 in Google's eyes and passes no link equity
Crawl the staging site with Screaming Frog and confirm all redirects are resolving correctly to their intended destinations
Check that no old URLs are returning 200 responses (they should redirect, not load)
Confirm that the new site's robots.txt is not blocking any important content
Verify that your XML sitemap contains only new URLs and no old ones
Test your canonical tags to ensure no self-referencing canonical issues
Check all pages on mobile — every redirect and every page must render correctly on mobile devices
Implement all 301 redirects at the server or CDN level before changing any DNS settings
Update your XML sitemap to reflect all new URLs and resubmit it in Google Search Console
Update your robots.txt to allow crawling of the new site structure
If changing domains, add and verify the new domain as a property in Google Search Console and use the Change of Address tool to notify Google
Submit your top 50 highest-priority new URLs for indexing via Google Search Console's URL Inspection tool
Update your Google Analytics 4 tracking to correctly attribute traffic to the new domain or URL structure
Check Google Search Console for crawl errors, coverage issues, and any new manual actions every 24 hours for the first week
Monitor your rank tracking tool daily for any keywords showing significant position drops
Check organic traffic in Google Analytics 4 against your pre-migration baseline
Review the redirect report in Screaming Frog to confirm all redirects are resolving correctly on the live site
- .
What Is Site Migration SEO?
Site migration SEO refers to the process of managing the SEO implications of moving a website — whether that means changing your domain name, switching CMS platforms, restructuring your URL architecture, moving from HTTP to HTTPS, or a combination of all four. Each of these changes affects how Google finds, crawls, and evaluates your pages, and each carries the risk of ranking loss if not handled with a systematic, pre-planned approach.
The fundamental SEO challenge with any migration is that your organic rankings are attached to specific URLs. Every link pointing to your site points to a specific URL. Every piece of PageRank and domain authority your site has accumulated is distributed across your existing URL structure. When those URLs change, all of that value needs to be carefully redirected to the new equivalents — or it is lost.
Site migrations fail when they are treated as a purely technical task handed off to developers without SEO oversight. They succeed when SEO requirements are built into the migration plan from day one, with a pre-migration audit, a redirect map, post-migration validation, and a monitoring period that catches and fixes problems before they cause permanent damage.
🔑 Key Concept
The most common cause of catastrophic ranking loss in site migrations is not the migration type — it is the absence of a complete, tested redirect map before the migration goes live. Every URL that changes must have a corresponding 301 redirect pointing from the old URL to its exact equivalent on the new site. A migration that goes live with hundreds of unmapped URLs is a migration that destroys SEO equity. Plan the redirect map first, execute second.
Why Site Migrations Are High-Risk for SEO
To understand why site migrations carry such significant SEO risk, it helps to understand how Google stores and updates information about your site.
Google builds a model of your site over months and years of crawling — indexing your pages, evaluating your content, recording your backlinks, and assigning ranking signals to specific URLs. When you migrate your site, you are asking Google to update its entire model of your domain simultaneously. This is a complex, time-consuming process for Google's crawlers, and anything that prevents them from correctly mapping old URLs to new ones interrupts the transfer of the accumulated signals.
The three most common failure points in site migrations are:
Missing or incorrect redirects — Old URLs that return 404 errors instead of redirecting to their new equivalent lose all their link equity and ranking signals permanently. Visitors following old links land on error pages. Google removes the old URLs from its index without passing their authority to any new page.
Redirect chains — A redirects to B, which redirects to C, which redirects to D. Each hop in a redirect chain loses a small amount of link equity and slows down crawling. Chains of three or more hops are a significant equity drain and should be resolved to single-hop redirects during migration.
Crawl budget waste — If your new site has thousands of broken links, duplicate pages, or unnecessary redirect chains, Google's crawlers waste their crawl budget on low-value pages and may not reach your most important content in a timely fashion.
The Core Principles of Site Migration SEO
Principle 1: Plan Before You Build
Every site migration that preserves rankings shares one characteristic: the SEO plan was created before the new site was built, not after it was launched. URL structure decisions, redirect maps, and canonical tag strategies must be made during the design phase — not retroactively applied to a site that is already live.
Principle 2: Map Every URL, Without Exception
A redirect map is a document matching every existing URL on your current site to its exact equivalent on the new site. It is the single most important deliverable in any site migration project. No URL should go live as a changed address without a corresponding redirect in this map.
For large sites with thousands of pages, automated tools can assist with mapping — but every high-traffic and high-authority page must be manually verified.
Principle 3: Test in Staging Before Going Live
Every redirect, every canonical tag, every robots.txt directive, and every sitemap should be tested in a staging environment before the migration goes live. Problems caught in staging take minutes to fix. The same problems caught after go-live can take weeks to resolve while traffic drops.
Principle 4: Go Live and Monitor Immediately
Migration day is not the end of the process — it is the beginning of the monitoring period. Set up immediate post-migration tracking so that any crawl errors, redirect failures, or indexing problems are caught within hours, not days.
Principle 5: Give Google Time, But Investigate Quickly
Some temporary ranking fluctuation is normal in the weeks following a migration as Google processes the changes. However, sharp sustained traffic drops within the first two weeks are a signal of a systematic problem — usually missing redirects or crawl errors — that requires immediate investigation, not patient waiting.
✅ Pro Approach
The best way to prepare for a site migration is to run a complete crawl of your current site before any work begins. Use Screaming Frog or a similar tool to export every URL, response code, and inbound link on your existing site. This becomes your pre-migration baseline and the foundation of your redirect map. No migration should begin without this crawl in hand.
Step-by-Step Site Migration SEO Implementation
Step 1: Pre-Migration Audit — Document Your Baseline
Before any development work begins, run a complete audit of your current site. This establishes the baseline you will use to verify that the migration has not damaged your SEO performance.
Your pre-migration audit should capture:
Document every metric with the date. This baseline is your before snapshot — everything post-migration is compared against it.
Step 2: Build Your Complete Redirect Map
Using your full URL list from the pre-migration audit, create a redirect map that matches every existing URL to its new equivalent. For a domain change, this means mapping olddomain.com/page to newdomain.com/page. For a URL restructure, this means mapping every old URL pattern to its new equivalent path.
Rules for a complete redirect map:
For large sites, sort your URL list by organic traffic and inbound link count before mapping. Pages with the most traffic and the most backlinks are your highest-priority redirects — any errors here have the greatest impact on rankings.
Step 3: Update Internal Links
Once the redirect map is complete, update all internal links on the new site to point directly to the new URLs — not through redirects. Internal links that go through redirects waste crawl budget and dilute PageRank transfer. Your new site should have no internal links pointing to old URLs on launch day.
Step 4: Test Everything in Staging
Before the migration goes live, conduct a full technical test in your staging environment:
Document all test results before approving the migration for go-live.
Step 5: Implement the Migration
On migration day, execute the following sequence in order:
Step 6: Post-Migration Monitoring
The 30 days following go-live are the critical monitoring period. Set up daily checks for the first two weeks:
Any sustained drop in rankings or traffic beyond what is expected from temporary fluctuation requires immediate investigation. The most common post-migration fixes are correcting missed redirects, resolving redirect chains, and fixing canonicalization errors introduced during development.
Step 7: Measure and Iterate
At 30 days, 60 days, and 90 days post-migration, run a formal comparison of your post-migration metrics against your pre-migration baseline. Rankings, organic traffic by page, referring domain counts, and crawl error rates should all be tracked over this period.
A successful migration shows traffic and rankings returning to — and eventually exceeding — pre-migration levels as Google fully processes the new site structure. If metrics have not recovered to baseline within 90 days, a deeper audit is warranted to identify residual redirect or canonicalization issues.
Common Mistakes to Avoid
Launching without a complete redirect map — The single most damaging migration mistake. Any URL that changes without a corresponding redirect becomes a permanent traffic and equity leak. Build the map before you build the new site.
Redirecting everything to the homepage — Using the homepage as a catch-all redirect for old or deleted URLs is a well-known soft 404 pattern that Google ignores. Every redirect must point to a genuinely relevant destination page.
Implementing without measuring — Always document your pre-migration baseline before making any changes. Without it, you cannot distinguish normal migration fluctuation from a serious problem that needs fixing.
Making too many simultaneous changes — Migrating your domain, restructuring URLs, and switching CMS platforms simultaneously creates so many variables that diagnosing problems post-migration becomes extremely difficult. Where possible, stage major changes separately.
Optimising for metrics instead of users — Every URL structure and redirect decision should ultimately make the website better for real visitors, not just cleaner for algorithm signals. Navigation that makes sense to users typically makes sense to Google too.
Ignoring mobile — Google indexes the mobile version of your site first. Every redirect, every page, and every element of your new site must work correctly on mobile devices before go-live. Mobile-specific issues discovered post-migration are significantly harder and slower to fix.