A redirect map is a spreadsheet listing every old URL and the new URL it should send visitors and Google to. Build it by collecting all old URLs, matching each to the closest new page, implementing 301 redirects, and testing them. A good map is the single biggest protection for your rankings during a migration.
Why the map matters
When a URL changes and nothing points it to the new address, Google sees a missing page. The links, history and rankings attached to that page are cut off. Most migration traffic drops trace back to this. Our website migration SEO recovery work starts here for that reason.
Step 1: Collect every old URL
Do not rely on a crawl alone. A crawl only finds pages that are linked today. Combine several sources:
Source list
Where old URLs hide
The backlink and Search Console lists matter most. They show the pages that Google and other sites actually use.
URL sources to combine
- Full crawl of the live site
- XML sitemaps
- Search Console Performance report, pages tab
- Search Console Pages report (indexing)
- Analytics landing pages
- Backlink report, linked URLs
- Server logs
Merge them, remove duplicates, and keep the traffic and backlink counts next to each URL. This gives you a priority order.
Step 2: Decide where each page goes
For each old URL, pick one outcome.
| Situation | What to do |
|---|---|
| Same page, new address | 301 redirect to the new URL. |
| Page merged into another | 301 redirect to the page that now holds the content. |
| Page replaced by a similar one | 301 redirect to the closest equivalent. |
| Page removed with no equivalent | Return a 404 or 410 status. Do not send it to the homepage. |
| Page with strong links but no match | Find the closest category or topic page, or create a useful page. |
Match by topic and intent, not by guesswork. If a person who landed on the old page would be happy with the new page, it is a good match.
Step 3: Write the rules
Group the redirects by pattern where you can. If /blog/post-name/ moves to /articles/post-name/, one rule covers hundreds of pages. Handle exceptions one by one.
Point every old URL straight to its final destination. A chain, where A goes to B and B goes to C, wastes crawling and can lose signals. Our guide to fixing 404 errors at scale covers how to find the chains and gaps afterwards.
Step 4: Test before launch
Test on a staging copy where you can. Run the whole list of old URLs through a crawler in list mode. For each one, check three things: it returns a 301, it lands in one hop, and the destination returns a 200 status. Also check that the staging site is blocked from indexing, then remove that block at launch. A leftover noindex is a common launch error, covered in our guide on noindex and robots.txt mistakes.
Step 5: Check after launch
On launch day, retest a sample of old URLs on the live site. Then watch Search Console:
- The Pages report for new "Not found (404)" and "Redirect error" entries.
- The Performance report for pages that lost clicks.
- Crawl stats for spikes in errors.
Fix gaps as they appear, and submit your new sitemap. Keep the redirects in place long after launch. Our answer on how long redirects should stay explains why.
When to call for help
Get help if the site has thousands of URLs, if you changed domains as well as URLs, or if traffic already fell after launch and you cannot find which pages broke. We compare the old site and the new one URL by URL and rebuild the map from the evidence. Our seo migration checklist covers the rest of the launch, and you can ask for a free SEO triage at any point.
FAQ
Questions owners ask us
Should I redirect everything to the homepage?
No. Redirecting many old pages to the homepage tells Google nothing useful, and Google may treat them as soft 404 errors. Each old page should go to the most relevant new page. If no equivalent exists, a 404 or 410 is more honest than a homepage redirect.
Which redirect type should I use?
Use a 301 redirect for a permanent move. Google treats permanent server side redirects as a strong signal that the new URL should be the canonical one. Avoid JavaScript and meta refresh redirects for a migration.
What if my migration already launched without a redirect map?
Build one now. Export old URLs from your backups, analytics and Search Console, match them to the new pages and add the redirects. Our free SEO triage can check how much damage was done first.
Get started