Migration technical SEO checklist: 50 things to verify before launching a redesigned site

Key takeaways

• Redirect mapping is the most important migration task: every indexed URL should redirect in one hop to its closest new equivalent.
• Google advises keeping redirects for at least a year and says a small to medium site can take a few weeks for most pages to move.
• Benchmark everything before launch so you can measure results and diagnose drops.
• Test on a protected staging site that mirrors production, then monitor daily for the first 30 days and weekly for 90.
• Most migration losses come from problems that were detectable before launch.

A platform change, domain move or redesign touches nearly every signal search engines use: URLs, internal links, content, speed and structured data. Google’s site move guidance says to expect temporary ranking fluctuation during a move, but a careful process keeps that dip small and short. This Emulent checklist covers 50 items to verify, from benchmarking to post-launch monitoring.

What should you document and benchmark before a migration?

Everything you need to protect and later compare against. Items 1 to 15:

1. Export indexed pages from Search Console with impressions, clicks and average position.
2. Crawl the current site and export every URL with status code, title, meta description, canonical and internal link count.
3. Export your backlink profile from Ahrefs, Semrush or similar, and note which pages earn the most links.
4. Document XML sitemap files, their URLs and URL counts.
5. Save the current robots.txt and document every rule.
6. Record Core Web Vitals field data for top templates.
7. List Google Business Profile and local listing URLs that point to your site.
8. Document structured data types and where they appear.
9. Record hreflang annotations for multilingual or multi-region sites.
10. Capture search results and rich results for your top 20 queries.
11. Export 12 months of analytics: top organic landing pages, conversions and revenue by page.
12. List integrations tied to URLs, such as email templates, social profiles, ad landing pages and partner links.
13. Record server response times (TTFB) for main page types.
14. List URL parameters and how each is handled.
15. Document navigation, footer, sidebar and related-content linking.

How should you plan redirect mapping and URL strategy?

Map every old URL to its best new match before development ends. Items 16 to 25:

16. Build a one-to-one redirect map, starting with pages that have traffic, links or rankings.
17. Use 301 redirects for permanent changes.
18. Remove chains so each old URL reaches its final destination in one hop.
19. Send URLs without an equivalent to the closest relevant page or category, not the homepage; return 404 or 410 only for content with no replacement.
20. Define canonical and blocking rules for tracking, sort and filter parameters on the new platform.
21. Use lowercase, hyphenated, descriptive and consistent URLs.
22. Test every redirect on staging with a bulk checker.
23. Update links you control, such as social profiles, Google Business Profile, directories, email templates and ad URLs.
24. Fold redirects from earlier migrations into the new map so old URLs do not chain.
25. Plan to monitor 404s in Search Console and logs, and keep redirects in place for at least a year.

What should you test on staging before launch?

Test the new site as if it were live, while keeping it out of search. Items 26 to 37:

26. Protect staging with HTTP authentication or IP restrictions; robots.txt alone does not keep URLs out of the index.
27. Crawl staging and compare page counts, titles, descriptions, canonicals and headings with the old crawl.
28. Validate structured data with the Rich Results Test and confirm every current type carries over.
29. Check that XML sitemaps generate correctly and list only valid new URLs.
30. Confirm canonicals on every template use the new URLs.
31. Test hreflang reciprocity, language codes and x-default.
32. Run performance tests and compare with your benchmarks.
33. Update internal links to point directly to new URLs instead of relying on redirects.
34. Test forms, analytics tags and conversion paths so measurement works from day one.
35. Prepare the production robots.txt with no leftover staging blocks and correct sitemap references, and list any noindex tags to remove at launch.
36. Confirm HTTP-to-HTTPS and www or non-www redirects on the new server.
37. Compare content on old and new pages to make sure nothing important was cut or reformatted away.

On WordPress, Emulent stages rebuilds on Kinsta, whose staging environments can be password protected and pushed to live when ready. For ecommerce replatforms, we recommend Shopify and map product, collection and blog URLs to its fixed URL patterns.

What should you do on launch day and after?

Launch everything together, then watch closely. Items 38 to 50:

38. Deploy all redirects at the same moment as the new site.
39. Submit the new XML sitemaps in Search Console.
40. Request indexing for your most important pages with URL Inspection.
41. Check the Page indexing report daily for 30 days for spikes in 404s, redirect errors or excluded pages.
42. Check server logs to confirm Googlebot is crawling new URLs and following redirects.
43. Compare organic traffic daily against benchmarks; some fluctuation is normal, but a steep, sustained drop needs immediate investigation.
44. Check rich result reports in Search Console to confirm rich results carried over.
45. Spot-check redirects on the live site.
46. Watch Core Web Vitals field data, which uses a rolling 28-day window, so allow about a month for it to reflect the new site.
47. Update remaining external links you control.
48. Crawl the full site two weeks after launch and compare with the staging crawl.
49. Review rankings weekly for 90 days and investigate pages that dropped.
50. Document what was planned, what happened and what you would change next time.

For domain changes, also use Search Console’s Change of Address tool; Google says it is not needed for HTTP-to-HTTPS or www changes.

How can the Emulent team help?

Emulent supports migrations from benchmarking and redirect mapping through staging checks, launch oversight and 90 days of monitoring as part of enterprise SEO engagements. A caveat: even well-run migrations usually see short-term fluctuation, so plan launches away from peak sales periods. Contact the Emulent team to plan your migration.