Website Migration SEO Checklist: How to Switch Platforms Without Losing Your Rankings

I've migrated more websites than I can count at this point. Some went perfectly. Some did not.

The ones that didn't go well all had something in common: someone skipped steps. Usually the boring ones. The redirect map nobody wanted to build. The metadata nobody thought to export. The monitoring nobody set up for the first month.

Here's the uncomfortable truth about website migrations: only about 10% actually improve search rankings. The rest either hold steady (if you're lucky) or tank. I've seen sites lose 50% of their traffic overnight. I've migrated client sites from WordPress to Astro and learned these lessons the hard way.

So I put together this website migration SEO checklist. Not from theory. From real projects where real money was on the line.

Why Most Website Migrations Tank Your Traffic

Let me be direct with you. Most migrations lose between 20-40% of their SEO value, even when executed well. That's the baseline. That's what "going well" looks like.

The reason is simple: Google has built a complex understanding of your site over months or years. Your URLs, your internal link structure, your content relationships, your domain authority signals. When you move to a new platform, you're asking Google to rebuild that understanding from scratch.

And Google doesn't do that quickly.

The commonly cited average recovery time is 523 days. Over a year and a half. And 17% of domain migrations never recover at all. Those aren't scare tactics. Those are numbers I've seen play out in client projects.

There's another layer now too. Migrations don't just affect traditional search results. They can impact your visibility in AI Overviews, featured snippets, and other SERP features that took months to earn.

So why migrate at all? Because sometimes you have to. Your current platform can't scale. The tech debt is killing your development speed. Performance is terrible and it's hurting conversions. Valid reasons, all of them. You just need to do it right.

Before You Touch Anything: The Pre-Migration Checklist

This is where most people rush. Don't.

Before you write a single line of code on the new platform, you need to benchmark everything. Here's what I document for every client migration:

Performance benchmarks:

• Current organic traffic (last 6 months, monthly)
• Top 20 pages by traffic (these are your priority pages)
• Current keyword rankings for target terms
• Core Web Vitals scores
• Domain authority and backlink profile
• Indexed page count in Google Search Console

Full site export:

• Every URL on the site (run a full crawl with Screaming Frog or similar)
• All meta titles and descriptions
• All internal links and their anchor text
• Structured data markup
• Image URLs and alt text
• Any custom canonical tags or hreflang attributes

Technical prep:

• Set up your staging site and block it from crawlers (robots.txt, noindex, password protection)
• Back up your entire current site, database and files
• Document your current robots.txt and sitemap structure

This sounds like a lot of work. It is. But every hour you spend here saves you ten hours of panic later. I've learned this from experience, and I've written about it in detail in our website relaunch checklist.

Your top 20 traffic pages deserve special attention. These are the pages that actually make you money. Test them first, test them last, and test them again after launch.

The Redirect Map Is Everything

If I could only give you one piece of advice about website migrations, it would be this: get your redirect map right.

Redirect misconfiguration causes over 60% of traffic loss in the first 30 days after migration. That's not a typo. More than half of all migration disasters come down to broken or missing redirects.

Here's what a proper redirect strategy looks like:

Map every single URL. Not just pages. Every URL that has ever received traffic or has backlinks pointing to it. Old blog posts from 2019 that still get 50 visits a month? Map them. That PDF download link someone shared on Reddit three years ago? Map it.

Use 301 redirects, not 302s. 301 redirects pass full link equity. 302s tell Google the move is temporary, which means Google holds onto the old URL and doesn't transfer your authority.

Keep redirects active for at least one year. Google recommends this explicitly. I'd keep them longer if possible. Removing redirects too early is one of the most common mistakes I see.

Don't forget non-HTML assets. Images, PDFs, downloadable files. If other sites link to your images or documents, those links need redirects too. This gets overlooked constantly.

Test every redirect before launch. I use a simple spreadsheet: old URL in column A, expected new URL in column B, actual result in column C. Run through every single one. Yes, even if there are 500 of them.

Understanding the importance of technical SEO is critical here. Redirects aren't glamorous. They're not the exciting part of a new website. But they're the difference between keeping your traffic and watching it disappear.

Migration Day: What to Do When You Flip the Switch

Migration day should be boring. If you've done the prep work, it's just execution.

Here's my migration day checklist, in order:

