Short answer: it can, and when it does, the new design is almost never the reason. Google does not punish you for a fresh look. It punishes you, in effect, for things that disappeared or moved during the switch and were never accounted for.
Most of the horror stories follow the same script. The new site launches. It looks great. Three weeks later the phone is quieter, and the Search Console graph shows a cliff. By the time anyone notices, the old site is gone and nobody kept a list of what was on it.
Here is what actually causes that cliff, and what a careful rebuild does about each one.
URLs changed and nothing redirected
This is the big one, and it causes most of the damage on its own.
Every page on your current site has an address. Google has been ranking some of those addresses for years. Other websites link to them. When a new site uses different addresses and the old ones simply stop working, Google treats every one of those pages as gone. The rankings do not transfer to the new page automatically. They evaporate.
The fix is a redirect map: a list of every old URL and the new URL it should send people to, applied as permanent redirects before launch. If a page is being retired, it redirects to the closest relevant page, not the homepage. If a page is being merged into another, it redirects there. Nothing goes to a dead end.
If the person rebuilding your site has not asked for, or produced, a list of your current URLs, this step is not happening.
Pages got dropped because they looked unimportant
Old sites accumulate pages. A blog post from 2019. A service you barely offer anymore. A page for a neighborhood you rarely work in. During a redesign it is tempting to cut all of that and launch something clean.
Some of those pages are earning. Not a lot each, but together they can be a meaningful slice of traffic, and a few of them might be the only pages ranking for a query your customers actually use. Cutting them without checking is throwing away rankings you already paid for.
Before anything gets cut, look at Search Console for the last twelve months and sort pages by clicks. Anything with real traffic either stays, gets rewritten in place, or gets merged into a page that redirects properly. The ones with nothing can go.
The content got shorter
Designers like white space. Search engines like words. A redesign that turns a 600 word service page into a headline, three icons, and a button has removed most of what Google was using to understand that page.
You do not need walls of text. You need each service page to say, in plain language, what the service is, who it is for, where you offer it, and what people usually ask about it. If the new design cannot hold that, the design is wrong for the job.
Titles and descriptions got reset
Every page has a title tag and a meta description that show up in search results. On a working site, these have usually been tuned over time, deliberately or by accident, to match what people search. A rebuild that generates fresh ones from scratch, or leaves them as "Home | Your Company," throws that away.
Carry the existing titles over where they are working. Improve the ones that are not. Do not let the new platform auto-generate them and call it done.
The new site is slower or broken on phones
This one is not about losing what you had. It is about the new site introducing a problem the old one did not have. Heavy page builders, uncompressed hero images, five fonts, and a chat widget can make a brand new site slower than the ten year old one it replaced. Google measures this from real visitors, and most of your visitors are on phones.
Test the new site on a phone over cellular before launch, not on a laptop in the office.
Google was never told
A small thing that gets missed. After launch, Search Console still has the old sitemap. The new one needs to be submitted, the old one removed, and the key pages requested for recrawl. If the domain or the www prefix changed, that has to be declared too. Without this, Google finds the new site eventually, but eventually can be weeks, and weeks is the gap where the phone goes quiet.
What a redesign done right looks like
- A full list of current URLs with their traffic, before any design work starts.
- A redirect map for every URL that changes or goes away, live at launch.
- Earning pages kept, rewritten, or merged. Never silently dropped.
- Titles and descriptions carried over or improved, not reset.
- Speed tested on a phone before launch.
- Sitemap submitted and recrawl requested the day the site goes live.
- Search Console watched daily for the first month, so a drop gets caught in days rather than discovered in a quarterly report.
None of this is complicated. It is just work, and it is the work that gets skipped when a rebuild is quoted on design alone.
If you are planning a redesign and want to know what is at risk on your current site, book a strategy call. The first thing we will do is look at what the site is earning today, so you know what you are protecting.