Domain Redirect Mapping Guide for Rebrands, URL Changes, and Site Migrations
301 redirectsdomain migrationSEOwebsite rebrandingURL managementsite migrations

Domain Redirect Mapping Guide for Rebrands, URL Changes, and Site Migrations

TTopDomains Editorial Team
2026-11-19
7 min read

Use this redirect mapping checklist to protect visitors and search visibility during rebrands, URL changes, domain moves, and site migrations.

A reliable redirect plan protects visitors, bookmarks, campaign links, and search visibility when you rebrand, change URLs, consolidate domains, or move to a new platform. This guide provides a reusable domain redirect mapping checklist, a spreadsheet template, scenario-based rules, testing steps, and a retirement workflow for obsolete redirects.

Overview

Redirect mapping is the process of recording where each old domain, URL, or protocol version should send visitors on the new site. The goal is not simply to point everything at a homepage. Each important old address should lead to the most relevant available destination, ideally preserving the visitor’s intent and the value of existing links.

Start with an inventory of current addresses before changing DNS, hosting, or site structure. Include the preferred and non-preferred versions of each domain, HTTP and HTTPS URLs where relevant, subdomains, important landing pages, media files, campaign URLs, and URLs reported in analytics or search tools. Exporting server logs, analytics landing pages, XML sitemaps, and backlink data can help reveal URLs that are not obvious from the current navigation.

Keep the redirect map as a working document rather than a one-time project file. It should show the old address, the destination, the redirect type, the reason for the change, the implementation location, and the test result.

Reusable URL redirect spreadsheet template

ColumnWhat to record
Source URLThe complete old URL, including protocol and path.
Source patternWhether the rule covers one URL, a directory, a subdomain, or an entire domain.
Destination URLThe most relevant final URL on the new site.
Redirect typeUsually 301 for a permanent move; use another status only when the scenario requires it.
Query-string treatmentPreserve, remove, or deliberately transform parameters.
ReasonRebrand, URL restructure, product replacement, campaign change, or removal.
Owner and implementationThe person responsible and the server, CDN, CMS, or hosting panel where the rule will live.
Status and test datePlanned, implemented, tested, corrected, or retired, with the latest check date.

Checklist by scenario

Rebranding or moving to a new domain

  • Confirm ownership, DNS access, registrar access, and hosting access for both domains.
  • Choose one preferred destination domain and define whether both HTTP and HTTPS requests should resolve to it.
  • Map important old pages to equivalent new pages instead of sending every request to the homepage.
  • Use permanent redirects for URLs that have moved permanently. A 301 is the usual choice for this situation.
  • Keep the old domain active and redirecting while visitors, bookmarks, referring sites, and search systems adjust. The appropriate review period depends on the site and traffic pattern.
  • Update internal links, canonical references, XML sitemaps, structured data URLs, social profiles, business listings, and email signatures.

Changing URL paths or restructuring a site

  • Export the old URL list and compare it with the new sitemap or route list.
  • Create one direct mapping for each page that has a clear replacement.
  • Redirect removed pages to a closely related replacement only when one genuinely exists. Otherwise, return an appropriate not-found or gone response rather than creating a misleading destination.
  • Check trailing slashes, uppercase characters, file extensions, language folders, and pagination patterns.
  • Test both representative URLs and unusual variants that appear in logs or external links.

HTTPS, host, and subdomain normalization

  • Select one canonical combination of protocol, hostname, and URL format.
  • Redirect alternate HTTP, HTTPS, www, non-www, and relevant subdomain versions directly to the final canonical URL.
  • Install and validate the SSL certificate before relying on HTTPS redirects. For related troubleshooting, see the SSL Certificate Checklist.
  • Do not assume a DNS record creates a redirect. DNS directs a hostname to infrastructure; the web server, CDN, CMS, or hosting panel must issue the HTTP response.

Campaign, tracking, and query-string changes

Decide how each query parameter should behave before implementation. Parameters used for analytics may be preserved if the destination and campaign measurement require them. Parameters that controlled an old search, filter, session, or tracking system may need to be removed or translated. Avoid blindly copying every parameter to a destination that cannot interpret it.

