Mapping Old Pages to New URLs So No 301 Dead-Ends
Moving to a better domain? Don't send every old page to your new homepage. Here's how to map old URLs to new pages during a 301 redirect so nobody hits a dead end.
You picked a better domain name. Now you have to move your website to it without dropping the customers and search rankings you already have. The tool for that is a 301 redirect. It tells a browser and Google, "This page lives somewhere new now — send everyone there."
The part people get wrong is the mapping. They point every old page at the new homepage and call it done. That works for the homepage. It quietly breaks everything else. If you want to map old URLs to new pages during a 301 redirect the right way, you line up each old page with its real match on the new site. One for one, wherever you can.
What a 301 dead-end actually is
A dead-end is when someone clicks a link or a search result expecting your pricing page — and lands on your homepage instead. The page they wanted is gone, and nothing on screen says where it went. They bounce. You just lost them.
It happens more than you'd think. Say a customer bookmarked your old "Emergency AC Repair" page. Or another plumber's blog linked to your "How We Quote a Job" page three years ago. Those are real paths to your door. Send them all to the homepage and the visitor has to go hunt for what they came for. Most won't.
Google treats it the same way. When it sees dozens of old pages all dumping into the homepage, it reads that as those pages no longer existing. The credit they earned — from other sites linking to them, from years of being indexed — doesn't carry over to the right new page. It gets watered down or lost.
The simple rule: old page to its twin
Here's the whole idea in one line. Every old URL should point to the new page that does the same job.
- Old homepage → new homepage
- Old "Services" page → new "Services" page
- Old "Kitchen Remodels" page → new "Kitchen Remodels" page
- Old "Contact" page → new "Contact" page
When the twin exists, send the visitor straight to it. That keeps the person on track and hands the page's earned credit to the page that deserves it.
When there's no exact twin
Sometimes the new site doesn't have a one-for-one match. Maybe you combined three thin service pages into one strong page. That's fine. Point all three old URLs at the one new page — as long as that page genuinely covers what the old ones did. The closer the match, the better it works. Sending a page about drain cleaning to a page about drain cleaning is good. Sending it to the homepage is the dead-end you're trying to avoid.
How to build your map
You don't need special software. You need a list and an afternoon.
- Pull every old URL. Your old site's sitemap is the fastest source. It's usually at yourdomain.com/sitemap.xml. If you're not sure, your web person or site builder can export the page list.
- Put them in two columns. Old URL on the left. New URL on the right. A plain spreadsheet is perfect.
- Fill in the match for each row. Go line by line. Find the twin on the new site and paste it in.
- Flag the orphans. Any old page with no good match? Decide where it best fits. Only fall back to the homepage when nothing else comes close.
- Check the ones that get traffic. If a handful of old pages bring in most of your visitors or have links from other sites, double-check those first. They matter most.
Once the map is done, whoever handles your redirects sets them up from that list. If you're doing it yourself, most hosts and registrars have a redirect tool with step-by-step help. Google's own guide to site moves with URL changes is a solid plain-English reference for the person doing the work.
Two mistakes that undo good mapping
Even a clean map can leak if the setup is sloppy.
First, watch for redirect chains — old page points to a second old page, which points to the new one. Each hop costs you a little and slows the visitor down. Point the old URL straight at the final destination. We go deeper on this in Redirect Chains and Loops: How They Quietly Leak Domain Authority.
Second, use the right kind of redirect. A 301 means "moved for good," which is what you want. A 302 means "temporary," and search engines treat it differently. If you're unsure which you've got, 301 vs 302 Redirects: Which One Protects Domain Authority? lays it out plainly.
How to know it worked
After the redirects go live, test them. Type a few of your old URLs into a browser and make sure each one lands on the right new page — not the homepage, not an error. Check the pages that matter most first. If you want the full before-and-after process for moving a name, How to 301 Redirect an Old Domain to Preserve Its Authority walks through it.
Good mapping is boring work. It's also the difference between a move that keeps your customers and rankings, and one that starts you back at zero on a nicer name.
Thinking about a better name but not sure it's worth the move? You can browse names for your city and trade in under a minute, or ask us about one specific domain you already have in mind. No pressure either way — just a straight answer.
