Website migrations terrify marketers for good reason. Research from Searchmetrics shows that 60% of migrations result in significant organic traffic loss. I learned this the hard way managing SEO across four properties during an acquisition.
Each site needed migration coordination. Different platforms. Different timelines. Same organic traffic that was driving millions in pipeline.
The generic SEO audit 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.
This website migration checklist comes from coordinating those four simultaneous migrations without losing traffic. Every step matters. Skip one and you'll spend months recovering rankings you could have preserved.
Website 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.
Unlike other SEO tasks, migration mistakes compound instantly. Miss one redirect and thousands of visitors hit 404 pages. Google sees broken signals. Rankings drop within days.
Most migration advice treats all websites the same. B2B SaaS sites are different. You have product pages, case studies, comparison pages, and content hubs. Each page type needs specific handling during migration.
The stakes are higher too. That organic traffic isn't just vanity metrics. It's pipeline. When search visibility drops 40% overnight, your demand gen numbers crater for months.
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 migrate anything.
Pay special attention to pages driving actual conversions. Not just traffic. Pipeline. Your product comparison pages might get less traffic than blog posts but convert at 10x the rate.
Export every URL from Google Analytics with traffic data from the last 12 months. Include organic sessions, conversions, and revenue attribution when possible.
Create a spreadsheet mapping old URLs to new URLs. This becomes your redirect blueprint. Don't assume URL structures will match perfectly between sites.
Pull ranking data for your top 100-200 keywords before changing anything. Use Ahrefs, SEMrush, or whatever tool you have access to.
Screenshot your Search Console performance over the last six months. You'll need this baseline to measure recovery post-migration. Most well-executed migrations see full traffic recovery within 4-6 weeks.
Your staging site needs to mirror production exactly. Same server configuration. Same URL structure. Same content.
Install Google Analytics and Search Console on staging with different property IDs. You want to test tracking before migration day, not after.
Set up fresh Google Analytics and Search Console properties for your new domain. Don't wait until migration day. These tools need time to start collecting data.
Verify domain ownership in Search Console using DNS verification. DNS verification proves more reliable than HTML file verification during migrations.
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 without direct equivalents, redirect to the most relevant parent page. Don't redirect everything to the homepage. 301 redirects pass 90-99% of link equity when implemented correctly.
Crawl your staging site to identify broken internal links before launch. Fix them now rather than discovering them in Search Console later.
Test your new internal linking strategy. B2B SaaS sites need clear paths from content to product pages to conversion points.
This is make-or-break for your SEO. Every redirect needs to work perfectly from day one.
Test a sample of redirects manually before updating DNS. Type old URLs directly into your browser. They should redirect to the correct new pages instantly.
For large sites, implement redirects in batches. Start with your highest-traffic pages. Monitor for issues. Then roll out the rest.
Upload fresh XML sitemaps with your new URL structure. Don't forget image sitemaps if you have significant visual content.
Update your robots.txt file for the new domain. Remove any staging restrictions. Make sure important pages aren't accidentally blocked.
Google's Change of Address tool tells Google about your domain migration directly. This step is optional but helps Google understand the connection between old and new URLs.
Submit the request in Search Console for your old domain. Point it to your new domain. This process can take several weeks to complete.
Don't just update links on your main site. Check your email signatures, LinkedIn profiles, social media bios, and any other properties you control.
Update links in your email automation sequences. Marketing emails with dead links look unprofessional and hurt deliverability.
Check Search Console daily for the first week. Look for 404 errors, redirect chains, and crawl issues.
Address errors immediately. Every 404 that Google discovers hurts your migration recovery time.
Expect organic traffic to dip initially. That's normal. What matters is the recovery trajectory.
Use your baseline data to track performance week over week. If traffic hasn't started recovering by week three, investigate deeper.
Some internal links will break despite careful planning. Find them fast with weekly site crawls.
Reach out to high-authority sites linking to your old URLs. Ask them to update links to your new domain. This step is optional but helps link equity transfer faster.
Update your Google My Business listing, industry directories, and partner pages with your new domain.
Don't forget about marketing materials. Brochures, case studies, and sales decks with old URLs look outdated.
How long does a website migration take to recover SEO traffic?
Well-executed migrations typically see full traffic recovery within 4-6 weeks. Complex sites or migrations with redirect issues can take 3-6 months.
Should I redirect every old URL individually?
Yes, when possible. Redirecting everything to the homepage destroys user experience and wastes link equity. Map similar content types to similar content types.
What if I discover missed redirects after migration?
Implement them immediately. Check your Search Console coverage report weekly to identify new 404 errors from missed redirects.
Can I migrate during my busy season?
Avoid migrating during high-traffic periods when possible. If you must migrate during busy times, plan extra monitoring and support resources.
How do I handle migrations for one person SEO teams?
Focus on your highest-impact pages first. Perfect redirects for your top 20% of traffic-driving URLs, then handle the rest in batches post-migration.