A well-maintained redirect map turns a complex website migration into a controlled, testable process. This practical 301 redirect mapping template shows what to record, how to choose destinations, which status codes to use, and how to monitor the result after launch so that redirect decisions remain useful beyond migration day.
Overview
Redirect mapping is the process of matching each old URL with the most appropriate new URL before a website, domain, platform, or URL structure changes. The finished map becomes the working specification for implementation, testing, reporting, and future maintenance.
The central rule is simple: redirect an old URL to the closest relevant live destination. A product page should normally point to its replacement product page, not to a broad category or the homepage. If no genuinely suitable replacement exists, a carefully considered 404 or 410 response may be more useful than sending visitors and search engines to an unrelated page.
For most permanent changes, a server-side 301 redirect is the usual choice. A 302 redirect is intended for a temporary change where the original URL is expected to return. Choosing between these status codes is part of the mapping decision, not an implementation detail to leave until after launch.
Keep the map in a spreadsheet or structured file that can be reviewed by technical, content, and analytics teams. For larger migrations, use a consistent format that can also support a bulk redirect upload. The website migration redirect checklist can be used alongside the map for wider launch planning.
What to track
A useful redirect mapping template records enough context to explain each rule and verify it later. At minimum, include these columns:
- Source URL: the complete old path, including the hostname where relevant. Record the canonical version rather than relying on memory or a partial path.
- Destination URL: the intended final URL, preferably using the final protocol, hostname, path, and slash convention.
- Redirect type: normally 301 for a permanent migration, or 302 when the change is genuinely temporary.
- Reason: such as domain change, HTTP to HTTPS, URL restructuring, product replacement, consolidation, or removal.
- Source category: product, service, article, landing page, media file, filter page, or another meaningful group.
- Priority: high-priority URLs can include pages with strong backlinks, meaningful organic visits, important conversions, or prominent internal links.
- Owner and status: identify who reviewed the row and whether it is proposed, approved, implemented, tested, or rejected.
- Validation result: record the response code, final URL, test date, and any error such as a loop, chain, broken destination, or unexpected query-string behaviour.
Start the source inventory with more than the current XML sitemap. Include URLs found in analytics, server logs, backlink tools, internal links, redirects already in place, paid campaigns, email messages, QR codes, and important external references. Crawl both the old and new sites where possible.
For each source, apply a destination decision in this order:
- Use the direct replacement if the content has moved without changing its purpose.
- Use the closest equivalent page when several old URLs have been consolidated.
- Use a relevant category or hub only when it genuinely satisfies the original visitor intent.
- Leave the URL without a redirect when no useful replacement exists, then make sure the resulting not-found response is intentional and helpful.
Do not automatically redirect every unknown path to the homepage. That approach can hide mapping errors, create poor user journeys, and make post-launch diagnosis harder. For query parameters, decide whether values should be preserved, removed, or handled by a separate rule. The guide to redirects and query parameters covers this decision in more detail.
Cadence and checkpoints
Redirect mapping should be checked at defined points rather than treated as a one-off spreadsheet exercise. Use this schedule as a practical baseline, then adjust it to the size and risk of the migration.
Before implementation
Remove duplicate source rows, normalise hostnames, and confirm whether paths are case-sensitive on the server. Check trailing-slash and uppercase variants if the old site exposed them. Confirm that every destination is intended to be indexable and is not itself scheduled for removal. Review the redirect mapping template guide when assigning ownership and approval states.
During staging tests
Test representative rows from every rule group, including direct page moves, consolidated pages, domain forwarding, HTTP to HTTPS, www to non-www, language paths, query parameters, and missing destinations. A redirect checker should show the expected status code and a single final destination. Test both the old URL and common variants where those variants may still receive links.
At launch
Run a prioritised smoke test immediately after the rules are published. Check the homepage, key templates, high-value landing pages, old campaign links, important documents, and a sample of lower-priority URLs. Crawl the old URL list in batches if the migration is large. Record failures in the map instead of fixing them informally, so there is a durable audit trail.
After launch
Review redirect requests, crawl errors, analytics landing pages, search performance signals, and server logs at least daily during the initial monitoring period. Once traffic and errors settle, move to a weekly review and then a monthly or quarterly maintenance cycle. A redirect rule that is technically correct can still become obsolete when content is renamed or removed later.
How to interpret changes
A successful status code alone does not prove that a migration is working. Interpret the response together with the destination, traffic pattern, and user intent.
- 301 followed by 200: usually indicates a direct permanent redirect to a live page. Check that the destination is relevant and final.
- 301 followed by another 301: this is a redirect chain. Update the original rule so it points directly to the final URL where practical.
- Repeated redirects or a browser error: this may be a redirect loop, often caused by conflicting protocol, hostname, slash, or application rules. Isolate each rule layer and test again.
- 301 to a 404 or 410: review whether the source should have a better replacement or whether the redirect should be removed.
- 302 on a permanent move: confirm the intended change with the owner. A temporary status may be appropriate during testing, but it should not remain by accident.
- Traffic falling for a group of mapped URLs: compare destination relevance, internal links, canonical tags, content changes, and crawl accessibility before assuming the redirect itself is the only cause.
Keep canonicalisation and redirects aligned. A canonical tag can consolidate signals for similar accessible pages, but it is not a substitute for redirecting a URL that has permanently moved. Likewise, do not add multiple redirect rules merely to match every possible spelling if one carefully designed normalisation rule can handle the requirement safely. For related cases, see the guidance on uppercase-to-lowercase redirects and trailing-slash standardisation.
When to revisit
Revisit the redirect map at three useful intervals: immediately after a migration, on a monthly or quarterly maintenance cycle, and whenever a related site change occurs. The maintenance review should cover new 404s, unexpected redirect chains, rules with little or no remaining traffic, destinations that now return errors, and campaign links that still use an old domain or path.
Update the map when the CMS, hosting platform, domain, URL convention, international structure, or analytics tagging changes. International sites need particular care: a language or country variant should not be redirected solely because it is different. Review whether hreflang or a redirect better represents the user and content relationship. Location-based rules should also be tested carefully because automatic geo redirects can affect crawling and user choice.
Before closing each review, complete this short action list:
- Export new source URLs from crawl, analytics, and server data.
- Compare them with the current map and investigate unmapped high-value requests.
- Test a sample of every redirect rule group with a redirect checker.
- Remove or revise chains, loops, stale temporary redirects, and broken destinations.
- Confirm that campaign and QR code links still preserve their intended tracking parameters.
- Save the revised file with a date, change summary, and reviewer.
A redirect map is most valuable when it remains a living operational record. Schedule its next review before the current one ends, and use the redirect rule testing checklist whenever new rules are introduced. That routine makes future migrations faster to plan and gives developers a clear, testable source of truth.