A redirect map gives every changed URL a planned destination before a domain change, rebrand, or site migration goes live. This checklist explains how to choose redirect targets, write rules for common website changes, test them safely, and keep a rollback plan so visitors and search engines can still reach the right content.
Overview
A redirect tells a browser or crawler that one URL should lead somewhere else. A 301 redirect is the usual choice when a page or domain has moved permanently. It can preserve access to old links and help search engines understand the relationship between the old and new locations. A temporary redirect may be more appropriate for short-lived changes, such as a maintenance route or time-limited campaign.
A redirect map is the working document behind the change. At minimum, it should contain the old URL, the intended new URL, the redirect type, the reason for the change, and a test result. For a domain migration, include both the old and new hostnames. For a URL restructure, record every changed path rather than relying only on a broad wildcard rule.
Use one preferred URL format throughout the site. Decide whether the canonical version uses HTTPS, www, a trailing slash, or another consistent convention. Then redirect alternate versions to that preferred format. This reduces duplication and makes future troubleshooting easier.
Redirects are only one part of a launch. Update internal links, canonical tags, XML sitemaps, structured data, social profile links, advertising destinations, email templates, and any third-party integrations that still reference old URLs. If the change involves DNS, review the DNS troubleshooting checklist separately; a DNS problem cannot be fixed with an application-level redirect.
Checklist by scenario
1. HTTP to HTTPS
- Confirm that the HTTPS version loads correctly and has a valid certificate.
- Redirect each HTTP URL to the matching HTTPS URL, keeping the path and useful query string where appropriate.
- Update internal links, canonical tags, image URLs, scripts, stylesheets, and sitemap entries to HTTPS.
- Check for mixed-content warnings after the redirect is active.
Do not redirect HTTP to a generic homepage when the equivalent HTTPS page exists. A page-to-page redirect gives visitors a more predictable experience and preserves the purpose of the original link. For certificate checks and renewal planning, see SSL certificate installation and renewal guidance.
2. WWW to non-WWW, or non-WWW to WWW
- Choose one hostname as the preferred version.
- Redirect the alternate hostname for every path, not just the homepage.
- Confirm that the preferred hostname serves the correct certificate and application configuration.
- Update absolute URLs in templates, feeds, sitemaps, and marketing materials.
Apply hostname normalization consistently. A visitor should not pass through several rules, such as HTTP to HTTPS, then non-WWW to WWW, then an added trailing slash. Where possible, combine these conditions into one redirect from the original URL to the final preferred URL.
3. Moving an old domain to a new domain
- Export a list of the old site’s indexable URLs, including important landing pages, posts, product pages, downloads, and URLs with external links.
- Create a row for each old URL and assign the closest relevant destination on the new domain.
- Keep equivalent paths where the information architecture has not changed. Map renamed or merged pages manually.
- Install redirects on the old domain and test them from outside the new site.
- Update internal links, XML sitemaps, canonical tags, analytics settings, email links, and business listings.
- Keep the old domain and its redirect configuration available for as long as the migration plan requires, and monitor it for missed URLs.
A domain-wide rule can preserve paths when the old and new structures match. It is not a substitute for mapping pages that were deleted, renamed, consolidated, or moved into a different folder. Also protect important non-page routes, such as image files, feeds, downloadable documents, and API endpoints, from being sent to an unrelated homepage.
4. Deleted or discontinued pages
First decide whether a genuinely useful replacement exists. If it does, use a 301 redirect to that replacement. If no relevant replacement exists, returning an appropriate not-found or gone response may be clearer than redirecting every deleted URL to the homepage. The right choice depends on the page’s purpose, remaining demand, links, and the quality of available alternatives.
Remove deleted URLs from internal navigation and the XML sitemap. Check whether the URL appears in paid campaigns, customer documentation, support articles, QR codes, or external partner links before removing it.
5. Trailing-slash or path-format changes
- Choose whether directory-style URLs use a trailing slash.
- Redirect the alternate form to the chosen form with one hop.
- Check that files, directories, language folders, and extension-based URLs are not caught by an overly broad rule.
- Update canonical tags and internal links to the preferred format.
6. Wildcard and pattern rules
Wildcard rules are useful when a complete section moves predictably, such as /old-blog/ to /articles/. Before publishing one, test paths with uppercase characters, encoded symbols, query strings, empty folders, and files that should not move. Put specific exceptions before broad rules. A rule that is convenient for hundreds of URLs can also redirect unrelated URLs if its pattern is too general.
How to set up and test redirects
Choose the layer that controls the request: the web server, hosting control panel, CDN, reverse proxy, or content management system. Server-level rules are often suitable for a full domain or site migration, while a CMS redirect tool may be easier for individual content changes. Avoid running competing redirect systems without documenting which one executes first.
For Apache-based hosting, a simple rule may look like this:
RewriteEngine On
RewriteCond %{HTTPS} !=on [OR]
RewriteCond %{HTTP_HOST} !^www\.example\.com$ [NC]
RewriteRule ^ https://www.example.com%{REQUEST_URI} [R=301,L]
This is an example, not a drop-in configuration. The correct syntax depends on the server, document root, existing rules, and preferred hostname. Nginx, a CDN, and a CMS use different configuration methods. Take a backup and confirm the hosting platform’s expected syntax before editing production settings.
Test the map in a staging environment when possible, then run a controlled production check. For each important URL, verify:
- The old URL returns the intended redirect status.
- There is only one redirect hop before the final page.
- The destination returns a successful response and displays the expected content.
- HTTP, HTTPS, hostname, uppercase, trailing-slash, and query-string variants behave as intended.
- Assets such as images, CSS, JavaScript, downloads, and feeds are not accidentally redirected.
- Authentication, checkout, form submissions, and other sensitive workflows still work.
Use browser developer tools, command-line headers, a crawler, or a redirect-checking utility to inspect the full response sequence. Record the date, test URL, response chain, final destination, and result in the redirect map. Also review analytics, server logs, uptime alerts, and crawl reports after launch. The website uptime monitoring runbook can help organize post-launch checks.
What to double-check
- Destination relevance: Each redirect should lead to the closest useful equivalent, not automatically to the homepage.
- Redirect chains: Change old URLs directly to final URLs rather than linking one redirect to another.
- Redirect loops: Check conflicting HTTPS, hostname, slash, and CMS rules that send a request back to its starting point.
- Query parameters: Decide whether tracking parameters should be retained, ignored, or normalized. Do not discard parameters needed for site search, product selection, or other functionality.
- Canonical signals: The final page’s canonical tag, internal links, sitemap entry, and redirect destination should agree.
- DNS and hosting: Confirm that the old and new domains point to the intended infrastructure and that the hosting plan can handle the launch. For planning context, compare shared hosting and VPS options.
- Email and subdomains: Do not change web redirects without checking mail records, webmail addresses, staging hosts, and other subdomains.
- Rollback: Save the previous configuration, export the redirect map, and define who can disable a faulty rule.
Common mistakes
Redirecting everything to the homepage hides missing mappings and frustrates visitors who expected a specific resource. Map high-value URLs individually and use a general rule only where the old and new structures genuinely match.
Changing redirects and DNS at the same time without a record of the old setup makes failures difficult to isolate. Save DNS records, server rules, CMS settings, and a URL inventory before the change.
Leaving internal links pointed at old URLs creates unnecessary hops and can keep obsolete addresses in circulation. Update templates, navigation, related-content links, feeds, and sitemaps.
Testing only the homepage misses broken deep links, files, language versions, campaign URLs, and legacy content. Test representative samples from every directory and every major traffic source.
Using a temporary redirect for a permanent move can send mixed signals about the intended destination. Select the status code based on the actual duration and purpose of the change, then document that decision.
When to revisit
Review the redirect map before a domain change, rebrand, URL restructure, CMS migration, hosting move, product retirement, or HTTPS and hostname change. Recheck it before seasonal planning cycles if campaign landing pages or promotional URLs are being replaced.
After launch, review redirect errors and server logs frequently enough to catch important omissions while the change is still easy to correct. Run a broader crawl after the site has had time to receive normal traffic, and repeat the audit during routine site maintenance. Revisit the process whenever your CMS, CDN, hosting platform, browser behavior, or search-engine documentation changes.
For the next migration, start with the same five actions: export the old URL inventory, choose one preferred URL format, map each important destination, test representative paths, and save a rollback copy. A current redirect map turns a risky one-time change into a repeatable website launch procedure.