A well-built redirect map protects valuable URLs, organic visibility and user journeys during a site migration. This reusable template and pre-launch checklist shows how to collect the right URLs, choose suitable targets and validate every 301 redirect before and after launch.
Overview
A redirect map is the controlled record of what should happen to each old URL when a website changes domain, platform, URL structure, navigation or content. It is more than a list of redirects: it explains why a URL is changing, where it should go, which HTTP status code applies and how the result will be tested.
For most permanent migrations, the expected implementation is a server-side 301 redirect. A temporary change may call for a 302 redirect, but the status should reflect the intended duration and purpose. Avoid sending every old URL to the new homepage. The best target is normally the closest relevant replacement, while genuinely removed content may need a carefully considered alternative or a direct not-found response.
Use the following columns as a bulk-ready redirect mapping spreadsheet. Copy the header row into Google Sheets, Excel or a CSV file, then adapt the fields to your CMS, hosting platform or deployment process:
old_url,new_url,status_code,reason,priority,organic_clicks,conversions,revenue,referring_links,canonical_target,implementation,status,notes
Column guidance:
- old_url: the complete legacy path, including relevant trailing-slash or case variations.
- new_url: the final intended destination, preferably using the canonical URL format.
- status_code: normally 301 for a permanent move, or 302 where the move is temporary.
- reason: for example, domain change, product replacement, URL restructuring or consolidation.
- priority: high, medium or low, based on traffic, links, conversions and business importance.
- organic_clicks, conversions and revenue: use the available reporting period and record the date range used.
- referring_links: note important external links or the number of referring pages if known.
- canonical_target: confirm whether the target URL is intended to be canonical and indexable.
- implementation: record whether the rule will live in Apache, Nginx, Cloudflare, a CMS or another layer.
- status and notes: use these for review, testing and sign-off rather than changing the original source data.
Keep one untouched copy of the original map and a separate working version. This makes it easier to compare planned, deployed and verified rules during a busy launch.
Checklist by scenario
For every migration
- Define the migration scope. Record whether the change involves a domain, protocol, subdomain, host, CMS, URL structure, content consolidation or several changes at once.
- Export the current URL inventory. Combine a crawl of the live site with XML sitemaps, server logs, analytics landing pages, Search Console exports and important URLs supplied by stakeholders. Include URLs that are not linked in the current navigation.
- Normalise the source data. Separate protocol, hostname, path and query string where useful. Identify duplicate casing, trailing-slash variants, parameter URLs, old subdomains and existing redirects.
- Prioritise the list. Mark URLs with organic traffic, conversions, revenue, strong internal links or valuable external links as high priority. A low-traffic URL can still matter if it is a key campaign or partner destination.
- Assign one final target. Map each important old URL to the closest equivalent new page. The destination should return the intended content and should not itself redirect.
- Choose the status code. Use a permanent status for a genuinely permanent move and a temporary status when the original URL is expected to return or the change is being tested temporarily.
- Remove avoidable hops. Map old URLs directly to final URLs rather than to an intermediate URL that redirects again. This reduces redirect chains and makes testing easier.
- Record ownership and implementation. Note who will add the rule, which layer will process it and when it can be tested.
For a domain or protocol change
- Map the old domain and hostname variants to the corresponding final URLs on the new domain.
- Decide on one preferred format, such as HTTPS and either www or non-www, then make all other variants resolve consistently.
- Check that DNS, certificates, hosting and redirect rules are ready for every relevant hostname before launch.
- Keep the old domain available for the required redirect period and monitor requests to it after release.
For a platform or CMS migration
- Compare the old and new URL patterns before importing content. Do not rely on an automatic slug conversion without sampling the resulting paths.
- Export existing metadata and identify pages that are being merged, retired or split.
- Test redirects outside the CMS where possible, especially if a CDN, web server or load balancer also has rules.
- Check that CMS-generated canonicals, XML sitemaps and internal links use the new URLs rather than the old ones.
For a site restructure or content consolidation
- Group old URLs by topic and identify the single best replacement for each group.
- Do not redirect unrelated pages merely to avoid a 404. A relevant destination is more useful than a generic one.
- Review internal links, navigation, hreflang where applicable and structured data so they point directly to final URLs.
For implementation choices, compare the practical differences between Apache, Nginx, Cloudflare and WordPress redirects. The correct location depends on your stack and rule ownership.
What to double-check
Before launch
- Confirm that every high-priority old URL has either a relevant final target or a documented reason not to redirect.
- Check that target URLs return the expected success response, use the preferred protocol and do not require an avoidable redirect.
- Look for source URLs that already redirect. Resolve them to their final destination before adding new rules.
- Review rule order. A broad rule placed above a specific rule may capture requests unexpectedly.
- Check for conflicting rules across the application, web server, CDN, hosting panel and domain provider.
- Confirm that redirect rules preserve required path components and do not accidentally duplicate, drop or expose query parameters.
- Prepare a rollback copy of the previous configuration and agree how it will be restored if the migration causes a serious fault.
At launch
- Test representative URLs from every old URL pattern, not just a handful of manually selected pages.
- Test protocol, hostname, uppercase, trailing-slash and common legacy variants where those forms have existed publicly.
- Run a crawl of the old URL list and record the status code, destination, response time and number of hops.
- Check that no redirect points to a blocked, noindex, missing or irrelevant page.
- Monitor server logs, analytics landing pages and error reports for unexpected spikes in redirects, 404 responses or loops.
A redirect checker can help with individual URLs, while a crawl or scripted request is more suitable for a bulk redirect map. For command-line verification, a request that shows headers and follows redirects can reveal the full path, but use the equivalent command supported by your environment and document the exact test method in the map.
For further validation, see redirect performance testing and the guide to finding and fixing redirect chains and loops.
Common mistakes
- Using only the current sitemap. Sitemaps may omit old, unlinked or parameterised URLs that still receive visits or links. Combine several sources.
- Redirecting everything to the homepage. This hides missing mappings and gives users a poor result. Use a relevant replacement or document why no redirect is appropriate.
- Building chains during a redesign. A rule from the first migration may send a URL to an intermediate path, which then sends it elsewhere. Update the map so each source reaches its final target directly.
- Mixing temporary and permanent rules without a reason. A status code should describe the change, not simply reflect which option is easiest in a plugin.
- Ignoring query strings. Campaign parameters, search filters and legacy tracking parameters can create unexpected matches or open redirect risks. Define which parameters should be preserved, removed or handled separately.
- Testing only in a browser. Browsers cache responses and may hide headers or intermediate hops. Test with a clean request and inspect the complete response sequence.
- Adding rules in several systems. Duplicate logic in a CMS, CDN and web server can cause conflicts. Record one authoritative owner for each rule set.
- Leaving an unsafe destination open. Redirect parameters that accept any external URL can create an open redirect. Only allow approved destinations and review forwarding inputs.
When troubleshooting conflicts, review redirect rule order and precedence. If results differ between tests, also consider cached 301, 302 or 308 responses and follow the steps in the redirect caching guide.
When to revisit
Keep the redirect map as a living migration record rather than a document that is filed away after launch. Re-run it before every domain change, platform migration, major site restructure, seasonal planning cycle or URL consolidation. It is also useful during a quarterly technical SEO audit, particularly when several teams have changed content or infrastructure since the last review.
Refresh the working template when your crawl, analytics, deployment or CDN workflow changes. Recheck server syntax and regular-expression rules when Apache or Nginx configuration changes, and review CDN or CMS instructions after significant platform updates. Testing commands and search-engine documentation can also change, so confirm that the current validation process still reflects your stack.
A practical recurring routine is:
- Export current URLs and compare them with the previous inventory.
- Recalculate priority using the latest available traffic, conversion and revenue data.
- Run the old URL list through a redirect checker or crawler.
- Flag chains, loops, unexpected 200 responses, irrelevant targets and broken destinations.
- Update the map, deploy only reviewed changes and mark each item as tested.
- Save the results with the migration date so before-and-after behaviour can be compared.
Before your next launch, make a copy of the CSV header above, attach the latest URL exports and complete the checklist from top to bottom. A small amount of structured preparation is easier to review than a last-minute collection of redirect rules, and it gives developers, content owners and technical SEO teams one shared record of what should happen.