ummseo
Technical SEO

Site Migration SEO Checklist: How to Move a Website Without Losing Your Rankings

By The UMM SEO Editorial Team··9 min read·1,146 words

A site migration keeps its rankings when every existing URL is mapped to its exact new destination with a 301 redirect, the content and technical signals search engines already trust are carried over unchanged, and performance is monitored closely in the weeks after launch. Skip any one of those steps and even a carefully planned move can cause a real, sometimes lasting, drop in traffic — not because Google penalises migrations, but because it has to rediscover and re-earn trust in URLs it has never crawled before.

A migration is not just a domain change. Switching from HTTP to HTTPS, moving to a new CMS or platform, restructuring URL patterns in a redesign, or merging several sites into one all count, and all carry the same underlying risk. This guide is a practical checklist: what a migration actually is, how to plan the URL mapping and redirects, which technical signals to carry over, what to verify the moment the new site goes live, and how to monitor recovery afterward.

What counts as an SEO site migration?

An SEO site migration is any change that alters a page's URL, domain, protocol or overall site structure — a domain change, an HTTP-to-HTTPS switch, a CMS or platform move, a redesign that changes URL patterns, or consolidating multiple sites into one. Google treats each changed URL as new and unproven, not simply as an edit to a page it already trusts.

Risk scales with scope. Changing a handful of URLs during a small redesign is low-risk if handled correctly; changing every URL on a 10,000-page site, or moving domains entirely, touches every ranking signal at once. Google's own guidance on site moves with URL changes treats these as fundamentally different situations that call for proportionally more planning.

Build a complete URL mapping and redirect plan before you launch

The single highest-leverage step in any migration is mapping every existing URL to its exact new equivalent and implementing a 301 redirect for each pair, rather than redirecting everything to the homepage. A precise one-to-one map tells search engines exactly where a page's rankings and authority should transfer; a blanket homepage redirect strands that value and rarely recovers it in full.

Build the map before the old site goes offline, not after. Crawl the existing site to capture every indexed URL — including ones that only show up in analytics or Search Console, not just the visible navigation — then pair each one with its new destination. This is the same rigour a thorough technical SEO audit applies outside a migration, just compressed into a single, higher-stakes pass.

  • Crawl the live site and export every indexed URL before it changes or goes offline
  • Cross-check against Search Console and analytics for URLs that get traffic but are not in the main navigation
  • Map each old URL to its single closest new equivalent — never to the homepage by default
  • Use permanent 301 redirects for anything moving for good; reserve 302s for genuinely temporary changes
  • Eliminate redirect chains by pointing every old URL straight at its final destination

Preserve the technical signals search engines already trust

Preserving rankings means carrying over the technical elements Google already associates with each page — title tags, meta descriptions, heading structure, internal links, canonical tags and structured data — not just the visible content underneath them. Migrations that change content and technical structure at the same time make it impossible to tell which change caused any resulting shift.

Treat the migration as a like-for-like move first, and save content or on-page SEO improvements for a deliberate follow-up once the new URLs have stabilised. Update the XML sitemap to list only the new URLs, keep canonical tags pointing at themselves on the new domain, and make sure structured data survives the platform change intact.

What to verify the moment the new site goes live

On launch day, verify that redirects actually fire, robots.txt is not accidentally blocking the new site, the updated XML sitemap is submitted, and Search Console's change of address tool is set correctly if the domain changed — all before assuming the migration is done. A single blocked robots.txt rule left over from staging can quietly deindex an entire new site.

Spot-check a representative sample of redirects across every major page type — not just the homepage — and confirm internal links point directly at new URLs rather than relying on redirects to carry the click. Run this checklist the same day as launch; problems caught within hours are far cheaper to fix than ones discovered a week into a ranking drop.

  • Spot-check redirects across every page type: homepage, category, product or article, and deep pages
  • Confirm robots.txt on the new site or domain is not blocking crawling by mistake
  • Submit the updated XML sitemap and remove any sitemap still referencing old URLs
  • Run Search Console's change of address tool immediately for a full domain change
  • Update internal links, canonical tags and hreflang to point at new URLs directly, not through a redirect

