Will a Redesign Hurt My Rankings?

Yes — a redesign can absolutely cost you rankings. It happens in Spokane constantly, and it’s almost never because the new site looks worse. It’s because the new site is a different site as far as Google is concerned, and nobody told Google that.

The good news is that every way this goes wrong is known, listed, and preventable. Here’s the actual mechanism, and the checklist that stops it.

Why rankings drop after a redesign

Google doesn’t rank “your website.” It ranks individual URLs, each carrying its own history: the links pointing at it, the queries it’s known for, how long it’s been around, how people behave when they land on it.

A redesign puts every one of those at risk in four specific ways.

1. URLs change and nothing points the old ones at the new ones

This is the big one. Your old /services/roof-repair/ becomes /what-we-do/roofing/, the old URL now returns a 404, and every link and every ranking attached to it evaporates.

Google will eventually find the new page. It will not automatically know it’s the same page, and it will not hand over the old page’s history. Ten years of accumulated authority, gone, because a URL got tidier.

The fix: a redirect map. Every old URL, 301’d to its closest new equivalent, before launch. Not to the homepage — to the equivalent page. A mass redirect to the homepage is treated as a soft 404 and passes almost nothing.

2. Content gets “cleaned up”

Designers reduce word count. It’s a reflex, and usually a good one — most pages are cluttered.

But the 900 words on your service page weren’t clutter to Google. They were the reason it understood what that page was about. Cut them to 200 punchy words and you’ve removed the evidence for the ranking.

The fix: compare word count and topic coverage page by page, before and after. Trim genuinely redundant copy. Don’t trim the substance and call it minimalism.

3. Heading structure gets rebuilt around the design

An <h1> becomes a styled <div> because the designer wanted different type. Six <h2>s become one <h1> and five <span>s. The visual hierarchy is identical; the machine-readable hierarchy is gone.

The fix: headings are content structure, not styling. Style them however you want — but keep one <h1> per page carrying the page’s actual subject, and keep the outline intact underneath.

4. The new site is slower than the old one

Page builders and heavy templates routinely ship a six-second Largest Contentful Paint. Core Web Vitals are a ranking signal, and worse, a slow page bleeds conversions independently of where it ranks.

The fix: set a Core Web Vitals budget before design starts and measure against it before launch, not after.

The pre-launch checklist

Run all of it. Every item has cost somebody their rankings.

Before you build

• Export every indexed URL — Search Console, plus a full crawl of the current site
• Record current rankings and organic traffic. This is your baseline, and without it you cannot prove afterward whether the redesign helped or hurt
• Note which pages carry backlinks. Those are the ones you cannot afford to lose
• Set the Core Web Vitals target

While you build

• Build the redirect map as URLs change, not at the end from memory
• Keep the heading outline of every page that currently ranks
• Keep the substantive copy on pages that currently rank. Rewrite it better if you like — don’t delete it
• Keep the internal links. They’re how authority moves around your site
• Carry the schema over, and improve it while you’re in there

Launch day

• Redirects live at launch, not the week after
• Crawl the new site and confirm no 404s from the old URL list
• Confirm the staging site’s noindex did not ship to production. This one takes sites out of Google entirely, and it is more common than you would believe
• Submit the new sitemap in Search Console
• Confirm analytics and Search Console are still recording

The first month

• Watch Search Console coverage for crawl errors daily for the first week
• Compare rankings against the baseline at 2 and 4 weeks
• Expect some movement. Two to four weeks of mild turbulence while Google re-crawls and re-evaluates is normal

What “normal turbulence” actually looks like

Even a clean migration wobbles. Google has to re-crawl every URL, follow every redirect, and re-assess pages that changed.

Normal: modest ranking fluctuation for two to four weeks, recovering to baseline or better.

Not normal: an immediate drop across the board on day one, pages disappearing from the index, or a decline still deepening after six weeks. Those are symptoms of a specific broken thing — usually redirects, usually fixable, and much more fixable in week one than in month three.

This is exactly why the baseline matters. Without one, every conversation after launch is a guess.

The honest answer

A redesign done carelessly will cost you rankings. A redesign done properly usually improves them — because the same work that protects your rankings (clear structure, meaningful internal links, faster pages, better copy) is the work that raises them.

The difference isn’t luck, and it isn’t the designer’s taste. It’s whether anybody planned for search before the design was finished.

If you’re weighing a redesign and want to know what’s actually at risk on your specific site, that’s what the free teardown is for — what you currently rank for, what a rebuild would put at risk, and what it would take to do it without the drop. No pitch, straight answer.