Traffic falls after a redesign for one main reason: the old URLs stopped existing and nobody told Google where they went. A redirect map prevents most of the damage, and the rest comes down to not throwing away the content that was ranking.
Record what you have before touching anything
You cannot protect what you have not measured. Before the rebuild starts, export your top pages by clicks and impressions from Google Search Console, take a full list of current URLs, and note which pages carry links from other sites.
Save it somewhere outside the site. This becomes the checklist you verify against after launch.
Keep the URLs that already rank
The cheapest way to keep rankings is to not change the address. If a page ranks and its URL is reasonable, leave it exactly as it is. Restructuring for tidiness alone is rarely worth the risk.
Where a URL genuinely has to change, plan it deliberately rather than letting a new CMS invent its own structure.
Build the redirect map
Every old URL that disappears needs a 301 redirect to the closest equivalent new page. One to one, to the most relevant destination.
Two habits cause most of the losses: sending everything to the homepage, which tells Google those pages had no specific value, and chaining redirects through several hops. Map each old address straight to its new one.
Carry the content across
A common pattern in redesigns is cutting text for visual reasons. If a page ranks for a topic, the words on it are part of why. Trim them heavily and the ranking usually goes with them.
Rewrite for quality by all means. Keep the subject coverage.
Preserve the metadata
Titles, meta descriptions, heading structure, image alt text, and structured data all need to survive the move. Rebuilds often drop schema entirely because the new templates were never given it.
Check speed before you launch
New sites frequently ship heavier than the ones they replace, usually through uncompressed images and video. Core Web Vitals feed into rankings, so measure on a real connection before launch rather than after.
Launch, then verify deliberately
On launch day: confirm the site is not blocking crawlers in robots.txt, submit the updated sitemap in Search Console, and spot-check redirects from your saved list of top pages.
Then watch. A small dip in the first two to four weeks is normal while Google recrawls. A sharp drop that does not recover usually means broken redirects, and the fix is almost always in the map.
Rebuilding an existing site?
We migrate content and rankings across carefully, so a redesign does not cost you the traffic you already earned.
Talk to usCommon questions
How long does it take for rankings to recover after a redesign?
Usually two to four weeks for Google to recrawl and settle, assuming redirects are correct. If traffic has not recovered after six weeks, something structural is wrong and the redirect map is the first place to look.
Should I keep my old URLs when redesigning?
Where they are sensible, yes. Keeping a ranking URL unchanged is the safest option available. Change them only where there is a real reason, and redirect one to one when you do.