Redirect mapping connects an old URL to the most relevant current destination when a site changes structure, platform, domain, or content. It should preserve user intent and useful search paths without sending every old page to a generic homepage.
Collect all old URL sources
Use the current crawl, sitemap, analytics, Search Console, server logs, internal links, external references, and known campaign URLs. Include valuable pages that are not linked in the current navigation.
Choose the best destination
Map each old page to the closest current page by topic, service, product, location, or task. If no relevant replacement exists, document whether the old page should return a not-found or gone state instead of creating a misleading redirect.
Record the mapping reason
Keep old URL, new URL, redirect type, source, intent, reason, owner, status, and test result. A reason helps future editors understand whether a mapping is a consolidation, rename, replacement, or temporary path.
The redirect audit checklist and technical SEO release checklist cover launch QA.
Prevent chains and loops
Resolve each old URL directly to the final destination when possible. Test for redirect chains, loops, mixed protocols, incorrect hostnames, case differences, trailing-slash behavior, and query parameters that create a second redirect.
Check content and intent
Open representative redirects as a visitor and confirm that the destination answers the same question or clearly explains the change. A technically valid redirect can still frustrate people when the page intent does not match.
Test internal and external paths
Update internal links, canonical tags, feeds, sitemaps, structured data, emails, campaigns, and important external references when the URL changes. Test a sample from every page type and priority group.
Monitor after launch
Watch crawl errors, redirect hits, destination engagement, 404s, index coverage, and traffic to important old URLs. Keep the mapping file as operational documentation instead of deleting it after launch.
Redirects technically work but visitors land on the wrong pages? Ask Vertinus to map the migration by intent and evidence.