Website Migration Redirect Map Template: How to Plan, Build, and Audit Bulk URL Redirects
site migrationredirect templatetechnical SEOURL mappingSEO tools

Website Migration Redirect Map Template: How to Plan, Build, and Audit Bulk URL Redirects

RRedirect Portal Editorial Team
2026-11-05
6 min read

Use this practical redirect map checklist to plan, implement and audit bulk URL redirects during a website or domain migration.

A redirect map turns a large website change into a controlled set of source-to-destination instructions. This practical checklist explains how to collect URLs, choose suitable destinations, prioritise important pages, prepare a bulk redirect map, hand it to developers, and audit the results after launch.

Overview

A redirect map is a working document that records which old URL should lead to which new URL. It is useful for a domain change, redesign, platform migration, HTTPS move, change from one URL structure to another, or consolidation of overlapping content.

For most permanent migrations, the intended implementation is a server-side 301 redirect. A temporary change may need a 302 redirect instead. The correct status depends on whether the old URL is being replaced permanently, so confirm the decision before implementation. The guide 301 vs 302 Redirects provides a useful status-code reference.

Keep the map separate from the implementation itself. A spreadsheet or database is easier to review than a configuration file, and it creates a record of decisions that can be checked by SEO, content, development and analytics teams.

  • Source URL: the complete old path, including the protocol and hostname where relevant.
  • Destination URL: the final intended URL on the new site.
  • Status: usually 301 for a permanent replacement, or 302 where the change is temporary.
  • Page type: product, service, article, category, landing page, file or other useful classification.
  • Match method: exact equivalent, closest topical match, consolidation, removal or no redirect.
  • Priority: high, medium or low, based on traffic, links, conversions, visibility and business importance.
  • Owner: the person responsible for approving the mapping.
  • Implementation status: proposed, approved, deployed, tested or needs correction.
  • Notes: reasons for the choice, query-string behaviour, exceptions or unresolved questions.

Checklist by scenario

For a domain migration

  1. Export every indexable URL from the old domain, including important image, document and feed URLs where users or referring sites may still rely on them.
  2. Include both the preferred and non-preferred hostname variations if the old site used HTTP, HTTPS, www or non-www versions.
  3. Map each old URL to its equivalent on the new domain. Preserve the path where it remains valid, but do not assume that a matching path means matching content.
  4. Define the canonical hostname and ensure the redirect rules do not create a second hop through another hostname.
  5. Test representative URLs from each hostname and protocol combination.

For a redesign or CMS migration

  1. Compare the old URL inventory with the new sitemap, navigation and content inventory.
  2. Map pages with the same purpose first. If a page has no exact replacement, use the closest genuinely relevant destination rather than sending it to the homepage by default.
  3. Record pages that should return a deliberate 404 or 410 response instead of being redirected. This is particularly important for obsolete, thin or inappropriate URLs.
  4. Check that important metadata, internal links, structured content and canonical URLs will point to the new addresses.
  5. Mark redirects that need application logic, server configuration, a hosting control panel or a WordPress redirect tool so implementation ownership is clear.

For a URL structure change

  1. Identify the old pattern and the new pattern, such as a change from /blog/title to /guides/title.
  2. Use a pattern-based rule only when the relationship is consistent and safely testable. Use individual rows for exceptions.
  3. Check trailing slashes, capitalisation, file extensions, pagination, language folders and category paths.
  4. Test query parameters separately. Preserve campaign parameters only when the destination and tracking setup support them; see Redirects and Query Parameters for considerations.

For a bulk redirect map

Start with a complete source list, then add destinations in batches. Sort the sheet by status, page type and priority so reviewers can identify gaps quickly. Do not treat an empty destination as an automatic redirect to the homepage. Each unresolved row should have a decision, an owner and a reason.

What to double-check

  • Source normalisation: remove accidental spaces, duplicated rows and inconsistent protocol or hostname formatting without losing meaningful URL differences.
  • Destination quality: confirm that every destination loads, is indexable when intended, uses the preferred canonical URL and matches the old page's purpose.
  • Status codes: verify that permanent changes return 301 and temporary routing returns 302 where appropriate. Do not infer success from a browser loading the final page.
  • Hop count: request each source and record every response. A source should normally reach its final destination directly. Use the redirect chain and loop troubleshooting guide when a request passes through multiple redirects.
  • Loops: test protocol and hostname rules together. An HTTP-to-HTTPS rule combined with a www-to-non-www rule can behave incorrectly if their conditions overlap.
  • Internal links: update navigation, templates, XML sitemaps, feeds, hreflang references and content links to use final URLs rather than relying on redirects.
  • Tracking: confirm that UTM parameters and other permitted query strings are retained, removed or transformed intentionally rather than accidentally duplicated or discarded.
  • Monitoring: compare crawl errors, server logs, analytics landing pages and important referring links before and after launch.

A redirect checker can validate response codes and final destinations, but it should complement—not replace—review of the mapping logic. A technically valid 301 can still point to an irrelevant page.

Common mistakes

Redirecting every old URL to the homepage: this hides missing decisions and gives visitors little context. Map to a relevant replacement, or document why no redirect is appropriate.

Building chains: redirecting an old URL to an intermediate URL that redirects again adds unnecessary complexity. Map old URLs directly to the final canonical destination.

Using a temporary redirect for a permanent move: this can make the migration intent unclear. Review the distinction in the 301 vs 302 reference guide before deployment.

Ignoring non-page URLs: PDFs, downloads, campaign landing pages and old subdomains can continue to receive visits and links. Include them in the inventory where they matter.

Relying only on the sitemap: a sitemap shows intended current URLs, not every old URL that may be requested. Combine crawl data, analytics, server logs, CMS exports and known external links when available.

Publishing without an exception list: pattern rules are efficient but can catch special cases. Keep explicit exceptions near the implementation and test them after every rule change.

When to revisit

Revisit the redirect map before each migration, domain renewal or major seasonal planning cycle. Inputs change: new URLs are published, products are retired, campaign links accumulate and hosting or CMS workflows may be replaced. A map that was accurate at launch can become incomplete over time.

Use this short review routine:

  1. Export newly reported 404s and redirecting URLs.
  2. Check high-value landing pages and important external referrers.
  3. Review redirect rules after changes to DNS, hosting, CDN, CMS or URL conventions.
  4. Remove obsolete temporary rules only after confirming that they are no longer required.
  5. Retest samples from every rule group, including exceptions and query-string variants.

For a reusable starting point, compare this workflow with the website migration redirect checklist and keep your own approved map under version control. The practical goal is simple: every important old URL should have a reviewed outcome, every rule should have a clear owner, and every deployed redirect should lead directly to the right final address.

Related Topics

#site migration#redirect template#technical SEO#URL mapping#SEO tools
R

Redirect Portal Editorial Team

Technical SEO Editor

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.