Website Redirect Mapping Template: Plan a Safe URL Migration
site migrationredirect templatetechnical SEOwebsite redesign

Website Redirect Mapping Template: Plan a Safe URL Migration

PPortal Redirect Editorial Team
2026-11-03
7 min read

Use this redirect mapping workflow and spreadsheet structure to plan, test, and monitor a safer SEO migration.

A well-maintained redirect map gives every changed URL a planned destination, a clear implementation rule, and a way to verify the result. Use this workflow and spreadsheet structure to prepare safer website migrations, domain changes, redesigns, and URL restructures, then monitor the map after launch.

Overview

Redirect mapping is the process of matching old URLs to their intended new URLs before a site change goes live. The finished map becomes a shared working document for SEO, development, content, analytics, and release teams. It should explain what happens to each important old address: whether it receives a permanent redirect, remains unchanged, returns a deliberate error, or is excluded because it has no useful replacement.

A redirect map is more than a list of rewrite rules. It records the reasoning behind each decision and provides an audit trail when a destination changes later. This matters during a domain migration, a platform rebuild, a navigation restructure, a change from HTTP to HTTPS, or a move between www and non-www hostnames. It is also useful when a large number of product, service, blog, or category URLs are being consolidated.

For most permanent URL changes, a 301 redirect is the usual status-code choice, provided the old URL has a relevant replacement and the change is intended to last. A temporary change may require a different approach. Avoid selecting a status code simply because it is available in a platform interface; record the reason for the choice in the map.

Start by agreeing the migration scope and freeze a copy of the current URL inventory. Do not rely only on the new sitemap. Gather URLs from the existing sitemap, analytics, search data where available, internal links, backlinks, server logs, and important campaign or QR-code links. The objective is to identify URLs that users, search engines, partners, or tracking systems may still request after launch.

What to track

Use one row per source URL, with consistent formatting and controlled values. The following columns form a practical bulk redirect map:

  • Source URL: the complete old URL, including the hostname and path. Store a canonical version, but note whether query parameters require separate handling.
  • Source pattern: the old folder, product format, or URL rule if multiple URLs can be handled by one pattern.
  • Source status: whether the URL currently returns a successful page, redirect, not found response, or another status.
  • Source importance: a priority such as high, medium, or low, based on traffic, links, conversions, business value, or visibility.
  • New URL: the exact destination, including the preferred protocol and hostname.
  • Match type: one-to-one, many-to-one, pattern-based, unchanged, intentionally removed, or needs review.
  • Redirect status: normally permanent or temporary, with the reason documented for exceptions.
  • Content match: a short note explaining why the destination is the closest relevant replacement.
  • Query-string treatment: preserve, remove, transform, or review. This is important for campaign parameters and application routes.
  • Implementation location: for example, Apache, Nginx, Cloudflare, WordPress, the CMS, or an application router.
  • Owner: the person or team responsible for approving and testing the row.
  • Test result: date tested, returned status, final destination, and any issue found.
  • Post-launch status: live, failed, monitored, superseded, or retired.

Keep the source and destination URL formats consistent. Decide in advance how to handle trailing slashes, uppercase characters, duplicate parameters, URL-encoded characters, and host variants. A redirect that works for one spelling may not cover another. Also document the intended query-parameter behaviour rather than assuming that every parameter should be passed through.

Prioritise rows instead of treating every URL as equally urgent. High-priority rows usually include pages with substantial visits, valuable external links, important conversions, strong internal linking, or a direct role in the migration. Low-priority URLs still need a decision, but they can be reviewed after the critical set has been validated.

Cadence and checkpoints

Use the redirect map at four checkpoints: discovery, pre-launch, launch, and post-launch.

1. Discovery

Build the inventory before development is complete. Compare the old URL set with the proposed new URL set and identify gaps early. Group similar changes, such as a folder move or a product-slug change, but retain representative individual rows for testing. Flag pages that have no obvious destination instead of sending them automatically to the homepage. A generic destination may confuse users and does not explain what happened to the original content.

2. Pre-launch

