Skip to content
Peacock Search
ServicesLocationsIndustriesVisibility ReviewAI AutomationSearch NotesAboutWhatsAppBook review
Home / Search Notes / How to Build a Redirect Map for a Website Migration

Search Notes

How to Build a Redirect Map for a Website Migration

September 8, 2026

Supports Migration Support

A redirect map is a spreadsheet that says where every old URL should go. Building it carefully is the single most protective thing you can do in a migration.

Quick answer

List every old URL that matters, decide the closest equivalent new URL for each, record the redirect type and reason, then test the whole map by crawling the old URLs and checking they end at the right page in one hop. Use permanent redirects, match pages one to one by relevance, and avoid sending everything to the homepage.

Step 1: collect every old URL

A crawl of the live site is the starting point, but it only finds pages that are linked. Combine several sources:

  • A crawl of the live site
  • The XML sitemap or sitemaps
  • Search Console: pages with impressions and clicks
  • Analytics: pages that receive traffic
  • A backlink tool: pages with external links, even if they are no longer linked internally

When I migrated this site, the crawl found 101 URLs, more than twice what I had expected. Two of them were duplicates still listed in a sitemap. Combining sources catches pages like that.

Step 2: decide what changes

The best redirect map is the shortest one. If you can keep a URL the same, do. On this migration most pages kept their URLs, so the map only needed to cover the exceptions, such as the old root-level post URLs.

Where URLs do change, make the new URL a real equivalent: same topic, same intent. If the old page has no equivalent, redirect it to the closest parent or category, not the homepage, or let it return a 404 or 410 if there is truly nothing relevant.

Step 3: build the map

Use one row per old URL, with columns like these:

  • Old URL
  • New URL
  • Redirect type (permanent or temporary) and why
  • Rule or one-off (pattern redirects save time for whole sections)
  • Traffic and backlinks (to prioritise testing)
  • Tested? And the result

For large sites, group by pattern first (for example `/blog/{slug}/` to `/articles/{slug}/`), then handle the exceptions one by one.

Step 4: choose the right redirect types

Use permanent redirects for anything that has moved for good. They tell search engines to transfer the old URL's signals to the new one. Some frameworks issue a 308 for permanent redirects, and Google treats a 308 the same as a 301.

Redirect types I used on this site:

  • `www` to the non-www domain, for every path
  • `/privacy-policy/` to `/privacy/` and `/case-studies-2/` to `/case-studies/`, removing duplicate URLs
  • Old root-level post URLs such as `/{slug}/` to `/search-notes/{slug}/`
  • Retired Search Notes straight to the page that replaced them, in a single hop

That last one matters. If `/old-post/` redirects to `/search-notes/old-post/`, and that then redirects to the replacement, you have created a chain. Point the old URL at the final destination.

Step 5: test before and after launch

  • Crawl the old URL list and record the status code, the number of hops and the final URL
  • Check every old URL ends at a page that returns 200
  • Look for chains (more than one hop), loops and redirects to irrelevant pages
  • Spot-check a sample by hand, especially high-traffic and high-backlink pages
  • Confirm internal links point to the final URLs, not to URLs that redirect
  • Make sure the new sitemap lists only final, indexable URLs

You can check single URLs with the redirect chain checker.

Step 6: keep watching

After launch, check Search Console for new 404s and "page with redirect" reports, and watch the pages with the most traffic first. Keep redirects in place for at least a year, longer if old URLs still have backlinks.

Common mistakes

  • Redirecting everything to the homepage
  • Leaving redirect chains and loops
  • Using temporary redirects for permanent moves
  • Mapping old URLs by title instead of intent
  • Forgetting parameters, trailing slashes and uppercase variants
  • Never testing the map

When to get support

A redirect map is one part of a safe migration. My SEO migration support includes building and testing it alongside the pre-launch audit and post-launch monitoring.

FAQ

How many redirects can a site have?

There is no practical limit for normal sites, but long chains slow crawling and waste signals, so keep every redirect to a single hop.

Should I redirect old URLs that had no traffic?

If they have backlinks or a clear equivalent, yes. If they were thin and nothing links to them, it is fine to let them return a 404 or 410.

Is a 301 better than a 308?

For Google they are equivalent for permanent moves. Use whichever your platform produces.

Related Search Notes

  • Common SEO Migration Mistakes That Cost Traffic
  • SEO Migration Checklist Before Launch
  • What to Monitor After a Website Migration

Practical use

How to turn this into action

  • Check whether the issue affects important templates, not just isolated URLs.
  • Separate urgent fixes from useful clean-up so the work can be prioritised.
  • Collect examples before briefing developers, writers or stakeholders.
  • Link the recommendation back to visibility, traffic quality or launch risk.
See how this supports Migration Support

Author

Written by Chris Payne

Chris Payne is the freelance SEO consultant behind Peacock Search. He has 8 years of SEO experience across ecommerce, publishing, UK and international websites, with a focus on technical SEO, content strategy, migrations and complex large-site audits.

More about Chris Payne
Peacock Search

Freelance SEO consultancy based in Romsey, specialising in audits, technical SEO, local SEO, content strategy and migration support.

Process SEO Audits Free SEO Audit Template Freelance SEO Consultant Agency Support AI Automation Sample Outputs Case Studies Privacy Cookies