Will redesigning my website hurt my rankings?

A redesign can hurt your rankings, but the design itself is rarely the cause: the damage comes from page addresses that change without being forwarded, and from content that gets cut or rewritten along the way. A site that keeps the same addresses, the same words and the same page titles under a new look carries little risk. Most redesigns change more than the look. Some movement in rankings after any large change is normal, and nobody can honestly promise there will be none.

What causes the drop

Nearly always something was lost in the rebuild. Old addresses that lead nowhere come first. The service page that lived at one address now lives at another, and the old one returns “not found”. Its rankings and the links pointing at it go with it. The fix is a 301 redirect, a permanent forwarding instruction, from each old address to its closest new page.

Pages get dropped as well. The old site had a page for each service and city, the new one has a tidy handful, and every search those pages answered now has nothing to land on. On the pages that survive, the text is often trimmed to suit the layout. Designers tend to prefer short copy. Google ranks a page on what it says. Titles and headings get rewritten too. The page title is one of the strongest hints about what a page is for, and a rebuild often resets them to defaults.

Then there’s what nobody sees. A site under construction is normally set to tell search engines not to list it, and if it launches with that “keep out” setting still on, pages fall out of Google. Structured data, tracking code and call tracking don’t show on the screen either, so nobody notices they are missing.

What is safe to change

Colors, type, photography and layout can change freely, as long as the words and headings on each page survive, along with its links. Menus are links, so a page removed from the menu and linked from nowhere else becomes harder for Google to find. Google also reads the phone version of your site, a practice called mobile-first indexing, so check that the new design shows the full content on a phone and doesn’t hide half of it.

What to do before launch

Write down what you have before anyone changes it. In order:

1. Record a baseline: where you rank across your service area, and which pages bring visits and calls. Google Search Console and Google Analytics hold most of this.
2. List every address on the current site, including pages that aren’t in the menu.
3. Match each old address to one new address, the closest in subject. Not everything to the home page.
4. Carry the titles, headings and text of pages that already rank across unchanged. Improve them later, one at a time, so you can see what each change did.
5. Build on a private copy and test every redirect there.
6. On launch day, turn off the “keep out” setting, submit the new sitemap in Search Console and spot-check old addresses by hand.

I’d start with step one every time. Without a baseline, an owner in Chula Vista who feels the phone go quiet after launch has no way to tell a real loss from a slow week.

What to watch afterward

After launch, the page indexing report in Search Console shows whether the count of “not found” addresses is rising. Compare rankings and calls with the baseline too. A period of settling is common. If one page has dropped and stayed down, compare its old version with its new one, which is why it pays to keep a copy of the old site.

When a redesign helps

Sometimes the old site was the problem. If it was slow on a phone, hard to read or hard to call from, a better build can improve both rankings and the share of visitors who get in touch. The aim is to keep what was working and replace what wasn’t. I plan and check rebuilds this way as part of site migrations.