Complete the map before rules are written. Check that every high-priority source has one intended outcome and that no destination points to a staging hostname, an HTTP address, or another URL that will immediately redirect. This is the right time to inspect for redirect chains and loops. A source should generally resolve to its final, relevant URL in as few steps as the implementation permits.

Test rules in a safe environment where possible. For each sample, verify the status code, Location header, final URL, protocol, hostname, path, query string, and page response. Include tests for URL variations such as HTTP and HTTPS, www and non-www, trailing slash differences, encoded characters, and old campaign links. The redirect rule testing checklist can be used as a separate sign-off document.

3. Launch

Keep a dated copy of the final rules and map. Confirm that the redirect layer is active at the same time as the new site, and check the highest-priority URLs immediately. Review both browser behaviour and raw HTTP responses; a browser may conceal intermediate redirects that a technical check will reveal.

4. Post-launch

Review the map daily during the initial monitoring period if the migration is substantial, then move to a weekly or monthly review once results are stable. Compare requested old URLs with the planned source list. New unplanned requests may reveal missed internal links, external references, malformed rules, or legacy URL formats that were not included in the original inventory.

How to interpret changes

Use the map and technical checks together. A growing number of unexpected 404 or 410 responses may indicate missing mappings, but not every removed URL requires a redirect. First determine whether the URL has a relevant replacement, whether it receives meaningful requests, and whether the removal was intentional. Record the decision so it is not reopened without context.

Unexpected 5xx responses, timeouts, or intermittent failures are more urgent because they can indicate a server, application, or rule-processing problem. A sudden increase in redirect hops suggests that old rules were layered on top of new rules rather than being consolidated. Trace each affected source through every response until you find the first unnecessary hop. Then point the original URL directly to the final destination where practical.

Watch for redirect loops caused by conflicting protocol, hostname, trailing-slash, or application rules. Test the exact URL variants that users may request, not only the preferred canonical URL. If a redirect points to a page that canonicalises elsewhere, review both signals together. A canonical tag and a redirect serve different purposes: a redirect sends the requester away, while a canonical indicates the preferred version among accessible pages.

Track destination quality as well as status codes. A technically successful redirect can still be poor if it sends a discontinued product to an unrelated category, drops important tracking parameters, changes language or region unexpectedly, or lands on a page with a new error. Review high-priority rows against real user journeys and campaign links. For international sites, do not use a redirect as a substitute for language or regional configuration; review the guidance on hreflang and redirects where relevant.

When to revisit

Revisit the redirect map after the initial migration, then on a monthly or quarterly cadence depending on site size and change frequency. A monthly review is sensible for sites with frequent releases, active campaigns, or changing product ranges. A quarterly review may be sufficient for a stable site, provided important errors are still monitored between reviews.

Update the map whenever a new URL structure, domain, platform, hostname, protocol, content consolidation, or tracking convention is introduced. Also revisit it after a redesign, a major campaign, a change to internal navigation, or the retirement of a content section. Keep old rules for as long as they serve a useful purpose, but review whether obsolete rules can be consolidated safely. Never delete a rule solely because it is no longer visible in the current sitemap; check request history, links, and business context first.

For each review, take these practical actions:

  1. Export the current redirect rules and compare them with the approved map.
  2. Run a sample of high-priority, recently changed, and previously failing source URLs through a redirect checker.
  3. Search crawl, server, and analytics data for unplanned old URLs, redirect chains, loops, and destination errors.
  4. Check that internal links, XML sitemaps, canonical tags, and campaign links use the intended final URLs.
  5. Assign every new issue an owner, priority, decision, and due date.
  6. Save the review date and a versioned copy of the map.

A redirect map is most valuable when it remains a living migration record rather than a file that is abandoned after launch. Review it after each meaningful site change, test the rows that matter most, and use the findings to simplify rules as the website settles.

Related Topics

#site migration#redirect template#technical SEO#website redesign
P

Portal Redirect Editorial Team

Technical SEO Editors

Senior editor and content strategist. Writing about technology, design, and the future of digital media. Follow along for deep dives into the industry's moving parts.