Technical SEO

Migration Redirect Map Template

A reusable redirect mapping template for SEO migrations, redesigns, URL changes, content consolidation, and platform moves.

A redirect map protects users and search signals when URLs change. It should be built before launch, tested on staging, and monitored after release.

Do not map every old URL to the homepage. Map each old URL to the closest useful destination, or choose a cleaner removal status when no replacement exists.

Download the working file: Migration redirect map template CSV.

Redirect map fields

FieldNotes
Old URLFull current URL before migration.
Old status200, redirect, noindex, canonicalized, 404, or other.
Old page typeProduct, category, service, guide, location, tool, asset, tag, parameter.
Current valueTraffic, impressions, links, conversions, or business importance.
New URLFinal destination URL.
Mapping decisionKeep, redirect, consolidate, noindex, 404, 410, or investigate.
Match qualityExact, close, partial, weak, no match.
Redirect typeUsually permanent for moved content.
Internal links updatedYes, no, or pending.
Sitemap updatedYes, no, or pending.
TestedYes, no, or pending.
NotesRisks, dependencies, owner, or launch issue.

Match quality rules

Match QualityMeaning
ExactSame content or direct replacement.
CloseSame intent with updated URL or stronger page.
PartialRelated page, but not a perfect replacement.
WeakDestination may frustrate users or act like a soft 404.
No matchBetter to remove, archive, or return an appropriate status.

Weak mappings deserve review before launch.

Testing checklist

  • Top old URLs redirect correctly.
  • Redirect chains are short.
  • No redirect loops.
  • Internal links point to final URLs.
  • XML sitemaps list final canonical URLs.
  • Canonical tags point to final URLs.
  • Analytics and conversion tracking still work.
  • Search Console is monitored after launch.

Keep the redirect map after launch. It becomes the evidence base if traffic drops.

Useful source references