What a redirect map is and why your redesign needs one

What a redirect map is in plain terms

You've maybe heard a story shaped like this before: a business redesigned its site, and the search traffic that used to arrive quietly dropped off soon afterward. The cause, in a surprising number of these stories, is simple and entirely preventable: a missing redirect map.

A redirect map is just a planned list. Every URL on the current site, paired with exactly where it should point after the redesign goes live. If yoursite.com/services becomes yoursite.com/what-we-do, the map spells that connection out, and it gets built into the new site technically, not left for visitors to stumble through themselves.

Why every old URL needs a planned destination

Every page on your current site that's ever been linked to, bookmarked, or indexed by a search engine carries some value attached to it, even pages you personally don't think about much day to day. When that page's URL disappears with no planned replacement, all of that accumulated value, the links, the search visibility, the bookmark someone saved two years back, leads nowhere at all.

A redirect map isn't about keeping every old URL forever, out of some obligation. It's about deciding, deliberately and in advance, what each one becomes, instead of letting the question answer itself by accident during a rushed launch.

Think of it as a forwarding address for every page on the old site. Mail still arrives. Nothing gets lost in transit because someone wrote the new address down first.

What happens to visitors and search engines without one

Without a redirect map, a visitor clicking an old link, or a search engine trying to revisit a page it already knows well, hits a dead page, shown as a "not found" error on screen. Visitors mostly just leave at that point. Search engines treat the dead end as a real signal that the page is genuinely gone, and over time, they stop sending traffic there entirely.

This quiet mechanism is behind most redesign traffic drops people hear about secondhand. It's not a punishment for redesigning at all. It's old signals pointing at nothing, with nobody catching the gap before launch day arrives.

The frustrating part is how avoidable it is. Nothing about building a redirect map requires special tools or advanced skill. It requires someone deciding to sit down and do it, and someone else confirming it actually got done.

It's a checklist item, not a mystery. Treated that way, it rarely gets skipped by accident, and it's a fair thing to ask about by name during any planning conversation, however early that conversation happens to be.

How this connects specifically to keeping search rankings intact through the whole process is covered at how to redesign a website without losing your google rankings.

Building the map from an inventory of the old site

A redirect map starts with a complete list of the current site's URLs, every page, not just the handful in the main navigation menu. From there, each URL gets matched to its closest equivalent on the new site, or gets marked deliberately as retired if there's genuinely no equivalent left.

This is tedious for a site with dozens of pages, and it's genuinely time-consuming for a site with hundreds. It's also not optional if you actually want the redesign to preserve everything the old site already earned over time.

A spreadsheet works fine for this. One column for the old URL, one for the new destination, one for a short note on why. Nothing fancier is required to get it right.

If your site has a sitemap file, that's a useful starting point for the URL list, since it's already meant to be a complete inventory of what exists. It won't catch everything on its own, so still check it against the site itself page by page, including anything that only shows up buried a few clicks deep.

The inventory step overlaps heavily with deciding what content survives the rebuild in the first place, which is its own topic covered at what happens to your old content during a website redesign.

The difference between a redirect and just deleting a page

Sometimes a page genuinely should go away entirely. A service you no longer offer. An event long past and no longer relevant. Deleting it isn't automatically the wrong call.

The real difference is intent. A redirect map means someone actually looked at that page and decided, deliberately, where it should now point, or that it should retire on purpose.

A page that simply vanishes with no decision behind it differs sharply from a page that was reviewed and retired intentionally. The map is what turns "it just vanished" into "someone actually decided," and that distinction matters more than it sounds like it should.

Checking the map actually works after launch

Once the new site is live, actually test a sample of the old URLs yourself, pulling a handful from the list and checking they land exactly where the map says they should. Redirect maps get planned correctly on paper and then implemented imperfectly more often than most people expect going in.

Pick a mix when you test: a few popular pages, a few obscure ones, and anything with an unusual URL structure. Problems tend to hide in the unusual cases, not the obvious ones everybody already checked first. Give this a real half hour, not a quick glance.

This testing step belongs inside the broader scope of the project as a whole, which is why it's worth confirming a redirect map is explicitly included when you scope a website rebuild before getting quotes. The redirect map itself is one piece of the larger process laid out at how to redesign a website without losing what works.

More from the blog

All posts