Site Migration SEO

CMS-specific implementation guides

Operational runbooks translating this playbook onto each major CMS, including hosting edges, authoring workflows, and integration seams that typically move rankings and AI retrieval outcomes.

Prefer a CMS-wide lens before tackling another topic? Review every SEO & GEO playbook surfaced for WordPress, Shopify, Webflow, Drupal, HubSpot CMS, Contentful, or Adobe Experience Manager.

What Is Site Migration SEO?

Site migration SEO is the process of planning, executing, and monitoring changes to a website's domain, URL structure, platform, or architecture in a way that preserves — and ideally improves — organic search rankings and traffic. Migrations are among the highest-risk SEO events a site can undergo; a poorly executed migration can erase years of accumulated authority in days.

Why Migrations Are High-Risk

Search engines build trust in URLs over time. When a URL changes, that trust must be transferred via 301 redirects — and even perfect redirects cause some temporary ranking fluctuation. Compounding errors (missing redirects, broken canonicals, misconfigured robots.txt, missing structured data) compound the impact. The difference between a migration that loses 10% of traffic temporarily and one that loses 60% permanently is almost entirely in the planning and execution quality.

The Four Migration Types

• Domain migration — Moving from one domain to another (rebrands, acquisitions); highest risk
• Protocol migration — HTTP to HTTPS; lower risk if done correctly
• Platform migration — Moving CMS or e-commerce platform (WordPress to Webflow, Shopify replatform); medium-high risk
• Structural migration — Changing URL structure, consolidating subdomains, or reorganizing site architecture; medium risk

The Pre/During/Post Framework

Every migration has three phases: pre-migration planning (the most important), launch execution, and post-migration monitoring. Most migration failures stem from inadequate pre-migration planning — specifically, incomplete redirect mapping and failure to replicate all SEO signals on the new site before launch.

• Crawl the current site completely — Export every URL with its status, title, meta description, canonical, and inbound internal link count
• Pull all ranking keywords and their landing pages — Export from GSC; this is your priority list for migration quality control
• Audit all backlinks — Use Ahrefs to identify all URLs with backlinks; these must have exact redirects, not just homepage redirects
• Build a complete redirect map — Map every old URL to its new equivalent; old URL → new URL, one-to-one where possible
• Replicate all on-page SEO on the new site — Title tags, meta descriptions, H1s, canonical tags, structured data, and internal links must all transfer
• Set up the new site in a staging environment — Crawl staging with Screaming Frog; verify all SEO signals are present before go-live
• Implement all 301 redirects at launch — Deploy the complete redirect map on day one; no URL should return a 404
• Update GSC with the new domain/property — Submit the new sitemap immediately; use GSC's Change of Address tool for domain migrations
• Monitor rankings and traffic daily for 30 days — Watch GSC for crawl errors, index drops, and ranking changes; fix any redirect gaps immediately
• Check for redirect chains — Verify no old redirect now chains through a second redirect on the new site
• Incomplete redirect maps — Redirecting only the top 50 pages and letting the rest 404 is the single most common migration failure
• Launching without verifying structured data — Schema markup often breaks in platform migrations; always validate on the new platform before launch
• Forgetting to update internal links — Redirects handle external links; internal links should be updated to point directly to new URLs, not through redirects
• Going live on a Friday — Issues discovered over the weekend go unfixed for two days; always migrate mid-week
• Closing the GSC property for the old domain — Keep the old GSC property active for at least 12 months post-migration to monitor redirect performance and catch crawl errors
• Screaming Frog SEO Spider — Pre and post-migration crawl for complete URL inventory and issue detection
• Google Search Console — Change of Address tool, sitemap submission, and post-migration monitoring
• Ahrefs — Backlink audit to identify all URLs requiring exact redirects
• Sitebulb — Visual redirect chain detection and crawl depth analysis

How long does it take to recover rankings after a migration?

For a well-executed migration, most rankings stabilize within 4-8 weeks. Some fluctuation in weeks 1-3 is normal as Google processes the redirects. A migration that was well-planned and cleanly executed typically recovers to pre-migration levels within 3 months. Poorly executed migrations can take 6-12 months to recover — or never fully recover.

Do 301 redirects pass full link equity?

Google has stated that 301 redirects pass "close to" full PageRank, though there is likely a small amount of equity lost per hop. The more important factor is whether the redirect is implemented at all. A missing redirect loses 100% of the equity; a redirect in place loses a negligible amount.

Should I migrate HTTP to HTTPS at the same time as a domain migration?

No. Stacking multiple migration types multiplies the risk. If you need both a domain migration and an HTTP-to-HTTPS migration, do them separately with at least 4-6 weeks of monitoring between them. Protocol migration first, then domain migration, is the lower-risk order.

How Distilled Managed a High-Profile Domain Migration Without Traffic Loss

SEO consultancy Distilled has documented multiple site migration case studies. In one notable example, a major e-commerce retailer replatforming from a legacy CMS to a modern platform used a rigorous pre-migration process: complete crawl export, ranking keyword mapping, full redirect map covering 35,000 URLs, structured data replication audit, and a 3-week parallel running period where both sites were live (new on staging, old on production) with daily crawl comparisons. The result was one of the cleanest migrations documented — organic traffic was maintained within 5% of pre-migration levels throughout the transition and improved within 60 days as the new platform's technical improvements began having an effect.