Website Migration SEO: How to Move Sites Without Losing Rankings

Website migrations are one of the highest-risk SEO events a company can undertake. A platform migration, domain change, or structural redesign that is not executed with careful SEO planning can produce a 30–60% organic traffic decline that takes 6–18 months to recover from.

This happens consistently because migrations are driven by web development and design teams — for whom the SEO implications are secondary — on timelines that don't allow for adequate pre- and post-migration SEO work. The result is a site that looks better, performs better technically, and ranks worse.

This guide is for anyone planning a website migration who does not want that outcome.

Migration Types and Their SEO Risk Levels

Domain Change

Moving from one domain to another — either a rebrand or consolidating multiple domains — is the highest SEO risk migration type. All existing domain authority, link equity, and ranking signals are tied to the old domain. Without a comprehensive redirect strategy, this equity is lost. Domain changes require a meticulous URL-level redirect map and a minimum of six months of monitoring post-launch.

Platform Migration

Moving from one CMS or ecommerce platform to another — WordPress to Webflow, Shopify to a headless solution, custom CMS to WooCommerce — is high SEO risk if URL structures change or if the new platform handles crawlability, canonical tags, or structured data differently. Manageable with proper planning.

HTTP to HTTPS

This should be a standard migration with minimal SEO risk if executed correctly. All HTTP URLs should 301 redirect to their HTTPS equivalents. Update all internal links to HTTPS. Update your sitemap and canonical tags to HTTPS. Verify in Search Console after migration that no pages are reverting to HTTP.

Structural Redesign (Same Domain, Same Platform)

If URL structures change — categories reorganised, page slugs changed, blog moved from /news/ to /blog/ — each changed URL needs a 301 redirect. The more URLs that change, the higher the risk. Preserve as many URLs as possible; change only those where the structural benefit clearly justifies the redirect overhead.

The Pre-Migration SEO Checklist

Crawl the existing site with Screaming Frog and document all URLs, title tags, meta descriptions, H1s, canonical tags, and redirect chains.

Export your top-performing pages from Search Console (by impressions and clicks) — these pages must be preserved or redirected with special care.

Export all existing inbound links from Ahrefs or Semrush — links to URLs that change need redirects to preserve link equity.

Build a complete URL mapping document: every old URL mapped to its new equivalent URL.

Test all redirects in staging before the migration goes live.

Verify robots.txt will allow crawling on the new site — staging environments frequently have robots.txt set to block all crawlers and this is sometimes accidentally deployed to production.

Prepare an updated sitemap for immediate submission post-launch.

The Migration Launch Checklist

Verify all 301 redirects are live and returning the correct status codes

Confirm robots.txt is allowing Googlebot access to all intended pages

Submit updated sitemap in Search Console

Use Search Console's URL Inspection tool to check a sample of key pages for crawling and indexation

Verify canonical tags are correctly configured on the new site

Confirm HTTPS is working sitewide with no mixed content warnings

Check Core Web Vitals on the new site — migrations sometimes introduce performance regressions

Post-Migration Monitoring

Monitor organic traffic and rankings daily for the first two weeks post-launch. A moderate temporary dip is normal as Google re-crawls and re-indexes the site. A sharp, sustained decline signals a problem that needs immediate investigation.

Check Search Console for: spike in 404 errors (missed redirects); pages dropping out of the index; crawl errors on the new domain; and coverage report changes. Set up ranking tracking for your top 50 keywords before the migration so you have a baseline for comparison.