301 Redirect Mapping Template

Free editable 301 Redirect Mapping Template. Copy, personalize, or download the Word .docx template from UNmiss.

Changing URLs without a plan is how sites lose hard-won rankings overnight. This template gives you a clean, repeatable way to map every old URL to its closest new equivalent, avoid redirect chains and soft 404s, and verify everything after launch. Copy it, fill in the placeholders, and ship your URL changes with confidence.

6 ready-to-use variants

Domain Migration Redirect Map (Old URL → New URL)

Moving to a new domain and need every old URL pointed at its exact match on the new site.

Domain Migration Redirect Map

When you move domains, every indexed old URL must point to its closest equivalent on the new domain with a single 301 (permanent) redirect. A 301 passes ranking signals; a 302 or 307 is temporary and should not be used for a permanent move. Never blanket-redirect everything to the homepage: search engines treat that as a soft 404 and drop the page.

Build your map as old→new pairs:

  • Old URL: [https://old-domain.com/services] → New URL: [https://new-domain.com/services]
  • Old URL: [https://old-domain.com/blog/post-a] → New URL: [https://new-domain.com/blog/post-a]
  • Redirect type: [301]
  • Status check: [200 OK at destination]

Point each redirect straight at the final live URL so there are no chains or loops, and update internal links to the new domain rather than relying on the redirects.

HTTP→HTTPS & www/non-www Consolidation

Forcing one canonical protocol and host so duplicate versions of your site collapse into a single address.

HTTP→HTTPS & www/non-www Consolidation

A site is often reachable at up to four addresses (http/https and www/non-www) which splits signals across duplicates. Pick one canonical version and 301 the other three to it so all authority consolidates on a single host and protocol.

Map each non-canonical variant to your chosen canonical:

  • Old URL: [http://example.com/page] → New URL: [https://www.example.com/page]
  • Old URL: [https://example.com/page] → New URL: [https://www.example.com/page]
  • Old URL: [http://www.example.com/page] → New URL: [https://www.example.com/page]

Configure this as a single server-level rule that forces the canonical host and protocol in one hop (paired with HSTS) rather than maintaining four separate path redirects. Each URL must still land on its matching page, not the homepage, and avoid http→https→www style chains. Then update your sitemap, canonical tags, and internal links to use the canonical URLs directly.

Consolidating Duplicate or Thin Pages (Merge Then Redirect)

Merging several overlapping or thin pages into one strong page and redirecting the rest.

Consolidating Duplicate or Thin Pages

When multiple pages compete for the same topic or are too thin to rank, merge their useful content into one authoritative page, then 301 the retired URLs to that survivor. This concentrates ranking signals instead of splitting them.

Decide which URL survives, then map the rest to it:

  • Survivor URL: [/guides/email-marketing]
  • Old URL: [/blog/email-tips] → New URL: [/guides/email-marketing]
  • Old URL: [/blog/email-basics] → New URL: [/guides/email-marketing]

Each redirected page should land on the single most relevant section of the survivor, not a generic hub or the homepage. Move any unique content and useful links into the survivor before retiring the source pages, and update internal links that pointed at the old URLs so they reference the survivor directly.

Retiring or Removing Pages (301 vs 410 Decision)

Deciding, page by page, whether to redirect a removed page or let it return gone.

Retiring or Removing Pages (301 vs 410)

Not every removed page deserves a redirect. Use a 301 when a close equivalent exists and you want to preserve its signals. Use 410 Gone (or 404) when the page is genuinely gone with no replacement: redirecting it to an unrelated page or the homepage creates a soft 404.

Make the call for each URL:

  • Old URL: [/promo/spring-sale] → Decision: [301] → Target: [/sales]
  • Old URL: [/event/2019-webinar] → Decision: [410 Gone] → Target: [none]

Ask: does a relevant equivalent exist? If yes, 301 to it. If no, return 410 so the page is dropped cleanly. Always send the redirect to the closest match in one hop, and remove internal links pointing at any 410'd URLs.

Site Restructure / URL Change Map

Reorganizing your URL structure or folders while keeping the same domain.

Site Restructure / URL Change Map

Restructuring folders, slugs, or your URL hierarchy on the same domain still breaks every old URL. Map each changed path to its new location with a 301 so rankings and backlinks follow the content to its new address.

Capture old→new pairs for every changed URL:

  • Old URL: [/products/widget] → New URL: [/shop/widgets/widget]
  • Old URL: [/category/news] → New URL: [/blog/news]
  • Redirect type: [301]

Map to the specific equivalent page, not a parent category or the homepage. If a page moved twice during planning, redirect the original old URL straight to the final URL so you avoid chains and loops. Regenerate your XML sitemap with the new URLs and update internal links, navigation, and canonical tags to point at the new paths directly.

Post-Launch Redirect QA Checklist

Verifying every redirect actually works the day a URL change or migration goes live.

Post-Launch Redirect QA Checklist

Redirects are only as good as their testing. After launch, crawl your old→new map and confirm each rule behaves before you trust it with your rankings.

Check each redirect against these criteria:

  • Old URL: [/old-path] → Returns: [301]
  • Lands on: [/new-path] → Final status: [200 OK]
  • Hops: [1] → Chain/loop: [none]

Confirm the status code is 301 (not 302/307), the destination returns 200, and each redirect resolves in a single hop with no chains or loops. Verify no important page lands on the homepage as a soft 404. Finally, submit the new sitemap, watch coverage reports for errors, and fix any internal links still pointing at old URLs.

How to use this template

  1. Crawl your current site and export a complete list of every live, indexed URL so nothing is missed in the map.
  2. Create your map as two columns of old→new pairs, with one row per old URL and its single closest new equivalent.
  3. For each old URL, identify the most relevant destination page; never default unmatched URLs to the homepage, which causes soft 404s.
  4. Set every redirect to 301 (permanent) so ranking signals pass; reserve 302/307 only for genuinely temporary moves.
  5. Decide retired pages individually: 301 to an equivalent where one exists, or return 410/404 when there is no replacement.
  6. Flatten any chains so each old URL redirects directly to the final URL in one hop, and remove any loops.
  7. Update internal links, navigation, canonical tags, and your XML sitemap to reference the new URLs directly instead of relying on redirects.
  8. After launch, test status codes for every mapped URL, confirm each lands on a 200 destination, and monitor coverage reports for errors.

Pro tips

  • Map to the closest equivalent page, not the homepage. A blanket redirect to the home page is treated as a soft 404 and loses the signal.
  • Eliminate redirect chains and loops: point the original old URL straight at the final destination so it resolves in a single hop.
  • Update internal links to the new URLs directly rather than leaning on redirects, which keeps crawling efficient and reduces wasted hops.
  • Use 301 for permanent changes only; if a move is genuinely temporary, use 302/307 so search engines keep the original URL indexed.

Frequently asked questions

What is the difference between a 301 and a 302 redirect?

A 301 is a permanent redirect that tells search engines the move is final and passes ranking signals to the new URL. A 302 (or 307) is temporary and signals the original URL should stay indexed. For migrations, consolidations, and permanent URL changes, use 301.

Can I redirect all my old URLs to the homepage?

No. Redirecting unmatched URLs to the homepage is treated as a soft 404 because the destination does not match the original content, and the page's signals are typically lost. Always map each old URL to its closest equivalent page instead.

What is a redirect chain and why should I avoid it?

A redirect chain is when URL A redirects to B, which redirects to C, forcing multiple hops. Chains slow crawling and can dilute signals. Point the original old URL directly at the final destination so every redirect resolves in a single hop, and never let two URLs redirect to each other in a loop.

When should I use a 410 instead of a 301?

Use a 410 Gone (or 404) when a page is permanently removed and has no relevant equivalent to redirect to. Use a 301 only when a close replacement exists. Forcing a 301 to an unrelated page creates a soft 404, so 410 is the cleaner choice for true removals.

Do I still need to update internal links if I have redirects in place?

Yes. Redirects are a safety net for external links and bookmarks, but your own internal links, navigation, and canonical tags should point directly at the new URLs. This avoids unnecessary hops, speeds up crawling, and prevents accidental chains.

How do I confirm my redirects are working after launch?

Test the status code of each old URL and confirm it returns 301, lands on the intended new URL, and that the destination returns 200 OK in a single hop. Re-crawl the site to catch chains or loops, submit the updated sitemap, and watch coverage reports for redirect or 404 errors.