Learning how to map old URLs to new ones during a migration is the single most protective step you can take when moving, redesigning, or restructuring a website. What is URL mapping? It is a simple document that pairs every old address with its new destination, so each page's visitors and search value land in the right place. Who needs it? Anyone changing domains, platforms, folder structures, or page names, from a small business to a large publisher.
When should the map be built? Before launch, while the old site is still live and easy to inventory, never as a scramble afterwards. Where do migrations go wrong most often? In the gaps: forgotten subfolders, redirected chains, and old pages sent to the homepage instead of their true replacements. Why does this matter so much? Because every unmapped URL is a broken promise to readers, bookmarks, and search engines that trusted the old address.
How do you build a map you can trust? You inventory everything, match pages by purpose rather than by name, and test the result before and after launch. This guide walks through that process in a calm, orderly way, so your migration keeps the traffic and rankings you worked to earn.
Search engines treat a URL as the identity of a page. When that address disappears without a redirect, the rankings, links, and history attached to it are at risk. A one-to-one redirect tells search engines the content moved, and most of its value moves with it.
Start by listing every old URL that exists, not just the ones in your navigation. Export pages from your content system, crawl the site, check your sitemap, and review analytics for addresses that still receive visits. Search Console data is especially useful because it shows URLs search engines actually know about.
Then decide the destination for each one. Match by topic and purpose: a product page goes to its replacement product page, a guide goes to the updated guide. When no close match exists, choose the most relevant category page rather than defaulting everything to the homepage.
Google's explanation of featured snippets and rich results is a useful reminder of how much structured visibility a strong page can earn, and therefore how much a careless move can lose. Pages holding special search features deserve extra care in the map. Flag them, verify their new versions keep the content that earned the feature, and test them first after launch.
Use permanent 301 redirects for pages that have moved for good, since they pass the strongest signal that the change is final. Avoid chains where one redirect points to another redirect, because each hop wastes crawl effort and slows visitors. Every old URL should reach its final destination in a single step.
Test before launch on a staging version wherever possible, then test again the moment the new site is live. Click through the top pages yourself, and crawl the redirect list with a tool to catch loops, chains, and accidental 404s. The migration checklists on our blog offer more detail on launch-day testing routines if you want a second reference.
For the first few weeks, monitor Search Console coverage, your 404 report, and traffic to the mapped pages. A healthy migration shows old URLs dropping out as new ones take their place, with overall traffic holding steady. Spikes in errors or sudden drops in a section mean a mapping gap needs fixing fast.
Not every old page deserves a redirect to a near twin. Pages that were thin, outdated, or part of a discontinued line may be better retired honestly. Redirecting irrelevant pages to unrelated content misleads visitors and dilutes the signal, so let genuinely dead pages return a proper 404.
Finally, update your own internal links to point directly at the new URLs. Redirects are a safety net, not a linking strategy. A site that links internally to its final addresses loads faster, crawls cleaner, and avoids depending on redirect rules forever.
Testing a long redirect map means opening hundreds of addresses without losing your afternoon, so try Open All URLs to load your old and new URL lists in batches and spot failures at a glance. Run it before launch and again on launch day, and you will catch the broken rows while they are still cheap to fix.
No. Sending unrelated pages to the homepage confuses visitors and is treated as a soft error by search engines. Redirect to the closest relevant category or topic page instead, and let pages with no sensible home return a genuine 404.
Keep them for at least a year, and ideally indefinitely if you control the old domain. External links and bookmarks can point at old addresses for many years. Removing redirects early discards traffic and link value you already preserved.
A 301 signals a permanent move and passes the page's history to the new URL, which is what migrations need. A 302 signals a temporary move and is right for short-term changes only. Using 302s by accident can delay search engines from trusting the new addresses.
Start with pages that have traffic, backlinks, or search features, then work through the rest by section. Analytics and Search Console data show where the value is concentrated. Even on huge sites, a small share of URLs usually carries most of the risk.