Monitor recovery and set realistic expectations

After launch, monitor recovery by tracking crawl stats, indexing coverage, and rankings for priority pages in Search Console on a weekly basis, expecting some short-term ranking volatility while Google recrawls and reprocesses the new URLs. Google has been explicit that a well-executed migration can still take weeks for signals to fully transfer, so a temporary dip is not automatically a sign something went wrong.

Set a review cadence rather than checking once and moving on: weekly for the first month, then monthly once metrics stabilise. If a specific page has not recovered within a few weeks while comparable pages have, treat that as a signal to re-check its individual redirect, canonical tag and internal links rather than assuming the whole migration is failing. Folding this review into ongoing SEO consulting keeps it from being dropped once the initial launch excitement fades.

Common migration mistakes that cause lasting ranking losses

The mistakes that turn a migration into a lasting ranking loss are almost always avoidable: no real URL map, blanket homepage redirects, changing content and structure at the same time as the URLs, and leaving the old site or a staging copy live and indexed alongside the new one. Any one of these can undo weeks of otherwise careful planning.

Backlinks deserve a specific mention. A redirect preserves most of a link's value, but it is not identical to the original link pointing directly at a live, indexed page, so a migration is a reasonable moment to reach out to a handful of your highest-value referring sites and ask them to update the URL directly — the same relationship-driven approach behind backlink building and digital PR applies just as well to protecting links you already have as it does to earning new ones.

  • No documented URL map — redirects built ad hoc instead of from a full crawl
  • Redirecting most or all old URLs to the homepage instead of their closest equivalent
  • Changing content, design and URLs simultaneously, making problems impossible to isolate
  • Leaving the old domain, subdomain or a staging environment live and indexed
  • Never following up with high-value linking sites to update anchor URLs directly

Try the free Link Gap Calculator

See roughly how many quality backlinks you need — and how long it takes — to rank for your keyword on Google and in AI search engines.

Open the Link Gap Calculator →

The UMM SEO Editorial Team

SEO strategy & link building

Written and fact-checked by the UMM SEO team — the strategists, link builders and content specialists who run real SEO campaigns for clients every week. Our guidance comes from hands-on backlink building, technical and on-page SEO, content and digital PR work, not from theory.

Frequently asked questions

What is an SEO site migration?

An SEO site migration is any change that alters a page's URL, domain, protocol or site structure — including a domain change, an HTTP-to-HTTPS switch, a CMS or platform move, a URL restructure, or merging multiple sites into one. Google treats each changed URL as new and unproven rather than as an edit to a page it already trusts.

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

Recovery typically takes several weeks as Google recrawls and reprocesses the new URLs, though it can take longer on larger sites or domain-wide changes. Some short-term volatility is normal and not automatically a sign of a problem, but a page that has not recovered after several weeks while similar pages have is worth checking individually.

Should I use 301 or 302 redirects for a site migration?

Use 301 (permanent) redirects for any URL that is moving for good, since that is what tells search engines to transfer ranking signals to the new URL. Reserve 302 (temporary) redirects for genuinely short-term situations, because they do not pass the same long-term signal.

Do I need to use Google Search Console's change of address tool?

Yes, whenever the migration involves a full domain change. The change of address tool tells Google explicitly that a site has moved, which speeds up how quickly it processes the new domain, whereas relying on redirects alone leaves Google to infer the move gradually through normal crawling.

Can a site migration cause permanent ranking loss?

It can, but usually only when execution goes wrong — missing redirects, a robots.txt blocking the new site, content changed at the same time as the URLs, or an old domain left live and competing with the new one. A migration planned around a complete URL map and verified at launch should recover fully within a normal timeframe.

Want this done for your site?

Message us on Telegram for a free SEO audit, a tailored strategy and a custom quote. No forms, no sales calls — just a straight answer.