Find the quiet dependencies
Start with the sitemap and CMS, then compare them with pages used in campaigns, sales documents and bookmarked workflows. Include downloads, translated versions, confirmation pages and form destinations. A route that is absent from the main navigation can still be important to the business.
Assign an outcome to each URL
Each row needs an intended outcome: keep the route, move to an equivalent page, merge overlapping material or retire it deliberately. Name the content owner and the check that will prove the result. Avoid sending every removed page to the homepage: it rarely answers the original visitor’s question.
Verify the route and the task
After launch, check both the HTTP outcome and what the person can do. A page may return success while showing the wrong language, omitting a download or losing a form integration. Use the inventory as the acceptance list and retain evidence for exceptions instead of declaring the migration complete from a screenshot.