SEO checks before and after a site migration
Updated 2026-11-17
Most traffic lost in a migration is lost to a few predictable mistakes: missing redirects, a robots.txt copied from staging, canonicals pointing at the old domain. They are easy to catch if you look the day you switch.
Before the switch
- Baseline audit of the live site. Keep the report; its
site.sitemapblock records how many URLs were listed. - URL map. Export every URL from the old sitemap and map each to its new address. Pages without a counterpart get a redirect to the closest relevant page, not the homepage.
- Audit the staging site if it is reachable publicly. Expect noindex and a blocking robots.txt there; write down that they must be removed at launch.
Launch day
- Run an audit on the new site within the hour.
- Look first for robots.txt blocking Googlebot, noindex pages and canonicals pointing to another domain. Any of these can undo the migration on its own.
- Check broken pages and sitemap errors: they reveal URLs the map missed.
- Request a sample of old URLs and confirm each reaches its new page in a single redirect.
The weeks after
Re-audit weekly for a month. Compare the score and the plan.now list with the baseline; a new high-severity finding is a regression. Submit the new sitemap in the webmaster tools and keep redirects in place for at least a year.
Cost
Baseline, staging, launch-day and four weekly checks are seven audits at the per-report price shown on the audit page.
Run the full audit on your site. One call checks every item in the check reference and ranks the fixes.
Open the playground Endpoint details