Platform and migration
URL Mapping for Website Migrations: How to Build a Redirect Map
On this page
URL mapping is the list that pairs every URL on your current site with its address on the new one, made before a migration. It decides where each page, file and old link will send visitors and search engines after launch, so traffic, rankings and inbound links follow the content instead of landing on errors.
Google’s own guidance for site moves starts here: map your old site’s URLs to the URLs for the new site. This guide covers how to build that map, how to turn it into redirects, and how to check it after launch.
URL mapping vs. redirect map
The two terms describe the same job at two moments.
| URL mapping | Redirect map | |
|---|---|---|
| What it is | The plan: where every old URL goes, decided with your team | The list of permanent redirects loaded on the new site at launch |
| When | Early, while the new URL structure can still change | At launch, built from the mapping |
Build the mapping first. The redirect map is its implementation, and it is only as good as the decisions behind it.
Where the URLs come from
The map has to cover every address that search engines, other sites and people still use, not only the pages in your menu. One page often has several addresses. Collect URLs from:
- A full crawl of the live site, including files and old sections nobody links to anymore.
- Your XML sitemaps.
- Search Console: pages with impressions, and pages Google has indexed.
- Analytics: landing pages that received traffic in the last year.
- Backlinks: pages other sites link to, including old ones that already redirect.
- Files: PDFs, images and documents that rank or are linked from elsewhere.
Merge the lists and remove exact duplicates. What is left is the inventory every decision is made on.
Three ways to map a URL
Each URL gets one of three outcomes:
- One to one. The same content exists on the new site. Redirect to its new address.
- Many to one. Several old pages merge into one. Redirect each to the closest page on the new site, the one that answers the same question.
- Retire. The content is gone on purpose. Return a 404 or 410 status instead of redirecting to an unrelated page. Sending retired pages to the home page loses the visitor and tells search engines nothing useful.
Record the reason for every merge and retirement. When someone asks in six months where a page went, the map answers.
The template
One row per old URL. These columns are enough for most migrations:
| Old URL | Status today | New URL | Type | Rule or manual | Owner | QA |
|---|---|---|---|---|---|---|
| /news/2019/launch | 200 | /insights/launch/ | One to one | Rule | Content lead | Passed |
| /products/old-widget | 200 | /products/widget/ | Many to one | Manual | Product marketing | Pending |
| /promo-2018 | 200 | (none) | Retire, 410 | Manual | Marketing | Passed |
Download the template (CSV) and start with your crawl.
Pattern rules or manual mapping
Large sites cannot map tens of thousands of URLs by hand, and they should not have to. Most URLs follow patterns: a blog that moves from /news/2019/title to /insights/title/ is one rule, not thousands of rows.
- Use rules for structured sections where the old and new paths follow a pattern.
- Map by hand the pages that matter most: top landing pages, pages with backlinks, merged content and anything a rule would send to the wrong place.
- Test every rule against the full URL list, not a sample. One broad rule can catch pages it was not written for.
Enterprise cases to plan for
- Multilingual sites. Each language version is its own URL and needs its own row. Map English to English and Spanish to Spanish, never every language to one version.
- Multisite networks. Map each site separately, then check the URLs that move between sites.
- Query parameters. Campaign, filter and session parameters create many addresses for one page. Decide which ones matter and how the rules treat them.
- Old domains. Previous domains and subdomains that still redirect to the current site need to point straight at the new URLs, not at the current ones that are about to change.
Who owns the map
The map needs two kinds of knowledge. Your content and marketing leads know which pages matter, which ones merge and which ones can go. The migration engineers know how the old and new systems build URLs and how rules behave at scale. Give each section of the site one owner who signs off its rows, and keep the map in one shared file, not in emails.
From the map to redirects
- Start from the mapping, not from memory or the CMS menu.
- Use server-side permanent redirects (301 or 308). Google treats a 301 as a strong signal to process the new URL, and a 302 as a weak one.
- Point every redirect straight at its final destination. No chains: Google follows up to 10 redirect hops, and each extra hop is a chance to fail. Update older redirects so they skip the URLs you are retiring now.
- Test the full list before launch on the staging site.
Launch and the year after
- Crawl again after launch and compare the results with the map: every old URL should answer with one redirect to the right page, or with its planned 404 or 410.
- Update your XML sitemaps to list only the new URLs, and submit them.
- Monitor Search Console and analytics for errors and pages that lose traffic, and fix them from the map.
- Keep the redirects for as long as possible. Google’s guidance is generally at least a year. Old links keep pointing at the old addresses long after that.
Common mistakes
- Building the map from the CMS menu instead of a crawl, which misses older and duplicate addresses.
- Sending everything to the home page. Visitors and search engines lose the page they were looking for.
- Forgetting files: PDFs and images that rank or are linked from other sites.
- Chains, where an old URL redirects to another old URL that redirects again, and loops, where two URLs redirect to each other.
- Temporary (302) redirects left in place for a permanent move.
- Mapping too late, when the new URL structure can no longer change.
- Removing redirects a few months after launch, while old links still point to them.
How URL mapping fits a migration
The URL map is one part of the migration plan, next to the content inventory and a decision for every module. See how a migration runs, the platform guides for Drupal and Adobe Experience Manager, and check where your team stands with the migration readiness checklist.
Take the next step
Give your team the autonomy they've been waiting for
Most enterprise teams stay stuck because their CMS slows them down. You can change that today with a clear, low-friction first step.