Redirect answer
What does a redirect map include?
A direct answer explaining the fields, checks, and QA columns a migration-grade redirect map needs.
Short answer
A real redirect map includes every old URL, its final new URL, priority source, intended status, destination status, chain or loop check, canonical check, internal-link update status, and launch QA result. A two-column old-to-new spreadsheet is a start, not a migration-grade redirect map.
The old URL list should come from a crawl, sitemap, Search Console, analytics, backlinks, and CMS exports.
Every destination should be tested for 200 status, self-canonical behavior, indexability, and content match.
The map should separate must-preserve traffic URLs from low-value URLs, but it should not ignore the long tail.
Basic redirect sheet vs migration-grade map
| Option | What it covers | Risk to watch |
|---|---|---|
| Basic redirect sheet | Old URL and new URL columns only. | Misses chains, status mismatches, homepage catch-alls, and high-value old URLs. |
| Migration-grade redirect map | Adds source, priority, status, destination QA, canonical QA, chain checks, and implementation owner. | Takes longer to build, but prevents silent traffic loss after launch. |
| Post-launch QA export | Confirms old URLs resolve to final canonical pages and records failures for the fix queue. | Without this pass, teams assume redirects work because the rules were uploaded. |
Minimum columns to include
- 1Old URL, new URL, redirect status, destination status, and final URL after redirects.
- 2Priority source: GSC clicks, GA4 sessions, backlinks, sitemap, product/category inventory, or manual page type.
- 3Content match note so old service, product, category, and article URLs do not all collapse to the homepage.
- 4Chain or loop status, canonical status, robots/noindex status, and internal-link update status.
- 5Owner, implementation status, QA date, and final launch result.
Official source checks
Need the answer applied to your site?
SEOParity turns the crawl, Search Console, redirect, canonical, sitemap, schema, and analytics evidence into a developer-ready fix list.