Redesigning without losing traffic: the redirect map nobody budgets for
Traffic is usually lost after a redesign because old URLs stop existing. Before launch, list every old URL that has impressions, backlinks or sitemap entries; map each one to its closest new equivalent with a permanent 301 redirect; keep the content and titles that earned rankings; and after launch, watch Search Console for 404s and compare top pages week by week. A dip of a few weeks is normal. A decline lasting beyond two months means something was missed.
The redesign is the moment companies most often lose what they built in search. Not because the new site is worse, but because the old site had addresses Google knew and the new one doesn’t.
What actually gets lost
Google ranks pages, not websites. Each page lives at a URL, and that URL accumulates history: rankings, links from other sites, clicks.
When the new site uses a different structure, /services/web-design/ instead of /web-design.html, the old URL returns an error. After a while Google concludes the page is gone and drops it. Everything it earned disappears, and the new page starts from nothing.
The redirect map
The fix is a permanent 301 redirect from every old URL to its closest new equivalent. Google then transfers the old page’s history to the new one.
The process:
- Inventory old URLs. Export every page with impressions from Search Console. Add pages with backlinks and everything in the old sitemap.
- Match them. For each old URL, pick the most relevant new page. Service to service, case study to case study, category to category.
- Implement before launch. Redirects go in at the server or hosting layer and must be live the moment the new site is.
- Verify after launch. Open every old URL and confirm it lands where it should.
When we rebuilt our own site, the old one was indexed under URLs the new structure didn’t have. We built a map of 79 redirects that covers about 77% of the impressions the old site had in search, plus a script that checks after every change that they still resolve. On our hosting, a single malformed line in the redirect file can break a deploy, so the script checks the format before anything else.
The common mistakes
Everything to the homepage. Faster to set up, and treated by Google much like missing pages.
Cutting the copy that ranked. New designs often mean shorter pages. If an old page ranked because it answered specific questions and the new one doesn’t, rankings fall even with a correct redirect.
Staging sites in the index. A copy of the site on a temporary URL without a noindex directive can end up in Google as a duplicate.
Noindex left on in production. The reverse problem: the directive that protected staging ships with the live site, and the whole site drops out of search within days. It is a one-line change, which is exactly why it gets missed.
Changed page titles. Titles are among the strongest on-page signals. If an old title ranks well, don’t change it just because the design changed.
The first four weeks
- Search Console page indexing report. A spike in 404s means a redirect was missed.
- Top pages, old versus new. Compare your strongest old pages with their new counterparts.
- Leads. In the end, the only number that matters.
Before you sign the redesign
Ask whoever is building the new site: who builds the redirect map, when, and how is it verified? If the answer is vague, that is not a detail. It is the most expensive part of the project, and it isn’t in the proposal.
If you are an agency handing a rebuild to a partner, make the redirect map a named deliverable in the brief, whoever the partner is. That includes us, if you work with our white label team.
Common questions
Can I redirect all old URLs to the homepage?
You can, but Google tends to treat mass redirects to the homepage much like missing pages, because the homepage doesn't answer what the old page did. Map each URL to its closest match. If there is no reasonable match, a 404 is more honest than a homepage redirect.
How long does recovery take?
When the migration is done properly, fluctuations usually settle within two to six weeks as Google recrawls. If traffic is still well below baseline after two months, something specific was missed, usually redirects or removed content.
Is a domain change riskier than a redesign?
Yes. A domain change adds Search Console's change of address tool on top of redirects, and recovery typically takes longer. Unless there is a strong business reason, redesign on the existing domain.
