A reliable redirect map turns a risky website migration into a controlled SEO project. This guide provides a reusable spreadsheet structure, practical mapping rules, priority scoring, launch checks, and a monitoring routine for domain changes, URL restructures, redesigns, and platform migrations.
Overview
A redirect map is the working record of how each important old URL will lead to its corresponding new URL. It should be prepared before launch, reviewed by the people responsible for content and SEO, tested in a staging or controlled environment, and retained after the migration for troubleshooting.
The usual default for a permanent migration is a 301 redirect. It tells browsers and search engines that the old address has been replaced. A temporary move may call for a 302 or 307, but using a temporary status for a permanent change can create confusion about the intended destination. Avoid relying on meta refreshes or JavaScript redirects when a server-side rule is available.
A good redirect map does more than list old and new addresses. It records why a URL matters, what should happen to it, whether the destination has been tested, and who owns the decision. For a broader planning framework, see the Website Migration URL Mapping Template and the SEO-friendly migration and redirect checklist.
A reusable spreadsheet structure
Use one row per source URL. The following columns are sufficient for most migrations:
- Source URL: the complete old address, including the path and relevant query-string notes.
- Destination URL: the single preferred new address.
- Redirect type: normally 301 for a permanent move; document any exception.
- Page type: product, service, article, category, resource, campaign, or another useful label.
- Priority: high, medium, or low based on traffic, conversions, links, and business value.
- Reason: renamed, consolidated, removed, platform change, domain change, or another explanation.
- Owner: the person accountable for approving the destination.
- Status: proposed, approved, implemented, tested, or live.
- Validation notes: status code, final URL, chain or loop findings, and follow-up actions.
What to track
Build the source URL inventory
Start with more than the current XML sitemap. Combine the site crawl with analytics landing pages, search performance data, server logs where available, backlink exports, internal links, campaign links, and known legacy URLs. Include URLs that currently return an error if they have external links or a clear replacement.
Normalize the inventory before mapping it. Decide how to treat uppercase and lowercase paths, trailing slashes, URL-encoded characters, HTTP and HTTPS versions, www and non-www hostnames, and common tracking parameters. Keep the original discovered form in a notes column if normalization could hide a real request pattern.
Choose one-to-one destinations first
The strongest mapping is usually one old URL to one closely matching new URL. Preserve the page's subject, intent, and useful content wherever possible. For example, an old guide about a specific product feature should point to the replacement guide or feature page, not automatically to the homepage.
Use many-to-one mapping only when several old URLs genuinely represent the same topic or have been intentionally consolidated. A group of near-duplicate category pages may point to one replacement category. However, redirecting every deleted page to a broad homepage or unrelated section can create a poor user experience and weak relevance. If no reasonable replacement exists, returning a deliberate 410 or 404 may be more accurate than forcing a redirect.
Score priority before implementation
Priority helps teams test the highest-risk rows first. Mark a URL as high priority when it has one or more of these characteristics:
- It receives meaningful organic, referral, or direct visits.
- It supports leads, sales, subscriptions, or another important conversion.
- It has valuable backlinks or is frequently cited externally.
- It is a key category, product, service, navigation, or campaign destination.
- It is likely to be requested by customers after the launch.
Medium-priority URLs may have limited traffic but remain useful for topical coverage or internal navigation. Low-priority rows can include obsolete URLs with no meaningful visits or links, but record the decision rather than silently omitting them. This approach makes it easier to protect important signals during an old-domain move and to fix broken backlinks after launch.
Cadence and checkpoints
Before launch
- Freeze the source inventory and mark the date it represents.
- Review every high-priority row with a content or business owner.
- Confirm that each destination is live, indexable where appropriate, and not itself scheduled for removal.
- Check for accidental chains, such as an old URL pointing to an intermediate URL that redirects again.
- Test representative rules for the chosen implementation: Apache, Nginx, Cloudflare, WordPress, or another platform.
- Prepare an exception list for URLs that should return a 404 or 410 instead of redirecting.
Use a bulk redirect testing process when the map is large. At minimum, test successful matches, missing sources, URL variants, query strings, encoded characters, and the canonical host and protocol.
Launch day
Deploy redirect rules as part of the migration sequence, not as an afterthought. Confirm DNS, hosting, certificates, application routing, and canonical settings in the intended order. Crawl a sample of old URLs immediately and record the HTTP status, final destination, number of hops, and any loop.
Keep the old-to-new map accessible to the support and development teams. It provides a fast reference when users report an old bookmark, an email link, a QR code, or a campaign URL that no longer behaves as expected.
After launch
Review the redirect map daily during the initial monitoring period, then move to a weekly review while traffic stabilizes. After that, a monthly or quarterly audit is usually practical, with a deeper review after releases, content pruning, domain changes, or major URL restructures. Compare newly discovered 404s, redirect requests, crawl findings, landing-page behavior, and important backlink destinations against the map.
How to interpret changes
A rise in 404s does not automatically mean every missing URL needs a redirect. First group the errors by source, referring page, request volume, and user intent. A single popular old URL deserves more attention than hundreds of random requests with no traffic or useful links.
Look for patterns rather than isolated rows:
- Many old URLs point to one irrelevant page: revisit the consolidation logic and create more specific destinations where possible.
- Redirect chains increase: update old rules so they point directly to the final canonical URL.
- Redirect loops appear: compare application routing, HTTP-to-HTTPS rules, www preferences, and trailing-slash logic. Remove competing rules before changing more destinations.
- Important backlinks lead to errors: add or correct a focused 301 redirect, then update internal links and outreach records where practical.
- Traffic falls for mapped pages: verify that the destination matches the old intent, the page is accessible, analytics is measuring the new address, and no indexing or canonical issue was introduced.
Do not use a redirect to solve every canonicalization problem. A redirect removes or replaces an address, while a canonical link indicates a preferred version among accessible alternatives. Review protocol, hostname, slash, parameter, mobile, language, and duplicate-content rules together. For recurring problems, use the redirect audit checklist or the more detailed URL redirect audit guide.
Also inspect security implications. User-controlled redirect parameters can create an open redirect vulnerability, particularly on short links, login flows, and campaign tools. Validate allowed destinations and review unexpected forwarding behavior using the open redirect prevention guide.
When to revisit
Keep the redirect map as a living migration record rather than archiving it immediately after launch. Revisit it on a monthly or quarterly cadence, and sooner when recurring data changes. Useful triggers include a redesign, CMS or hosting migration, domain or brand change, content consolidation, a new country or language structure, a change in mobile URL handling, or a spike in crawl errors.
At each review, export new 404s and redirect requests, compare them with the existing source list, test high-priority destinations, and remove rules that are obsolete only when you have evidence they are no longer needed. Before retiring a rule, check historical traffic, external links, internal references, campaign materials, and QR code destinations. Update the owner and notes for every changed row.
For a practical next step, copy the spreadsheet fields in this article, build the source inventory, and label the first 20 high-priority URLs. Map those URLs one-to-one where possible, test the rules in bulk, and establish the next monthly review date before launch. A small, maintained redirect map is more useful than a large list that no one validates.