A new website should be a step forward. Too often it's a step back — the design is beautiful, everyone's proud of it, and three weeks after launch the organic traffic has fallen off a cliff. It's one of the most common and most painful outcomes in our field, and the frustrating part is that it is almost entirely preventable.
The traffic doesn't vanish because the new site is worse. It vanishes because the redesign quietly broke the signals Google had spent years learning to trust: the URLs, the content, the internal links, the technical fundamentals. This is a guide to keeping every one of those signals intact through a relaunch.
01Why redesigns lose rankings
Four failure points cause the overwhelming majority of the damage. Recognising them is half the battle.
The first is broken URLs. A new site structure or CMS changes the address of a page, the old address 404s, and every ranking and backlink pointing at it is orphaned. The second is lost content. In the pursuit of a cleaner design, the copy that was actually ranking gets trimmed, merged, or dropped — and the relevance goes with it. The third is technical regressions: a staging site's "block search engines" setting shipped to production, a missing sitemap, structured data that didn't come across. The fourth is a slower site — a heavier, flashier build that fails the speed and interaction thresholds the old one passed.
Every one of these is avoidable with a plan. Here is the plan.
02Before you touch the design: measure and map
The single most important work happens before a pixel moves.
Crawl and record the current site
Take a full inventory of the existing site while it still works: every URL, its title and meta description, its headings, its word count, and its current search performance from Search Console and analytics. This is your baseline and your insurance. You cannot protect what you never wrote down.
Identify your winners
Not all pages are equal. Find the pages that bring in organic traffic, hold rankings, or carry backlinks. These are the pages a redesign must treat with the most care — ideally by keeping their URL and content largely intact. A redesign is a bad time to gamble with a page that's already working.
Build a URL map
If the URL structure is changing at all, create a spreadsheet mapping every old URL to its new destination. Every single one. This map becomes your redirect file, and it is the difference between a clean migration and a month of firefighting.
03Redirects: the step that saves you
When a URL must change, a 301 redirect — a permanent redirect — tells search engines the page has moved and passes its accumulated authority to the new address. Skipping this is the number-one cause of post-launch traffic loss.
# Every changed URL needs its own 301. Example (Nginx):
location = /old-services-page {
return 301 /services/web-development;
}
# Avoid long redirect chains — always point old → final destination,
# never old → interim → final.A few rules that matter in practice: redirect each old URL straight to its true new equivalent, not to the homepage (a pile of redirects to the homepage is treated as good as a 404 for ranking purposes). Avoid chains where one redirect points to another. And test the whole map on staging before launch, not after.
04Preserve what already works
A redesign is a visual project that quietly depends on editorial discipline.
- Keep the content that ranks. If a page earns traffic, its new version should say at least as much, on the same topic, with the same intent. Redesigns love to shorten copy; search rewards substance. Trim genuinely, not aggressively.
- Carry over metadata. Titles and meta descriptions that are working shouldn't be rewritten wholesale just because everything else is new.
- Maintain internal links. The links between your pages tell Google what's important. Rebuild them in the new site rather than letting the redesign flatten your structure.
- Bring your structured data across. Article, Organization, Product, FAQ and LocalBusiness schema often get left behind in a rebuild. Port it, and take the opportunity to improve it.
- Protect your speed. A heavier new site can fail the interaction and loading thresholds the old one passed. Build performance in from the start, not as a post-launch fix — we explain the current bar in protect your Core Web Vitals.
05Launch day and after
The migration isn't finished when the new site goes live. The first days are when problems surface.
- Confirm search engines can crawl the new site. Check that no "disallow all" robots rule or "noindex" tag survived from staging — this single oversight has sunk more launches than any other.
- Submit the new sitemap in Search Console and make sure it lists the live URLs.
- Spot-check redirects across your most important old URLs. Every winner from your inventory should resolve to its new home in one hop.
- Re-crawl the live site and compare against your baseline: missing pages, broken links, orphaned content, changed titles.
- Watch, don't panic. A brief dip as Google re-crawls and re-learns the new site is normal. A sustained drop after a week means something on this list was missed — go back and find it.
06A word on AI search
Rankings are no longer the only thing a redesign can cost you. The same signals that keep you in Google's classic results — clear content, clean structure, trusted URLs — are what keep you cited in AI answers too. A redesign that preserves your SEO generally preserves your AI-search visibility as well, but it's worth checking both. We cover the second half in staying visible in AI search.
07Frequently asked questions
Will I lose my Google rankings if I redesign my website?
Not if the redesign is planned properly. Rankings are lost when URLs break, content is dropped, or technical SEO regresses — all avoidable. A redesign that keeps URLs where possible, redirects the rest, and preserves ranking content typically keeps its rankings, with only a short settling period after launch.
How long does it take to recover if traffic drops after a redesign?
It depends on the cause. A short dip while Google re-crawls the new site usually settles within a few weeks. A drop from a real mistake — broken redirects, a stray noindex, lost content — persists until you fix the mistake, then recovers over the following weeks. The fix is what matters, not waiting.
Do I need to redirect old URLs if the content is the same?
If the URL address changes, yes — you need a 301 redirect from old to new even when the content is identical, so search engines and existing links follow the page to its new address. If the URL stays the same, no redirect is needed.
Should I keep the same content in a redesign?
Keep the substance of any page that's ranking or earning traffic. You can improve and modernise it, but don't strip it down — the words are part of why it ranks. New design, same or stronger content is the safe formula.
08Where this leads
A redesign should grow your business, not set it back. The difference between the two is entirely in the preparation: the inventory, the URL map, the redirects, and the discipline to protect what already works. Done well, you get a better-looking, faster site and the rankings you've already earned.
This is exactly the kind of project where it pays to know what to ask for — see questions to ask before you sign. When you're ready, our web development team plans redesigns SEO-first from day one. Plan your redesign with us.