1. Remove noindex tags from the new site (you blocked crawlers during staging, remember?)
2. Activate all 301 redirects and verify they work
3. Submit your updated XML sitemap to Google Search Console
4. Verify SSL certificate is properly configured (no mixed content warnings)
5. Confirm analytics tracking is firing on every page
6. Test structured data with Google's Rich Results Test
7. Check your top 20 pages manually, every single one
8. Verify robots.txt allows crawling of everything that should be crawled
9. If changing domains: submit a Change of Address in Google Search Console

Do this on a Tuesday or Wednesday morning. Not a Friday. Not before a holiday. You want a full work week ahead of you to catch and fix problems.

One thing I always do: I keep the old site available as a fallback for at least 48 hours. If something goes catastrophically wrong, I want to be able to roll back.

The First 30 Days After Migration

The migration isn't done when the new site goes live. It's done when your traffic recovers.

For the first 30 days, I monitor daily:

• Organic traffic compared to pre-migration baseline
• Crawl errors in Google Search Console (404s, 500s, redirect loops)
• Index coverage (are pages getting indexed? are old URLs getting deindexed?)
• Core Web Vitals (new platform might have different performance characteristics)
• Rankings for target keywords (expect some fluctuation, but watch for drops over 10 positions)

Here's what recovery typically looks like:

• If you catch issues early (first week): 4-8 weeks to recover
• If issues go unnoticed for a month: 3-6 months to recover
• Domain changes: up to 1 year for full recovery, sometimes longer

The key word there is "catch." You can't fix what you don't measure. That's why the monitoring matters so much.

I wrote about broader website optimization strategies that apply here too. Core Web Vitals, page speed, mobile performance. A migration is a good opportunity to improve these things, but only if you're tracking them.

If traffic drops more than 20% in the first week and your redirects are all working, don't panic. Some fluctuation is normal as Google recrawls and reprocesses your site. But if it hasn't started recovering by week three, start investigating.

The Mistakes I See Over and Over

After doing this for years, I keep seeing the same mistakes.

Redirecting everything to the homepage. This is the big one. Someone decides that instead of mapping 300 old URLs to their new equivalents, they'll just redirect everything to the homepage. Google sees this as a soft 404. You lose all the page-specific authority you built up. I've seen this wipe out 80% of a site's traffic.

Forgetting to update robots.txt. Your staging robots.txt blocks all crawlers. You launch the new site and forget to update it. Google can't crawl anything. I've seen sites go weeks before someone notices.

Losing metadata. All those carefully written meta titles and descriptions you had? Gone, replaced by auto-generated defaults from the new CMS. Export them before migration and reimport them after.

Skipping structured data migration. Your old site had review schema, FAQ schema, product schema. Your new site doesn't. Those rich results you were getting in search? Gone.

Not monitoring after launch. "We launched, it looks great, let's move on to the next project." Three weeks later, traffic is down 40% and nobody noticed. This is shockingly common.

Changing URL structure unnecessarily. If your old URLs were /blog/post-title and your new platform defaults to /posts/post-title, consider keeping the old structure. Every URL change is a risk. If the new structure isn't meaningfully better, keep the old one.

Download the complete checklist: Grab this checklist as a printable PDF so you don't miss anything. Download checklist (PDF)

When to Hire Help (and When You Can DIY)

Not every migration needs a specialist. Here's how I think about it:

You can probably DIY if:

• Same domain, same URL structure, just a visual redesign
• Small site (under 50 pages)
• No significant organic traffic to protect
• You're comfortable with redirect configuration on your platform

You should get help if:

• Changing platforms with URL structure changes (WordPress to Shopify, for example)
• Site has 100+ pages with established organic traffic
• You have significant backlinks that need to be preserved
• International site with hreflang attributes

You really need expert help if:

• Changing domains entirely
• Merging multiple sites into one
• Enterprise site with thousands of pages
• Revenue directly depends on organic traffic

The cost of hiring someone to manage a migration properly is almost always less than the cost of lost traffic. I've seen businesses lose months of revenue from botched migrations. A few thousand dollars for expert help looks cheap compared to that.

If you want to understand what professional SEO support looks like, I break it down in SEO Services Explained.

The Bottom Line

A website migration doesn't have to be a disaster. But it does require respect for the process.

Benchmark everything before you start. Build your redirect map like your business depends on it, because it does. Monitor obsessively for the first month. And don't skip the boring stuff.

The boring stuff is what saves you.

If you're planning a migration and want someone to look over your checklist before you flip the switch, reach out. I'd rather help you avoid problems than fix them after the fact.