Define the legacy-to-final URL contract

Export the pre-migration URLs from the old sitemap, Search Console, analytics landing pages, backlink data and server logs where available. Include important retired campaign links and PDF URLs, not just pages that still appear in the new navigation. For each legacy URL, record one intended final URL, its purpose and the owner who can verify equivalence.

An old emergency-service page should redirect to the new equivalent service page, not the home page merely because it is convenient. If no relevant replacement exists, a real 404 or 410 can be more honest than a misleading catch-all. Keep an exception list for temporary campaign redirects, authentication flows and legitimately removed resources.

Crawl the complete redirect path, not only the first hop

Use a crawler or a scripted HTTP client that records each status and Location header until the terminal response. Capture the initial URL, every hop, final URL, status, response time and whether the chain crosses protocols or hosts. Flag loops, 5xx responses, redirects to blocked or non-indexable destinations, and chains longer than one hop for review.

For example, /old-service might redirect to http://newsite/service, then https://newsite/service/, then /services/current. Visitors may arrive, but every extra hop adds latency and operational fragility. Update the first rule to point directly to the canonical destination and test both desktop and mobile entry points.

Check canonical, sitemap and internal-link agreement

The terminal page should normally return 200, be indexable when intended, and declare a canonical consistent with its final public URL. Verify that the XML sitemap lists final canonical URLs rather than legacy paths. Search internal templates, navigation, breadcrumbs, structured data and email links for old URLs. Redirects are a safety net, not a permanent internal-linking strategy.

Google describes permanent server-side 301 and 308 redirects as strong signals for canonical destination changes. A redirect is only one signal, however; conflicting canonicals, old sitemap entries and links to intermediate destinations can complicate the move. Record those contradictions in the same issue tracker as broken redirects.

Monitor indexing and demand with matched cohorts

Segment priority URLs into high-traffic, high-conversion, heavily linked and low-risk cohorts. Track requests to old paths, Googlebot responses, Search Console indexing and impressions, organic landing-page sessions and business conversions on the new URLs. Compare like-for-like periods and account for seasonality, measurement changes and URL renaming.

Expect indexing and traffic to fluctuate during a move. Do not treat a temporary impression dip as proof that a specific redirect caused it. Investigate a cluster when its new pages are not discovered, its final responses are wrong or its query coverage stays materially weaker after reasonable recrawl time. Save examples, not just aggregate graphs.

Set an incident response and regression cadence

During the first week, check critical entry points daily and alert on redirect loops, unexpected 404s and 5xx responses. Re-crawl priority legacy URLs weekly during the initial stabilization period, then monthly while meaningful legacy traffic persists. Deploy redirect fixes with tests for case, trailing slash, query parameters and both www and non-www host variants.

Keep redirect rules version-controlled where possible. A content team that renames a destination can accidentally create a new chain after launch. Make destination changes trigger a check of incoming redirects, canonicals and internal links. Record who approved the mapping and what changed so a later developer can understand why the rule exists.

Decision-ready report

Report the percentage of priority legacy URLs ending in a correct 200 destination, number of chains and loops, unresolved high-value URLs, median hops and conversion-path exceptions. Distinguish expected retired pages from genuine errors. Prioritize a broken lead-generating URL above dozens of harmless obsolete tags.

Use the broader website migration guide for pre-launch preparation, and the canonicalization and sitemap QA guides for supporting checks. The goal is not zero redirects; it is direct, relevant, reliable redirects that preserve useful user journeys and clear indexing signals.