Website migration & redirect planner
Map old URLs to new destinations, identify missing mappings and prepare a practical migration checklist.
What is this tool for?
A website migration changes where content lives or how it is delivered. A redirect map connects an old page with its closest relevant replacement, helping visitors and crawlers find the new destination. Use this planner before a redesign, domain move or content restructure. If URLs remain the same, you may not need redirects, but content, crawlability and monitoring still need attention.
How it works
- Each mapping must contain an absolute HTTP or HTTPS old URL and destination, without credentials or fragments. Blank destinations need a decision. No URLs are fetched.
- Flag duplicate sources, self redirects, mapped chains and cycles. Multiple old pages may legitimately share one relevant replacement; review rather than automatically reject that choice.
- The checklist combines your change type with backup and monitoring answers. A valid map does not install redirects or verify response codes.
A worked example
Illustration: /services-old/ /services/ /solutions/ creates a chain. Map the original page directly to the final relevant destination, then verify the deployed status and destination. A removed page without a relevant replacement may appropriately return 404 or 410.
What the results do—and do not—tell you
No ranking preservation guarantee. Redirect behaviour, canonicals, internal links, XML sitemaps, analytics, robots rules and live response codes must be verified separately. This tool exports a review map, not server configuration. Do not redirect every removed page to the homepage.
What to do next
Agree the final mapping, record a rollback point and assign someone to monitor errors, indexing and enquiries after launch.
Supporting guidance
Model and guidance reviewed 10 November 2026. Financial scenarios use GBP; use a consistent VAT basis. No result is a quote or promised outcome.
Explore the relevant Elite Apps service