Document the rule clearly: “preserve all parameters,” “preserve only campaign parameters,” or “remove parameters.” Then test links containing multiple parameters, encoded characters, fragments, and repeated keys. A redirect normally cannot send a server-side request to a browser fragment after the hash mark, so client-side behavior may require a separate solution.

Temporary destinations and experiments

Use a temporary redirect, commonly a 302, when a move is genuinely temporary or the destination is part of a controlled short-term test. Record an owner and review date so temporary rules do not become permanent by neglect. When the change becomes permanent, update the mapping and test the resulting 301 behavior.

What to double-check

Redirect chains and loops

Every source should ideally resolve in one direct step to its final destination. A chain such as old URL to intermediate URL to final URL adds unnecessary processing and makes troubleshooting harder. A loop occurs when rules send a request back to a previous address, often because HTTP-to-HTTPS, host normalization, and CMS rules were configured independently.

Run a crawler or command-line request tool across the mapping. Record the complete status sequence, final URL, response code, and whether the destination is accessible. Test from more than one network when DNS changes are involved, but remember that a DNS propagation checker cannot confirm the correctness of an application-level redirect by itself.

Implementation location

Place each rule where the request is actually handled. Depending on the setup, this may be an Apache configuration file, an Nginx server block, a hosting control panel, a CMS plugin, an application route, a CDN, or a dedicated redirect service. Avoid duplicating the same rule across several layers unless the behavior is understood and documented.

Confirm that the old domain still points to the system containing the redirect rules. If you are moving hosting at the same time, coordinate DNS, certificate issuance, origin configuration, and redirect deployment. The DNS Records Explained guide can help separate DNS responsibilities from web-server behavior.

Validation after launch

  1. Test a sample from every redirect pattern, including the root domain and key directories.
  2. Test old URLs with and without trailing slashes, expected query strings, and both protocols where applicable.
  3. Confirm that final pages return a successful response and do not redirect again.
  4. Check internal links and canonical tags on the new site.
  5. Review analytics, server logs, crawl reports, and error reports for missed URLs.
  6. Monitor high-value old URLs and referring links after launch.

Common mistakes

  • Redirecting every page to the homepage: This loses context and may leave visitors unable to find the content they requested.
  • Changing domains and DNS without testing the redirect host: A correct rule is useless if the old hostname no longer reaches it.
  • Creating long chains: Combine rules so old URLs point directly to final destinations.
  • Mixing permanent and temporary logic: Label each rule and add a review date for temporary changes.
  • Ignoring email and verification records: A domain move can affect business email, SPF, DKIM, DMARC, and third-party verification. Review the business email DNS guide before changing records.
  • Deleting the old domain too soon: Confirm that ownership, renewal, DNS, and redirect responsibilities are documented before retiring it. The Domain Renewal and Expiration Guide covers related safeguards.
  • Leaving duplicate rules in different systems: Keep one authoritative map and record where every active rule is maintained.

When to revisit

Review the redirect map before seasonal planning cycles, major campaigns, platform changes, and any new site migration. Revisit it immediately after a rebrand, domain consolidation, URL restructure, hosting change, or CMS replacement. A recurring review is also useful when analytics shows traffic arriving at old URLs, when monitoring reports new not-found errors, or when a campaign introduces new parameters.

Use this retirement workflow for obsolete redirects:

  1. Confirm the source URL has no important traffic, links, bookmarks, or operational purpose that still depends on it.
  2. Check whether the rule is referenced in marketing materials, partner sites, email templates, or printed collateral.
  3. Record the decision, reviewer, date, and reason in the spreadsheet.
  4. Remove or revise the rule in the authoritative implementation layer.
  5. Test the old URL and confirm the intended response after deployment.
  6. Watch logs and error reports for a defined review period, then update the map.

Keep a dated export of the final mapping before each major change. That simple record makes future audits faster, helps identify regressions, and gives every site owner a clear starting point for the next domain or URL decision.

Related Topics

#301 redirects#domain migration#SEO#website rebranding#URL management#site migrations
T

TopDomains Editorial Team

Domains and Hosting 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.