A well-maintained redirect map helps protect organic visibility when URLs, domains, subdomains, platforms, or site taxonomies change. This guide explains how to build an SEO migration redirect map, what to record in a 301 redirect spreadsheet, how to validate implementation, and which signals to monitor after launch.
Overview
An SEO site migration redirect map is the working record that connects old URLs to their intended destinations. It should be created before launch, used to guide implementation, and retained for post-launch testing. The goal is not to redirect every old URL to a homepage. The goal is to preserve the clearest available relationship between an old address and a useful, equivalent replacement.
Redirect mapping is especially important during a domain change, redesign, CMS replatforming, HTTP-to-HTTPS move, subdomain migration, or taxonomy update. A URL that disappears without a suitable response can lose accumulated relevance, links, bookmarks, and referral traffic. A poorly chosen destination can create a poor user experience or leave search engines with an unclear replacement.
Use this process alongside a broader technical SEO release checklist. A redirect map is one control within a migration plan; it does not replace checks for indexability, canonicals, internal links, structured data, rendering, or performance.
For each source URL, decide whether it needs a one-to-one redirect, a pattern-based redirect, a valid alternative response, or no redirect at all. Record the decision and its owner so that unresolved rows do not disappear into a launch checklist.
What to track
1. Build a complete URL inventory
Start with more than the current XML sitemap. Combine URLs from the existing sitemap, crawl data, server logs if available, analytics landing-page reports, Google Search Console performance data, backlink tools, CMS exports, and known campaign or documentation URLs. Deduplicate the list while preserving useful source information.
Include URL variants that may be treated differently by the server, such as HTTP and HTTPS, www and non-www hosts, trailing-slash variations, uppercase paths, parameterized URLs, and legacy folders. If a URL has valuable links or recurring visits but is absent from the sitemap, it still belongs in the migration review.
2. Use a reusable redirect mapping template
A spreadsheet is usually sufficient for planning and review. Add one row per source URL, or document a clearly defined pattern when thousands of URLs follow the same rule. Use columns such as:
| Column | Purpose |
|---|---|
| Old URL | The complete source address, including its current protocol and host. |
| Replacement URL | The most relevant destination after migration. |
| Redirect type | Usually a permanent redirect for a permanent move; record exceptions explicitly. |
| Expected status code | The response the source should return, such as 301 or 410 where appropriate. |
| Canonical target | The canonical URL expected on the destination page. |
| Pattern or rule | The rewrite logic used when several source URLs share a structure. |
| Priority | For example, high for pages with links, traffic, conversions, or strategic importance. |
| Owner | The person responsible for implementation or validation. |
| Validation date | When the row was last tested. |
| Observed status | The status and final URL found during testing. |
| Notes | Document exceptions, removed content, query parameters, or unresolved decisions. |
Keep the original URL in a stable, normalized format, but do not remove meaningful query parameters until their treatment has been decided. A source URL that redirects to another redirect is not complete mapping; the intended final destination should be recorded directly wherever possible.
3. Choose the correct mapping type
| Situation | Preferred approach | Review point |
|---|---|---|
| One page has a direct replacement | One-to-one permanent redirect | Confirm the replacement serves the same or closely related intent. |
| A folder or slug changes consistently | Pattern-based redirect | Test representative URLs, including edge cases and old exceptions. |
| Content is merged into another page | Redirect to the consolidated page | Check that the destination covers the important information from the source. |
| Content has no useful replacement | Return an intentional not-found or gone response where appropriate | Do not force unrelated URLs to the homepage. |
| HTTP, HTTPS, or host changes | Map each old variant to the final preferred URL | Confirm there is one final protocol, host, and path format. |
Use permanent redirects for permanent URL changes, but verify the exact implementation options supported by the web server, CDN, CMS, or hosting platform. For implementation examples, keep the rule simple and testable. An Apache-style rule might look like Redirect 301 /old-path/ https://www.example.com/new-path/; a platform may instead require a CMS redirect entry or edge rule. Treat examples as syntax patterns, not drop-in instructions for every stack.
Cadence and checkpoints
Before implementation
- Export and normalize the old URL inventory.
- Identify high-priority URLs using traffic, conversions, links, search visibility, and business importance.
- Compare the old and new URL structures.
- Assign a destination or an intentional non-redirect outcome for every important source.
- Review pattern rules against exceptions and manually mapped URLs.
- Share the map with development, content, analytics, and whoever owns the launch.
Do not wait until launch day to discover that a new taxonomy has no destination logic. If the new site is still changing, version the spreadsheet and mark rows as proposed, approved, implemented, or validated.
During staging validation
Test the redirect rules in a staging environment when possible, or use a controlled test set before changing production behavior. Crawl the old URL list and record the status code, redirect hops, final URL, canonical target, and page content. Test both representative pattern URLs and known exceptions.
Important checks include:
- Old HTTP URLs reach the intended final HTTPS URL.
- Old hostnames reach the final preferred hostname.
- Source URLs do not produce redirect chains or loops.
- Redirects do not point to irrelevant pages or generic error pages.
- Destination pages return a successful response and are eligible for indexing when intended.
- Canonical tags agree with the final URL.
- Internal links point directly to current URLs rather than old addresses.
At launch and after launch
Keep the old URL inventory available for immediate crawling after release. Run a crawl that follows redirects, then export failures and unexpected destinations back into the spreadsheet. Update the validation date and owner for each tested group.
Replace the XML sitemap with the new canonical URLs. Update navigation, templates, hreflang references if used, structured data references, feeds, and important internal links. A useful internal linking strategy review can identify links that still rely on the old structure.
Use Google Search Console to compare the migration baseline with post-launch clicks, impressions, indexed pages, and reported errors. Pair that data with GA4 landing-page and conversion reports; the GA4 and Google Search Console reporting template provides a practical framework for joining those views.
How to interpret changes
Not every fluctuation means the redirect plan failed. First separate technical errors from expected changes. A drop in sessions may reflect seasonality, tracking changes, content removal, ranking movement, or a destination that no longer matches the original intent. A rise in 404s, redirect errors, or excluded pages is more directly useful for finding migration defects.
Prioritize investigation in this order:
- Server and redirect failures: Look for 5xx responses, redirect loops, timeouts, and unexpected 4xx responses on important old URLs.
- Wrong destinations: Check whether a source redirects to a page that answers a different question or serves a different product, category, or language.
- Chains: Change old-to-intermediate-to-final paths into direct old-to-final mappings where feasible.
- Canonical conflicts: Confirm the destination does not canonicalize to another URL unintentionally.
- Internal-link leakage: Find links, canonicals, sitemaps, and structured data that still reference retired URLs.
- Content gaps: Determine whether important old pages were removed without a genuinely useful replacement.
Compare groups, not only sitewide totals. Segment by directory, template, language, device, traffic source, and priority. If one product folder performs normally while one blog or documentation pattern generates errors, the problem may be a specific rule rather than the migration as a whole.
For JavaScript-heavy sites, verify that links and important page content are present in the rendered output as well as the initial HTML. The JavaScript SEO audit guide can support that part of the review. Also check crawl waste from unnecessary parameters or repeated redirects using a crawl budget audit workflow.
When to revisit
Keep the redirect map as a living migration record rather than archiving it immediately after launch. Review it daily during the first launch period if the site is large or business-critical, then move to a weekly review until error patterns stabilize. A monthly or quarterly check is useful afterward, especially for sites that regularly publish, retire, or reorganize content.
Reopen the map whenever you:
- Change domains, subdomains, protocols, or primary hostname settings.
- Replatform the CMS, server, CDN, or routing layer.
- Rename categories, folders, products, documentation sections, or blog paths.
- Merge, retire, or substantially rewrite high-value pages.
- See a new cluster of 404s, redirect chains, indexed duplicates, or traffic losses.
- Acquire a site or consolidate multiple properties.
- Change analytics, consent, or tracking implementation and need a fresh baseline.
For a practical recurring workflow, export new 404s and redirected requests, add them to the spreadsheet, assign an owner, and record the final decision. Then crawl a sample of every active rule and compare Search Console and analytics data with the previous period. A content change may require a redirect decision as well; use the content refresh workflow when deciding whether a page should be updated, merged, or retired.
Before closing each review, confirm four things: important old URLs have an intentional outcome, current internal links use final URLs, the sitemap contains only intended canonical URLs, and the next validation date is assigned. That small discipline turns a one-time 301 redirect spreadsheet into a repeatable SEO migration control.