Website Migration SEO - How to Migrate Without Losing Rankings

A website migration is one of the riskiest things you can do to your search visibility. Replatforming, redesigning, changing domains or restructuring URLs all touch the signals search engines rely on, and getting any of them wrong can wipe out traffic that took years to build. The good news is that traffic loss during a migration is almost always avoidable. It comes down to planning and discipline, not luck.

This checklist covers what to do before launch and after, so you can move your site without throwing away the SEO equity you have earned. It applies whether you are replatforming, redesigning, or consolidating multiple sites.

What counts as a migration

The word covers more than moving to a new domain. Any of these is a migration in SEO terms because they change how engines see and access your content:

• Changing platform or CMS (for example, moving to a new ecommerce platform).
• Redesigning a site in a way that changes URLs, templates or content.
• Changing domain name.
• Moving from HTTP to HTTPS, or restructuring your URL paths.
• Merging several sites into one, or splitting one into several.

The more of these you change at once, the higher the risk. Where possible, avoid stacking a redesign, a replatform and a domain change into a single release.

Before launch: plan and prepare

The bulk of the work happens before anything goes live. A rushed migration with no preparation is where rankings disappear.

Crawl and inventory the current site

You cannot preserve what you have not catalogued.

• Run a full crawl of the existing site with a tool like Screaming Frog to capture every URL, title, meta description, heading, status code and canonical.
• Export your top-performing pages from Search Console and analytics, so you know which URLs drive traffic and conversions and must be protected.
• Note pages with valuable backlinks, since these carry authority you do not want to lose.
• Record current structured data, so it can be replicated on the new site.

Map old URLs to new URLs

This is the single most important step. Every old URL needs a defined destination on the new site.

• Build a redirect map that pairs each old URL with its closest equivalent new URL.
• Map to the most relevant page, not just the homepage. Redirecting everything to the homepage is treated as a soft 404 and loses the value of the page.
• Decide deliberately what to do with retired pages. If there is a relevant replacement, redirect to it; if not, plan how to handle it rather than leaving a dead link.
• Keep the URL structure as close to the original as you reasonably can, since fewer URL changes means fewer redirects and lower risk.

Preserve on-page elements

Carry across the things engines use to understand and rank pages.

• Titles and meta descriptions for pages you are keeping.
• Headings and body content, especially on high-performing pages.
• Image alt text and file names where practical.
• Structured data, rebuilt and validated on the new templates.
• Internal linking, so the new architecture connects pages as well as or better than before.

Protect the staging site

A staging or development site must never be indexed, or you risk duplicate content and confusion.

• Block staging from search engines, typically with HTTP authentication, which is more reliable than relying on robots.txt or noindex alone.
• Double-check the staging environment is not publicly crawlable before launch.

Final pre-launch checks

• Confirm the new site allows crawling. A very common disaster is launching with a leftover Disallow: / in robots.txt or a site-wide noindex carried over from staging.
• Prepare the new XML sitemap.
• Test the redirect rules in the staging or pre-production environment so you know they fire correctly before they go live.

At launch: go live cleanly

Launch is mostly about flipping the switch in the right order and confirming the basics immediately.

• Deploy the 301 redirects. Use 301 (permanent) redirects, not 302 (temporary) ones, so authority is passed to the new URLs.
• Remove any staging-era blocks: clear the noindex, fix robots.txt to allow crawling, and remove HTTP authentication.
• Confirm the site serves correctly over HTTPS and that the certificate is valid.
• Spot-check a sample of redirects across different page types to confirm they land on the right destinations with a single 301 hop, not a chain.

After launch: monitor closely

The first few weeks after launch are when problems surface and when fast action limits damage.

Tell Google and submit sitemaps

• Submit the new XML sitemap in Search Console.
• If you changed domains, use the Change of Address tool in Search Console to signal the move.
• Make sure both old and new domains are verified in Search Console during a domain change, so you can monitor both.

Watch for errors

• Monitor the Search Console Pages and Coverage reports for spikes in 404s, redirect errors or noindexed pages.
• Recrawl the site to catch broken internal links, redirect chains and missing pages.
• Check that redirects are still resolving in a single hop, since chains slow crawling and dilute signals.

Track performance

• Compare organic traffic, rankings and indexed page counts against your pre-migration baseline.
• Expect some short-term fluctuation as engines recrawl and reindex. A temporary dip is normal; a sustained, deepening drop is a signal to investigate.
• Keep the redirects in place for the long term. Old URLs can hold backlinks and be crawled for a long time, so removing redirects too early loses that value.

Common mistakes that cost traffic

• Launching with the site blocked from crawling or set to noindex.
• Redirecting all old URLs to the homepage instead of relevant pages.
• Using temporary 302 redirects instead of permanent 301s.
• Forgetting to migrate or revalidate structured data and metadata.
• Changing too many things at once, making it impossible to diagnose what went wrong.
• Removing redirects too soon after launch.

The takeaway

A successful migration is methodical, not dramatic. Inventory everything, map every URL to a sensible destination, preserve your on-page signals, keep staging out of the index, and monitor hard once you are live. Do that and a migration becomes a routine technical project rather than a gamble with your traffic.

Migrations are high stakes and easy to get wrong under deadline pressure. If you have a replatform or redesign coming up, Control Tower can plan and oversee the SEO side so your rankings come through the other side intact.