301 Redirect Mapping Template for Website Migrations

Overview

A redirect map is the working record that connects each important source URL to its intended destination. It should be prepared before implementation, reviewed by the people responsible for SEO and content, and retained after launch as an operational document.

The basic structure is simple: one old URL, one new URL, one redirect decision, and enough notes to explain the decision. A practical 301 redirect mapping template can include these columns:

• Source URL: the complete old path, including the original hostname when domains are changing.
• Destination URL: the final, preferred URL on the new site.
• Redirect type: normally 301 for a permanent move, with a different status used only when the change is genuinely temporary or conditional.
• Page type: product, service, category, article, media, utility, or another useful classification.
• Priority: high, medium, or low based on traffic, links, conversions, visibility, and business importance.
• Status: mapped, reviewed, implemented, tested, or needs decision.
• Notes: explanations for removals, consolidations, parameter handling, or exceptions.

Start with evidence rather than assumptions. Combine the current XML sitemap, server logs or crawl data where available, analytics landing pages, search visibility reports, internal links, and known campaign URLs. Include URLs that may not appear in the current navigation, such as older articles, partner links, downloadable resources, and branded short links.

For background on implementation and bulk validation, see the 301 redirect mapping and bulk checker guide. If the migration changes domains, also review the difference between domain forwarding and URL redirects; they solve related but different operational problems.

Checklist by scenario

Redesign with the same URL structure

• Export the existing URL list before templates or navigation change.
• Confirm which URLs will remain unchanged and exclude them from unnecessary redirect rules.
• Map deleted pages to the closest useful replacement, not automatically to the homepage.
• Check that new templates preserve important internal links, titles, canonicals, and indexable content.
• Test any changed trailing-slash, capitalization, file-extension, or parameter conventions.

Domain migration

• Record the full old and new hostnames, including protocol and preferred hostname choices.
• Create path-level mappings before applying broad domain forwarding.
• Ensure each old URL resolves directly to its final new URL where possible.
• Verify that redirects preserve relevant query parameters used for campaign attribution.
• Update internal links, sitemaps, structured data references, email links, and campaign documentation.

URL restructure or CMS migration

• Export both the old CMS routes and the new route list.
• Match pages by subject, intent, and user task rather than by similar words alone.
• Pay special attention to pagination, category paths, author archives, media URLs, and feeds.
• Identify generated URLs and decide whether they need individual rules, normalization, or no redirect.
• Use bulk URL redirects only after the source and destination patterns have been reviewed for collisions.

Content consolidation or removal

• Group pages that cover the same intent and select one durable destination.
• Redirect genuinely useful retired pages to the most relevant surviving page.
• Do not redirect unrelated or obsolete URLs simply to increase the size of the map.
• For pages with no suitable replacement, document the removal decision and verify the intended response.

What to double-check

Review the map in batches before deployment. Sort by priority first, then inspect every high-value source URL individually. A relevant destination should satisfy the original visitor intent as closely as possible. A product page should lead to the replacement product or an appropriate category; an editorial guide should not normally be sent to a generic homepage.

Check status codes and redirect behavior with a redirect checker or command-line request. Confirm that the source returns the intended permanent status, the destination returns a successful response, and the chain does not contain unnecessary intermediate hops. The HTTP redirect status code guide can help distinguish permanent redirects from temporary redirect behavior.

Inspect canonical tags, internal links, hreflang references where applicable, and XML sitemaps on the new site. These should point to the final URLs rather than continuing to rely on redirected addresses. Also test protocol changes, hostname variants, encoded characters, uppercase paths, and common legacy formats.

Preserve tracking deliberately. Redirects should not accidentally remove or overwrite campaign parameters. Use the guidance on preserving tracking parameters across redirects to review marketing links, QR destinations, affiliate links, and other measurable entry points.

Common mistakes

• Redirecting everything to the homepage: this gives visitors little context and weakens the usefulness of the migration map.
• Mapping only pages in the navigation: high-value URLs often live in archives, external references, campaigns, or old content.
• Creating redirect chains: point each old URL to the final destination instead of routing through another retired URL. See the guide to redirect chains and page speed.
• Using temporary redirects for permanent changes: choose the status code based on the intended lifespan and behavior of the move.
• Ignoring query strings: decide which parameters are meaningful, which should pass through, and which should be normalized.
• Deleting the source list after launch: retain the map so future broken links, support questions, and campaign audits can be resolved quickly.
• Testing only a sample: sampling is useful, but automated checks should cover the complete rule set and identify collisions or loops.

When to revisit

Revisit the redirect map before every seasonal planning cycle, major campaign, redesign, CMS release, or domain and hosting change. It should also be updated when teams change URL conventions, launch new product categories, retire content, or replace the system that manages redirects.

After launch, review redirect analytics, crawl errors, server responses, landing-page performance, and support reports on a scheduled basis. Investigate spikes in missing pages, unexpected destinations, repeated requests for old URLs, and campaign links that no longer attribute correctly. Add confirmed discoveries to the map rather than creating undocumented one-off fixes.

For ongoing protection, pair the map with redirect uptime monitoring so broken destinations are found before a campaign or migration depends on them. Before making the next change, export the current rules, update the source and destination inventory, run a full validation pass, and record who approved the final version. That simple cycle keeps site migration redirects accurate as the underlying site evolves.