Protecting Your Rankings During a Website Migration

Benchmark before you change anything

Export current rankings, traffic by page and backlinks. You need a baseline to detect problems after launch.

Build a complete redirect map

Every old URL with traffic or links should 301 redirect to its most relevant new equivalent. Avoid redirecting everything to the homepage.

Test on staging

Crawl the staging site to check titles, canonicals, internal links, structured data and noindex tags before launch.

Monitor after launch

Watch Search Console coverage, crawl errors and traffic daily for the first weeks.

• Submit the new sitemap
• Check redirects resolve correctly
• Fix 404s with traffic
• Confirm analytics is tracking

Set launch acceptance criteria

Agree the checks that must pass before launch: important pages render correctly, redirects point directly to relevant destinations, canonicals use the intended public host, and production pages are not accidentally blocked. Compare a crawl of the old site with the planned new structure, including PDFs and other assets that attract traffic or links. Preserve valuable URLs where practical.

Create a rollback plan with the development team and identify who owns DNS, deployment, content and analytics decisions. Record redirects and tracking configuration outside individual accounts so another team member can inspect them. A launch checklist should include real mobile journeys and form submissions, not only a homepage screenshot.

Separate normal fluctuation from a technical fault

After launch, prioritise evidence of broken redirects, unexpected noindex directives, server failures and missing content. Search engines need time to process structural changes, so traffic fluctuation alone does not identify a cause. Review affected page groups against the baseline, keep a change log and fix verified issues first. A migration plan reduces avoidable risk; it cannot guarantee that rankings will remain unchanged.