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

A website migration is one of the riskiest things you can do to your organic traffic.

I’ve been brought in to clean up after enough failed migrations to know that most of the damage was completely preventable - and the difference between a smooth migration and a disaster almost always comes down to the preparation.

The way I see it, SEO should be a priority in any migration, not an afterthought. If you only bring SEO in after your rankings have dropped, you’ll wish you’d dealt with it sooner.

So in this post, I’ll share the SEO migration checklist I use with clients, covering what to do before, during, and after your website migration.

What counts as a website migration?

People often think a migration only means changing your domain name, but any significant change to your website can affect how search engines see it.

The main types of website migration include:

• Domain migrations - moving from one domain to another (including rebrands)
• Platform migrations - changing CMS, e.g. moving from WordPress to Shopify
• Redesigns - new templates, new layouts, new page structures
• URL structure changes - reorganising your site’s URLs or navigation
• Protocol or hosting changes - HTTPS moves, server changes, or consolidating multiple sites into one

Now, some of these are riskier than others, but the reason why they all matter is the same: Google has spent years learning the signals on your website. Your URLs, your internal links, your content, your structured data - they all contribute to how you rank. A migration rewrites those signals, and if the new ones don’t match up, Google essentially has to re-evaluate your site from scratch.

The SEO migration checklist

Here’s the checklist I work through on every migration. I’ve split it into three phases: before launch, launch day, and after launch.

Phase 1: Before the migration

1. Crawl and benchmark your current site

First and foremost, crawl your existing website with a tool like Screaming Frog and save the crawl. This is your record of every URL, title, heading, and internal link on the site - and if anything goes missing after launch, it’s how you’ll prove what was lost.

2. Export your rankings and analytics

Take a full export of your rankings, your top pages by organic traffic, and your Google Search Console data. You need a before picture, because without a benchmark, any recovery work later becomes guesswork.

3. Map every URL that has value

Build a redirect map that accounts for every URL with traffic, rankings, or backlinks - not just the pages in your navigation. This is where most migrations go wrong. The homepage and top pages get mapped, but the hundreds of older URLs quietly earning long-tail traffic get left to 404, and all the value they carried disappears with them.

4. Use one-to-one redirects wherever possible

Each old URL should redirect to its closest equivalent on the new site with a 301 (permanent) redirect. Redirecting everything to the homepage is not a redirect strategy - Google treats those as soft 404s, and the equity doesn’t pass.

5. Check the new site on staging

Before launch, crawl the staging version of the new site and compare it against your benchmark. Are the H1s the same? Has any content been dropped from the new templates? Are the internal links still there, or have they vanished into a JavaScript menu? Is the structured data still in place? This is essentially a parity check, and it catches the problems that are cheap to fix before launch and miserable to fix afterwards.

Phase 2: Launch day

6. Deploy your redirects and test them

The moment the new site goes live, your redirect map needs to be live with it. Test a sample of your most important old URLs immediately to confirm they 301 to the right destinations.

7. Check your robots.txt and meta robots

One of the most common launch-day mistakes is carrying the staging site’s noindex tags or blocked robots.txt over to production. Check both before you do anything else - I’ve seen entire websites deindexed because of this one oversight.

8. Submit your new sitemap

Update your XML sitemap and submit it in Google Search Console. If you’ve changed domains, use the Change of Address tool as well.

9. Verify canonical tags and analytics

Make sure the canonical tags point to the new URLs (not the old ones, and not staging), and confirm your analytics and tag manager are firing on the new site.

Phase 3: After the migration

10. Monitor crawl activity and errors

Watch Google Search Console daily in the first few weeks. The crawl stats report will show you how Googlebot is processing the change, and the pages report will surface any 404s or redirect errors you missed.

11. Track your rankings against the benchmark

Some ranking fluctuation is completely normal while Google recrawls and re-evaluates the site. What you’re looking for is anything that drops and doesn’t start recovering - that usually points to a specific missing redirect, a lost piece of content, or a template issue.

12. Fix what the data tells you

Compare the post-launch crawl with your benchmark crawl. Missing pages, lost internal links, and changed headings are all things you can fix quickly if you catch them early.

How long does it take to recover from a migration?

With proper preparation, most websites see a brief dip while Google recrawls everything, then recover within a few weeks - and often perform better afterwards, because a migration is also a chance to fix long-standing structural problems.

Without preparation, recovery can take many months, and in some cases the traffic never fully comes back. The reason why is simple: the longer broken signals sit there, the more Google’s picture of your site resets.

Final thoughts

A successful website migration isn’t about luck - it’s about doing the unglamorous preparation work properly and in the right order.

If you’re planning a migration and want a specialist to handle the SEO side, my SEO migration services cover everything in this checklist, from benchmarking through to post-launch monitoring. And if you’ve already migrated and lost traffic, don’t wait for it to fix itself (it won’t) - get in touch and I’ll tell you honestly what’s recoverable.

For everything else that keeps a website technically healthy, check out my technical SEO services or speak to an SEO consultant about your specific situation.