Google: If You Redesign Your Site Your Rankings May Go Nuts

Jan 30, 2023 - 7:31 am 4 by

Google Waves

Gary Illyes from the Google Search Relations team posted another PSA on LinkedIn. This time he said, "when you redesign a site, its rankings in search engines may go nuts."

Yes, this is probably super obvious to most of you reading this site but Gary dives a bit deeper.

He said, "Among other things, search engines use the HTML of your pages to make sense of the content. If for example you break up paragraphs, remove H tags in favor of CSS styling, or add breaking tags (especially true for CJK languages), you change the HTML parsers' output, which in turn may change the site's rankings."

In short, when redesigning, sure - go ahead - make the site pretty. But changing the core HTML can result in ranking changes.

Gary recommends, "try to use semantically similar HTML when you redesign the site and avoid adding tags where you don't actually need them."

So if you can change the design but at the same time keep things in the HTML looking similar, that is your best bet. Change a lot without changing a lot - if that makes sense.

Forum discussion at LinkedIn.

 

Popular Categories

The Pulse of the search community

Search Video Recaps

 
Video Details More Videos Subscribe to Videos

Most Recent Articles

Google Updates

Google Search Ranking Volatility Remains Heated Through The Weekend

Feb 15, 2026 - 9:45 am
Search Forum Recap

Daily Search Forum Recap: February 13, 2026

Feb 13, 2026 - 10:00 am
Search Video Recaps

Search News Buzz Video Recap: Google Volatility, Bing AI Performance Reports, New AI Mode Retail Ads, UCP Checkout & ChatGPT Ads Go Live

Feb 13, 2026 - 8:01 am
Google Search Engine Optimization

Where Are Those New Google Search Console Features?

Feb 13, 2026 - 7:51 am
Google Ads

Google Ads Product Eligibility View Across Campaigns

Feb 13, 2026 - 7:41 am
Google Search Engine Optimization

Google Still Recommends You Focus On Visible Anchor Text For Links

Feb 13, 2026 - 7:31 am
 
Previous Story: Google: Don't Use Relative Paths In Your rel-canonical