Review a Redirect Map Before a Migration

Make the mapping explicit

A redirect plan should connect each old URL to a relevant replacement. Use a sheet with one source and one destination per row. If the old page has no useful replacement, record that decision separately rather than mapping every retired page to an unrelated homepage.

Enter the correct base domain when your sheet uses paths such as /old-guide/. The checker keeps the distinction between /guide and /guide/, because your server may treat them differently. It also preserves query strings.

Resolve conflicts before deployment

1. Check repeated sources. The same old URL should not have two competing destinations.
2. Remove self redirects and loops, including loops that pass through several intermediate URLs.
3. Review chains. Where appropriate, map the old URL directly to the final relevant destination.
4. Confirm that the replacement page exists and answers the visitor’s original need.
5. Save the reviewed map and a record of where it will be implemented.

Test the live responses afterwards

The map checker follows only the rows you provide. It cannot see a web server rule, a CMS setting, a CDN redirect or a destination that is unavailable. After implementing the map, test representative old URLs and inspect the actual response and final destination.

Update internal links to the final URLs so visitors do not rely on redirects for everyday navigation. Revisit the sitemap and other references that still use retired addresses. Keep a recovery copy of the original mapping and configuration in case a live test exposes an unexpected result.

Try the workflow

Download the redirect mapping sheet and use the Redirect Map Checker to review a pasted plan. The checker does not install redirects or request the live destinations.