On this page10 sections
Why the redirect map deserves its own review
A content migration is usually planned around the new pages, templates, and publishing schedule. The redirect map receives less attention because it looks like a technical appendix. That is a mistake, because the map decides what a visitor and a search engine see when they follow an old link. A missing or misdirected redirect turns a carefully planned migration into a set of dead ends. A short review before launch checks the map as a product surface, not as a developer detail.
Start from a complete source inventory
Export the URLs that currently receive traffic, links, or paid spend. Include pages with internal links, external backlinks, campaign parameters, and search impressions. De-duplicate the list but keep the original variants so a redirect can still catch them. Record the export date and the source tool. A map built only from the sitemap will miss pages that rank, pages that are linked from partners, and pages that still receive paid traffic long after the campaign ended. The inventory is the scope of the review.
Match each source to a real destination
For each source URL, confirm that the destination exists, returns a successful status, and answers the same intent. A redirect to the homepage is technically valid but often unhelpful; it tells the visitor the page is gone without offering a replacement. Group the sources by intent and map them to the closest successor page. Where no good successor exists, decide whether to keep the old page, merge its content, or return a clear not-found response rather than a soft landing that disappoints.
Check for chains and loops
Follow each redirect through its full chain and confirm it resolves in one hop. Chains slow navigation and can break when an intermediate page changes. Loops are worse: they leave the visitor on an error page after several redirects. Test the map with the staging environment and with a link checker that follows redirects. Record any chain longer than one hop and any loop. A clean map resolves every source directly to its destination, including the case where the destination later receives its own redirect.
Verify the status codes
Confirm that permanent moves return a permanent redirect and temporary moves return a temporary one. A temporary campaign detour should not be marked permanent, and a permanent consolidation should not silently use a temporary code. Check the response for the exact source URL, including trailing slashes, uppercase variants, and query strings. Record the observed status code for each case. A map can look correct in a spreadsheet while the server returns a different code because a rule takes precedence.
Preserve campaign and query parameters
Redirects can strip query parameters, which breaks attribution and landing-page behavior. Test a source URL with a campaign parameter and confirm that the destination receives the parameter or that the team has decided to drop it on purpose. Check the same for tracking links used in paid ads and partner placements. If a parameter must be preserved, verify the rule passes it through. A migration that loses parameters can make a working campaign look like direct traffic for weeks.
Review the internal links separately
The redirect map handles incoming links, but the site's own internal links should point directly at the new URLs. Crawl the new site and list internal links that still point to old paths. Each one is an avoidable redirect and a sign that a template or content block was missed. Update the links at the source rather than relying on the map. Keep a short list of intentional exceptions, such as links inside archived content that should not be edited.
Test the high-value pages by hand
Automated checks catch most errors, but a few pages deserve a manual pass. Test the top organic pages, the pages with the most external links, and the pages used in active campaigns. Open each source URL in a fresh browser, follow the redirect, and confirm the destination renders correctly on desktop and mobile. Check that the page title, visible date, and primary call to action make sense for the visitor who arrived from the old link. Record the result for each page.
Prepare the rollback and monitoring
Decide what happens if the map causes a problem after launch. Keep the old map and the old pages available long enough to restore a rule or revert a destination. Record who can make the change and how quickly. Set up monitoring for 404s, redirect chains, and sudden drops in organic entrances to the migrated sections. A rollback plan is not a sign of doubt; it is what lets the team launch on schedule without pretending the map is perfect.
Review the map again after launch
After the migration, compare the actual redirect behavior with the reviewed map. Look for new 404s, chains that appeared when destinations changed, and sources that were missed. Update the map and the internal links. Record what the review caught and what it missed so the next migration benefits. The redirect map is a living asset during the transition, not a one-time export. A short post-launch review keeps it accurate while the old URLs are still in use.