The short version: A redesign doesn’t cost you your Google rankings — a redesign done without a URL plan does. The usual failure is quiet and mechanical: a page gets rebuilt, saves under a slightly different address, the old address starts returning “not found”, and every bit of authority that page had built goes with it. It takes an hour or two to prevent and months to recover from, and almost nobody puts it in the quote.
What actually carries your Google rankings?
Your URLs, and the links pointing at them.
This is the bit that gets lost in a redesign conversation, because a redesign is discussed visually — layouts, colours, photography. But Google doesn’t rank your website. It ranks individual pages, at individual addresses. Everything a page has earned — the links pointing to it from other sites, the history it’s built, the position it holds — is attached to that address.
Change the address without telling anyone, and as far as Google is concerned the page that earned all that no longer exists.
The design can change completely. The addresses need a plan.
How does a redesign actually lose them?
Usually like this, and it’s more mundane than you’d expect.
Say your About page lives at /about. During the rebuild someone creates a new About page. The old one is still sitting there in the background, so the new page can’t have the same address — it quietly saves as /about-2. Nobody notices, because on the front end it looks perfect and the menu points to the right place.
Then the old page gets deleted or unpublished. Now /about returns a 404. Every link any other website ever pointed at your About page lands on nothing. The authority that page had accumulated doesn’t transfer to /about-2 — there’s no connection between them. The new page starts from zero.
The same thing happens with small wording changes nobody thinks twice about: /contact becomes /contact-us, or the other way round. Services becomes services-and-pricing. Each one is a page starting again.
Multiply that across a whole site and you have the thing people describe as “we got a new website and our traffic died.” It usually wasn’t the design.
Why does this happen so often?
Because it isn’t anybody’s job unless someone makes it their job.
The person building the site is building the site. They’re matching the design, getting it responsive, making the forms work. The URLs are an implementation detail that happens automatically, and automatic is exactly the problem — the platform picks an address that doesn’t clash with what’s already there, and a clashing address is precisely what you want when you’re replacing a page.
It’s also invisible at handover. The site looks finished. Everything works. You don’t find out for six to eight weeks, when the rankings have drifted and nobody can point to what changed.
What should happen instead?
You map the URLs before the build, not after.
It isn’t complicated work, it’s just work nobody bills for:
List every URL on the current site first. All of them, before anything is touched. Your sitemap is the starting point; a crawl catches the rest.
Decide what each one becomes. Most should keep exactly the address they have — that’s the cheapest ranking protection there is. If a page is being merged into another, or genuinely retired, note where it should send people instead.
Build to those addresses. If you’re replacing /about, the new page should end up at /about, not beside it. That usually means removing or renaming the old page first so the address is free.
Redirect everything that moved. A 301 redirect from every old address to its new home. Not a page saying “this has moved” — an actual redirect, so Google passes the authority along.
Check it after launch. Crawl the new site, look for 404s, and watch Search Console for pages that suddenly stopped existing.
That’s an hour or two of planning on most small business sites, and it’s the difference between a redesign that keeps its momentum and one that starts from scratch in every sense.
What if you’re changing platform as well?
Then treat it as the higher-risk version of the same job.
Moving between platforms tends to force URL changes, because different systems structure addresses differently — some impose prefixes you can’t remove. So the mapping matters more, not less, and there’s more of it to do. The principle doesn’t change: know every old address, decide its new home, redirect it.
Worth knowing before you start, rather than discovering halfway through.
What if it’s already happened?
Some of it is recoverable, and it’s worth trying.
Find the old addresses — Search Console will show pages that were getting impressions and stopped, and an old sitemap or the Wayback Machine will fill in the rest. Work out what each one should now point to. Then put the redirects in.
Be realistic: the longer a URL has been returning 404s, the more ground you’ve lost, and some of those external links may never be crawled again. But redirects put in late still work better than redirects never put in at all, and it’s usually a short job for a decent result.
The honest summary
A redesign is not a risk to your rankings. Handing one to someone who hasn’t thought about URLs is.
If you’re getting quotes, it’s a fair question to ask: what’s your plan for our existing URLs? Anyone who does this properly will have an answer ready. It’s a good way to tell who’s rebuilding your website and who’s just building a website.
Planning a redesign and want to keep what you’ve already earned? We map URLs and redirects before a build, not after — and if you’re not sure whether you need a rebuild at all, start here instead. See how we approach WordPress web design, or get in touch.
FAQ
Will a new website hurt my Google rankings?
Only if the URLs aren’t handled. A redesign that keeps its addresses, or redirects the ones that change, generally holds its rankings — the design itself isn’t what Google is ranking. The damage comes from old addresses starting to return 404s while the new pages sit at slightly different ones with no connection between them.
What is a 301 redirect and why does it matter in a redesign?
It’s a permanent instruction that a page has moved, and it passes the old page’s accumulated authority to the new address. Without one, an old URL simply stops existing and everything it earned stops counting. It’s the single most important technical step in any redesign that changes addresses.
Why did my traffic drop after a website redesign?
The most common cause is URL changes that were never redirected — pages saving as /about-2 while /about 404s, or /contact quietly becoming /contact-us. Check Search Console for pages that were getting impressions and suddenly stopped, then map redirects from the old addresses to the new ones.
Can I keep my URLs the same when I redesign?
Usually, and you generally should. Keeping an address is the cheapest possible way to protect what a page has earned, and there’s rarely a good reason to change one purely because the design is changing. Changing platform can force some changes — that’s when a proper redirect map matters most.
