Redirect mapping template

WEBSITE MIGRATION

A redirect map records where an old page should lead and why. Build it before changing URLs so valuable pages, links and visitor journeys have an explicit destination.

Download redirect mapping CSV

Import the UTF-8 CSV into your spreadsheet app using comma-separated columns. Save a working copy and replace the fictional example rows.

Start with the pages people already use

1. Combine your CMS inventory with sitemap URLs, analytics landing pages, Search Console pages and known external links. Include important images or downloads if their URLs will change.
2. Keep unchanged URLs where practical. For every changed URL, select the closest useful replacement and record the reason.
3. Assign one owner to review content equivalence and another to implement the redirect. Resolve unknown destinations before launch.
4. For permanently moved pages, plan server-side 301 or 308 redirects directly to the final destination. Avoid chains, loops and blanket homepage redirects.

A filled example

These fictional URLs illustrate decisions, not a ready-to-import server configuration.

What the worksheet records

Source URL, current status, destination, planned action, reason, inbound-link priority, owner, validation status and notes. “Review removal” is a decision queue, not an instruction to redirect irrelevant pages.

Validate the implementation

• Request each source URL and record its actual response and final URL.
• Confirm destinations are accessible and contain the expected content. Check loops and intermediate hops.
• Update internal links, navigation, canonicals and sitemaps to final URLs.
• After launch, review crawl errors and traffic changes alongside the migration record. A redirect alone cannot guarantee preserved rankings.

Reference: Google’s site move guidance.

Pair this map with the SEO page inventory and launch checklist.