Website Migration SEO Checklist: The 15 Steps You Can't Skip

Website migrations terrify marketers for good reason. Research from Searchmetrics and most agencies puts the failure rate high: a large share of migrations lose significant organic traffic. The traffic doesn’t come back on its own.

I learned this the hard way managing SEO across four properties during an acquisition. Four sites. Different platforms. Different timelines. Same organic traffic that was driving millions in pipeline. Each one needed migration coordination, and I was the team doing it.

The generic SEO checklists online don’t account for B2B SaaS complexity. Multiple conversion paths. Product pages with specific URL structures. Content hubs that feed the sales team. They treat a SaaS site like a personal blog. It isn’t.

This checklist comes from coordinating those four simultaneous migrations without tanking traffic. Every step matters. Skip one and you’ll spend months recovering rankings you could have just kept.

What makes a website migration different from other SEO work

Migration isn’t like optimizing a blog post or fixing site speed. You have a hard deadline. A specific launch date. No room for gradual testing.

And the mistakes compound instantly. Miss one redirect and thousands of visitors hit 404s. Google sees broken signals. Rankings drop within days, not months.

Most migration advice treats every website the same. B2B SaaS sites aren’t the same. You have product pages, case studies, comparison pages, and content hubs. Each page type needs specific handling.

The stakes are higher too. That organic traffic isn’t a vanity metric. It’s pipeline. When search visibility drops 40% overnight, your demand gen numbers crater for months. Someone is going to ask why. So treat the migration like the revenue event it actually is.

Pre-migration planning (3-4 weeks before)

This is where the migration is actually won. Everything on launch day is just execution of decisions you made now.

1. Complete a full SEO audit

Start with a comprehensive crawl of your existing site. Use Screaming Frog or Sitebulb to identify every URL, broken link, and technical issue before you move anything.

Pay special attention to pages that drive conversions, not just traffic. Pipeline. Your product comparison pages might pull less traffic than blog posts but convert at 10x the rate. Those are the pages you protect first.

2. Map URLs and traffic

Export every URL from analytics with traffic data from the last 12 months. Include organic sessions, conversions, and revenue attribution where you can get it.

Build a spreadsheet mapping old URLs to new URLs. This is your redirect blueprint. Don’t assume the structures will match cleanly between platforms. They almost never do.

3. Document your baseline

Pull ranking data for your top 100-200 keywords before you touch anything. Use Ahrefs, SEMrush, or whatever you have access to.

Screenshot your Search Console performance over the last six months. You need this baseline to measure recovery later. Without it, you’re guessing whether things are getting better or worse.

Technical migration setup (1-2 weeks before)

4. Set up a staging environment

Your staging site needs to mirror production exactly. Same server config. Same URL structure. Same content.

Install analytics and Search Console on staging with separate property IDs. You want to test tracking before migration day, not discover it’s broken after.

5. Configure tools for the new domain

Set up fresh analytics and Search Console properties for the new domain now. Don’t wait for launch. These tools need time to start collecting data.

Verify domain ownership in Search Console using DNS verification. DNS verification is more reliable than HTML file verification during a migration, when files are getting moved around anyway.

6. Plan your redirect strategy

This is where most migrations fail. Every old URL needs a destination. Product pages go to new product pages. Blog posts go to new blog posts. Category pages go to new category pages.

For pages with no direct equivalent, redirect to the most relevant parent page. Do not redirect everything to the homepage. Clean 301s pass the large majority of link equity. Lazy redirects throw it away.

7. Test the new site structure

Crawl your staging site to find broken internal links before launch. Fix them now instead of discovering them in Search Console later.

Test your internal linking strategy while you’re there. B2B SaaS sites need clear paths from content to product pages to conversion points. If those paths break in the migration, your funnel breaks with them.

Migration day execution

8. Implement 301 redirects

This is make-or-break. Every redirect needs to work perfectly from the moment you go live.

Test a sample manually before updating DNS. Type old URLs straight into your browser. They should redirect to the correct new page instantly, no chains, no detours.

For large sites, roll out redirects in batches. Start with highest-traffic pages. Monitor. Then push the rest.

9. Update XML sitemaps

Upload fresh sitemaps with the new URL structure. Include image sitemaps if you have meaningful visual content.

Update robots.txt for the new domain. Strip out any staging restrictions. Double-check you’re not accidentally blocking pages that matter.

10. Submit a change of address

Google’s Change of Address tool tells Google directly about the domain move. It’s optional, but it helps Google connect old and new URLs faster.

Submit it in Search Console for the old domain, pointed at the new one. The process can take several weeks to complete, which is exactly why you don’t want to skip it.

11. Update every link you control

Don’t just fix links on the main site. Email signatures. LinkedIn profiles. Social bios. Any property with your name on it.

Update links inside your email automation too. Marketing sequences with dead links look unprofessional and hurt deliverability. These are easy to forget and embarrassing to miss.

Post-migration monitoring (first 30 days)

12. Monitor crawl errors daily

Check Search Console every day for the first week. Look for 404s, redirect chains, and crawl issues. Fix them immediately. Every 404 Google discovers adds time to your recovery.

13. Track traffic recovery against your baseline

Expect an initial dip. That’s normal. What matters is the trajectory. Track performance week over week against the baseline you documented earlier. If traffic hasn’t started recovering by week three, dig deeper. Something is broken.

14. Fix broken links as they surface

Some internal links will break despite your planning. Catch them with weekly crawls.

For high-authority external sites linking to old URLs, reach out and ask them to point at the new domain. Optional, but it speeds up link equity transfer.

15. Update marketing materials and listings

Update Google Business Profile, industry directories, and partner pages with the new domain. Don’t forget offline assets either. Brochures, case studies, and sales decks with old URLs make the whole thing look half-done.

The one-person version of this

If you’re a solo operator like I was across those four properties, you can’t make everything perfect on launch day. So don’t try. Get the redirects flawless for the top 20% of traffic-driving URLs, the pages tied to pipeline, and batch the rest post-launch.

The whole point of treating migration as a system instead of a panic is that you decide what matters before the deadline forces the decision for you. Build the redirect map, document the baseline, and the launch becomes execution instead of improvisation.

Want the systems approach to SEO and the rest of your growth engine? Start with the blog, or book a call if you want help before your next migration.

Related reading: How to Build an SEO Strategy Your Skeleton Crew Actually Owns · score yourself with the matching audit · start with an audit · read the manifesto