New researchTechnical SEO & AI Search · 2027Explore the framework

Monitor redirects after a site migration: an ongoing QA plan

Build a post-migration redirect monitoring routine that catches broken mappings, chains, old internal links and traffic losses long after launch.

Part of the Site Migrations series. For the full picture, start with Site migration SEO checklist: crawl before, during and after launch.

Redirect monitoring after a site migration is the work that starts once the launch checklist ends. A redirect map can pass on launch day and fail later when a CDN rule, CMS route or product URL changes. The site migration checklist covers planning and launch; this guide covers how to keep old URLs working and catch drift over time.

What should you monitor after a site migration?

Keep the complete old-to-new URL map as a test set. For every old URL, check the response code, each hop, the final URL and whether that destination serves the intended content. Google’s site-move guidance recommends testing redirects and monitoring traffic on both old and new URLs.

Signal Healthy pattern Investigate when
Old URL response Permanent redirect to the relevant new URL 404, temporary redirect, loop or wrong target
Final destination Live and indexable when meant to rank 5xx, noindex, unrelated content or wrong canonical
New internal links Point directly to final URLs Menus and templates still link through redirects
New sitemap Lists canonical final URLs Old, redirected or non-indexable URLs remain
Search and visits New URLs gradually take over Valuable old pages have no matching new visibility

Not every retired URL requires a replacement. If a page was intentionally removed and has no equivalent, record that decision. The redirect mapping guide explains how to distinguish a genuine replacement from an irrelevant catch-all.

How do you build a repeatable redirect test?

Start with the mapping created before launch. Preserve the original URL, intended destination, page type, previous traffic or links, and the reason for the mapping. Add URLs from old sitemaps, analytics, server logs and Search Console that the original inventory missed.

Run the old URL list through a crawler or HTTP test that follows redirects and records every hop. Compare the final URL with the approved map, not just with “any 200.” A technically successful 301 to the wrong product or language page is still a migration error. The international URL mapping guide covers locale-specific cases.

For the new site, separately crawl internal links and the new sitemap. Google’s site-move guidance says to update internal links to new URLs and submit the new sitemap. Leaving your own navigation on old URLs adds unnecessary redirect hops and makes future cleanup harder.

When should you recheck the redirects?

Use a risk-based schedule, not a universal deadline. Check critical paths immediately after launch and after every routing, CMS, CDN or catalogue release. Retest the full map periodically while old URLs still receive requests or links. The right interval depends on how often the site changes and how costly a broken mapping would be.

A practical monitoring log includes the date, test version, number of old URLs tested, changed outcomes, owner and resolution. Put business-critical URLs, linked pages and formerly high-click pages in a small alerting set. A full test can run less often, but the alerting set should not disappear once the launch room closes.

Google recommends keeping redirects as long as possible, generally at least one year so its systems can revisit old and new URLs and transfer signals. That is a minimum monitoring horizon, not an instruction to switch every redirect off after twelve months. Consider long-lived external links and bookmarks before removing rules.

How do you separate migration problems from normal fluctuations?

Use Search Console and analytics alongside the HTTP tests. Google’s site-move documentation says ranking and traffic fluctuations can occur while a move is processed. A dip alone is not proof of a broken redirect; a dip plus a 404 on the mapped old URL or a noindexed destination is stronger evidence.

Compare groups of URLs by page type, section and market. Watch whether new pages gain impressions as old pages fade, and investigate important old URLs whose replacement has no visibility. If the mapping passes but performance stays weak, the traffic-drop-after-migration guide covers other causes, such as lost content or internal links.

Post-migration redirect monitoring checklist

  • Preserve the approved old-to-new map and add missed old URLs.
  • Test every old URL’s status, hops, final URL and content match.
  • Flag loops, chains, temporary redirects and irrelevant destinations.
  • Check new internal links and sitemaps for final canonical URLs.
  • Compare Search Console and analytics by old and new URL groups.
  • Re-test after routing changes and keep redirects for at least a year.

Frequently asked questions

How long should migration redirects stay in place?

Google recommends keeping them as long as possible, generally at least one year. Longer can help people and links that still use old URLs, but you should update your own links to the final destinations.

How often should I test redirects after a migration?

Set a cadence based on launch risk and site changes: intensive checks immediately after launch, then repeated checks after releases and while old URLs still receive traffic. The important point is to retain the full URL map and re-test it, not to rely on one launch-day crawl.

Is a 301 to the homepage good enough for an old page?

Usually not. Map a page to its relevant replacement; if no equivalent exists, handle its removal deliberately. A mass redirect to an unrelated homepage can hide missing content and may be treated as a soft 404.

Can Search Console replace redirect testing?

No. Search Console shows Google's crawl and performance data after processing, while a redirect test can detect a wrong target immediately. Use both, plus analytics and server logs where available.

· Founder, Crawlens

Dien builds Crawlens, a desktop crawler for technical SEO audits, and writes about the checks it runs: crawling, indexing, rendering and Search Console data.

Audit your own site with Crawlens

Crawl, run 70 checks, and see them next to Search Console and Core Web Vitals data.

Download free for Windows