SEO Migration Checklist: How to Move a Website Without Losing Organic Visibility

A website migration — a redesign, CMS switch, domain change, or URL restructure — is one of the highest-risk events for organic traffic, because it touches nearly everything search engines use to understand your site at once: URLs, internal links, technical signals, and sometimes content itself. Most migration traffic losses are avoidable and come from missing or incomplete redirect mapping, not from the migration itself.

Migrations don't lose traffic because moving a site is inherently risky — they lose traffic because the mapping between old and new wasn't complete.

Pre-Migration Benchmark

Before any change goes live, capture a clear baseline so you can later confirm the migration didn't cause a real problem versus normal fluctuation.

• Export current organic rankings for your priority keywords
• Export Search Console performance data (clicks, impressions, average position) for at least the prior 3 months
• Crawl the entire current site and export the full list of indexed, live URLs
• Export your current backlink profile and note which pages hold the most external links
• Record current Core Web Vitals field data as a baseline for comparison after launch

URL Inventory and Mapping

Build a complete old-URL-to-new-URL map before launch — every single indexed URL needs an intended destination, even if that destination is simply 'this page no longer exists, redirect to the closest relevant parent category.' An incomplete map is the single most common cause of migration traffic loss.

Redirect Mapping

• Use 301 (permanent) redirects for every URL that has a genuine new equivalent
• Map each old URL to its closest actual equivalent — never mass-redirect everything to the homepage, which Google treats as a weak, low-relevance signal
• Check for and eliminate redirect chains (A → B → C) — redirect A directly to C
• Test redirects before launch in a staging environment, not just spot-checked after going live

Canonicals, Robots.txt, and Sitemap

Confirm canonical tags on the new site point to the new URLs correctly (not still referencing the old domain or old URL structure), that the new robots.txt doesn't accidentally disallow crawling of the entire site (a common staging-environment leftover), and that the new XML sitemap only lists live, canonical new URLs — not a mix of old and new.

Internal Links

Update internal links across the new site to point directly to final new URLs rather than relying on redirects to catch them. Every internal link that has to pass through a redirect is a small, avoidable signal loss repeated across every page that uses it — see our guide on internal linking for the broader principles this applies to at scale.

Analytics and Search Console Transition

Add and verify the new domain or URL structure as its own property in Search Console alongside the old one during the transition window, so you can directly compare indexing and performance data across both. Update analytics tracking configuration for the new URL structure before launch, not after.

Launch Day and Post-Launch Monitoring

A Realistic Timeline

Pre-migration preparation — benchmarking, full URL inventory, and redirect mapping — typically takes longer than the migration itself, often several weeks for a mid-sized site, and that time is rarely wasted; it's what determines whether the migration goes smoothly. Expect a period of ranking volatility immediately after launch as search engines recrawl and reassess the new URLs, generally stabilizing within two to six weeks for a well-executed migration with complete redirects. A migration with significant redirect gaps can take months longer to recover, if it fully recovers at all — which is the core argument for investing properly in the mapping stage rather than treating it as a formality.

Common Mistakes

• Mass-redirecting every old URL to the homepage instead of mapping to genuine equivalents
• Forgetting to remove a staging-environment noindex tag or disallow rule at launch
• Leaving internal links pointing to old URLs that now redirect, instead of updating them directly
• Treating the migration as done at launch instead of committing to several weeks of active post-launch monitoring
• Not benchmarking beforehand, making it impossible to tell whether a later dip is migration-related or normal fluctuation

SEO Migration Checklist

• Pre-migration rankings, traffic, and full URL inventory benchmarked and saved
• Every old URL mapped to a genuine new equivalent, not defaulted to the homepage
• 301 redirects implemented and tested in staging before launch, with no redirect chains
• Canonicals, robots.txt, and sitemap verified correct on the new environment before and immediately after launch
• Internal links updated to point directly to new URLs
• New environment verified and tracked in Search Console and analytics alongside the old one during transition
• Daily indexing and crawl checks scheduled for at least the first two weeks post-launch

Migrations are exactly the kind of high-risk, high-complexity project our SEO migration service is built for, typically paired with a pre-migration technical SEO audit to establish the benchmark — see a sample SEO audit for what that baseline review looks like. Post-launch, watch for indexing issues and Core Web Vitals shifts specifically, since both commonly move during a migration.