How to approach it
Export old landing pages and list direct destinations serving the same purpose. Compare inventory and content, then identify repeated sources and paths that redirect again. Verify the deployed response and final page.
Check the old URL’s purpose before picking the destination. An older product may have accumulated links because its manual is useful, while a category URL may attract buyers comparing multiple models. Use the exact old URLs from search reports and relevant referring links. Include historical case and trailing-slash variations if the old host treated them differently.
Worked example
If /old-a points to /old-b and /old-b points to /current, map both old URLs directly to /current if it serves both requests.
How to verify the change
Run the map checker before import, then verify what the server actually does. Include the expected redirect status and final response in your test. A map can be clean while a host rule sends the request somewhere else. Update internal links to the final page and retain the export and test log.
When an old destination is retired again, update any redirects that pointed to it. The original source list is useful here because an ordinary navigation crawl may never discover historical URLs that visitors still reach from other sites.