Before our own site's redesign went live, we checked every one of its 234 pages the way Google and an AI assistant would read them. We found 7 faults. Not one of them was caused by the redesign.
That is the part most redesign plans miss. The faults had been sitting on the old site, quietly costing rankings and mentions, and nobody could see them because every page looked fine. A redesign is the moment those problems either get carried into the new site or get caught on the way.
So what does a redesign actually put at risk? Far more than the design review ever looks at. Your page addresses, the words Google has already ranked, the hidden tags search engines read, and the links that connect one page to the next can all change in a single launch, and the visibility you built over years drains away without a single error message.
The good news is that none of this is bad luck. Every loss a redesign causes has a cause you can check for before launch, and a redesign done in the right order does more than protect what you have. It fixes what was already broken.
The difference between a redesign that holds its traffic and one that loses it comes down to a question almost nobody asks in the design review: what do the bots see?
What Your Designer Checks Versus What Google and ChatGPT Check
Your design review is a visual review. You look at the new layout on a laptop and a phone, you check the colors and fonts, you click through the menu, and you sign off when it looks and feels right. That is the right review for the people who will visit the site.
Google does not see any of that. Neither do ChatGPT, Claude, or Perplexity. What they read is the page underneath the design: the address it lives at, the words in its code, its title and description, the tags that say which version is the real one, and the links pointing in and out.
Who checks that layer before launch? In most redesigns, nobody. The designer's job ends at the screen, the developer's job ends when the pages load, and the search review happens after launch, usually in the week someone notices the phone ringing less.
The look. Colors, fonts, photography, and whether the site finally feels like the brand.
The flow. Menus, buttons, and whether a visitor can find the contact page in 2 clicks.
The feel. Animations, transitions, and how quickly the pages seem to load.
The sign-off. A person scrolls it on a laptop and a phone, likes what they see, and says yes.
The words. Whether the text that ranked, and the lines AI assistants quoted, are still on the page.
The tags. Titles, descriptions, the canonical tag that says which address is the real one, and the tag that hides a page from search.
The markup. Structured data that tells search engines and AI assistants what each page is about.
The links. Whether every page can still be reached from somewhere else on the site.
Both reviews matter, and they are different jobs. A site can pass the design review with top marks and fail the second one badly, because the second one checks things a person scrolling the page will never notice.
Before you approve the new design, ask which of your current pages bring in traffic and leads today, and whether anyone has confirmed that those exact pages, their words, and their addresses survive the launch. If nobody can answer, the visibility review has not happened yet.
What a Quiet Traffic Loss Looks Like From Inside Your Business
A redesign that loses visibility rarely breaks anything you can see. The new site loads, the pages look great, and the launch gets a round of compliments. The damage shows up somewhere else, and usually later, which is why it so often gets blamed on the market instead of the launch.
These are the signs that tend to surface first.
How do you know it is the redesign and not a slow month? Compare the pages that changed with the pages that did not. If traffic fell on the pages whose address, words, or template changed and held on the rest, the cause is the launch, and the fix is specific rather than a guess.
That comparison only works if you captured a baseline before launch. Without the before picture, every drop turns into an argument about seasonality, and the pages that could have been rescued quietly lose their place while the debate goes on.
Losing Google Rankings and Losing AI Mentions Are 2 Different Problems
Most redesign advice treats search as a single thing. It is really 2 things, and they recover in different ways.
Google has a documented path back. Its own guidance on site moves says plainly that "301 and other permanent redirects don't cause a loss in PageRank," PageRank being Google's name for the ranking value a page has built up. A permanent redirect, the kind developers call a 301, tells Google a page has moved for good and where it went.
The same guidance also warns that "you may experience ranking fluctuations while Google recrawls and reindexes your site." So you redirect every old address to its closest new one, you expect a dip, and the value follows.
AI assistants work differently. ChatGPT, Claude, and Perplexity mention you based on what they can read and quote from your pages when they look, and a redirect only protects the address. It does nothing for the words, the structure, or whether the assistant's bot can see the content at all.
That last point catches a lot of redesigns. Vercel's 2024 analysis of AI bot traffic found that "none of the major AI crawlers currently render JavaScript," naming the bots from OpenAI, Anthropic, Meta, ByteDance, and Perplexity. If your new site builds its content in the browser with JavaScript, the code that assembles parts of a page after it loads, those bots may be reading an almost empty page.
The same study named an exception worth knowing. Google's Gemini reads pages through Google's own bots, which do run JavaScript, so a page can look perfect to Google and still be close to invisible to ChatGPT.
We ran into this on our own site. Our FAQ markup used to be added to each page by JavaScript after it loaded, so AI bots never saw it, and we moved it into the page the server sends.
Why does that matter for your redesign? New designs lean heavily on tabs, sliders, accordions, and sections that load as you scroll. Every one of those can hide words an AI assistant used to quote, even while Google still sees them without trouble.
A redirect moves the address. It does not move the words that earned the ranking, the markup that told search engines what the page was about, or the plain text an AI assistant quoted. Treat redirects as the floor of a safe relaunch, not the whole of it.
If you want the fuller picture of how assistants decide whom to name, read how to get mentioned by ChatGPT, Claude, and Perplexity. The short version for a redesign is simple: keep the words that were being quoted, and keep them readable without JavaScript.
The 4 Things Every Redesign Can Break
Every loss a redesign causes lands in 1 of 4 places. Knowing which is which turns a vague worry into something you can actually audit, page by page, before launch.
Which layer breaks most often? In our experience, signals, because nobody can see them. When we audited our own 234 pages before launch, most of the 7 faults sat in that layer.
On 7 of our 9 author pages, the FAQ markup contained a stray line break that made it invalid, so Google had been discarding it without a single warning showing on the page. One section's canonical tag pointed at an address that did not exist. And an old copy of the homepage was still open to search engines, competing with the real one.
None of those showed up in any design review, because none of them change how a page looks. All of them change how a page is read. That is the whole case for auditing a test copy of your new site the way a bot reads it, before a single visitor arrives.
The content layer is the one teams argue about most. What if your new design genuinely needs less text? Then move the words rather than delete them. A long answer can sit lower on the page, below a short summary, and still be there for Google and every AI assistant that reads it.
Pathways deserve a second look too. If your new menu is leaner than the old one, check which pages lost their only link. Links pass value between your pages a little differently for AI bots than for Google, which is covered in how internal linking works differently for AI crawlers.
Three Ways Teams Relaunch a Site. Two of Them Lose Traffic.
Put 10 redesign projects side by side and they fall into 3 patterns. The difference between them is not the design quality or the tools used. It is when the visibility work happens.
Content: unchecked.
Signals: unchecked.
AI mentions: unwatched.
Content: unchecked.
Signals: partly checked.
AI mentions: unwatched.
Content: protected.
Signals: audited.
AI mentions: tracked.
Why do most teams end up in A or B? Because the visibility work sits between 2 jobs. The designer owns how the site looks, the developer owns whether it works, and search falls into the gap between them, which is exactly where a proper relaunch plan has to put someone in charge.
Option C is not a bigger project. It is the same project done in a different order, with the checks moved to the front where they are quick, instead of the back where every fix turns into a recovery.
It also changes the conversation after launch. With a baseline in hand, a dip is something you can read, page by page, rather than something you argue about. You know which pages changed, what they ranked for before, and whether they are coming back.
What a Careful Redesign Still Will Not Protect
Doing everything right still leaves a few things outside your control. Knowing them up front keeps expectations honest, and it stops a normal dip from turning into a panic.
Is there any way to speed up the recovery? For Google, yes. Submit the updated sitemap in Google Search Console and ask Google to re-read your most important pages. For AI assistants, the best lever is making sure the pages they quoted are complete and readable the moment they return.
None of these limits are reasons to avoid a redesign. A site that looks dated costs you trust with every visitor, and a careful relaunch lets you fix that without handing back the search visibility you already earned.
How to Relaunch in the Right Order
The order matters more than any single step. Every item below is standard practice on its own. What protects your traffic is doing them before launch instead of after it.
Inside those 3 stages sit 5 steps. Here is what each one involves, in the order that protects the most.
Want a quick way to take that baseline? Run your site through the free AI search readiness checker before you touch anything, and again after launch. It scores the site on classic search, AI search, and AI answers (SEO, GEO, and AEO), so you can see whether the new site kept what the old one had.
Which step do teams skip most? Step 3. It feels redundant once the design is approved, and it is the one that catches the faults nobody can see.
If you are working with a design agency, ask them who owns each of these 5 steps before the project starts. A clear name next to each one is the best sign the relaunch will protect what you have. A shrug is the best sign it will not.
Frequently Asked Questions
If the redesign is also a move off WordPress, read why WordPress will quietly die for small business, and what comes next, which walks through how a clean move to a lighter setup works.
To measure whether AI assistants are still sending you visitors after launch, see how to track traffic from ChatGPT, Claude, and Perplexity.
And for the hidden markup that shapes how your pages show up in AI answers, read which structured data helps in AI search, and which does not.
A redesign is the one moment when years of search visibility can disappear in a single afternoon. It is also the best chance you will get to fix what has been quietly broken for a long time. The sites that come out ahead treat what Google and AI assistants read as part of the build, not as something to check once the traffic falls.
At Entexis, we redesign and rebuild websites with search visibility built into the work, not checked after launch. We map every old address, audit the test copy the way Google and AI assistants read it, and keep watching the pages that changed once the new site is live. When a full rebuild is not the right move yet, we also consult on what to fix on the site you already have. If you are planning a redesign and cannot risk the leads your current site brings in, let us run you through a no-pressure discovery session. Start the conversation with Entexis.
