Content cleanup often creates a second task: deciding what should happen when old URLs disappear. A redirect map records those decisions before changes are implemented, reducing broken journeys and preventing broad, poorly matched redirects from becoming the default.
Start with the exact URLs being changed
Build the map from the verified set of pages that will move, merge or be removed. Avoid using an old sitemap as unquestioned truth. The working list should correspond to the actual cleanup decisions.
Classify what happened to each page
Record whether the content has a direct replacement, has been consolidated into a broader resource or no longer has a meaningful equivalent. This classification makes the redirect decision easier to defend and review.
Choose destinations by reader continuity
Ask where someone following the old URL would reasonably expect to arrive. A closely related replacement can preserve the journey; an unrelated category or homepage often cannot. If there is no useful equivalent, do not manufacture relevance.
Check for redirect chains
Existing sites may already contain redirects. Where practical, map old URLs directly to the current intended destination rather than creating unnecessary intermediate hops. Review the actual implementation because historical rules may differ from documentation.
Update internal links as part of the cleanup
Redirects should not become a substitute for maintaining the site's own links. Change navigation and contextual links to point directly to surviving destinations, particularly where retired pages were linked frequently.
Verify the implemented map after release
Test representative and important URLs, confirm destinations and investigate unexpected responses. Keep the map as a record of intended behaviour so implementation defects can be distinguished from deliberate retirement decisions.