Title: How to Redesign Your Website Without Losing Your Google Rankings or AI Search Mentions Author: Entexis Team Category: SEO, GEO & AEO Read time: 12 min URL: https://entexis.in/website-redesign-without-losing-rankings-or-ai-mentions Published: 2026-09-22 --- 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. Pages checked the way Google and AI assistants read them 7Hidden faults found, none caused by the redesign itself 7 of 9Author pages whose FAQ markup Google was silently discarding 1 yearMinimum time Google suggests keeping old redirects in place 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. *[Diagram: What the Design Review Signs Off vs What Search Engines Actually Read]* What Google and AI Assistants Read The address. Whether each page still lives where Google and other sites expect to find it. 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, Before Launch The left column is the review everyone remembers. The right column is the one that decides whether the new site keeps the traffic the old one earned. Run both on the test copy of the new site, before a single visitor sees it. 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. > **The Question to Add Before Sign-Off:** 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. Pages That Ranked Now Show as Not FoundGoogle Search Console, the free tool Google gives site owners, starts listing old addresses it can no longer find. Each one is a page that used to rank and now sends Google, and every site that linked to it, into a dead end. An AI Assistant Stops Naming YouYou ask ChatGPT or Perplexity a question it used to answer with your page, and a competitor comes back instead. The assistant is not punishing you. It simply cannot find the words it used to quote. Your Best Old Pages Now Land on the HomepageA detailed service page that ranked for a specific search now redirects to the homepage. The visitor wanted an answer and got a front door instead. Google reads that the same way the visitor does, and the ranking fades. 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. > **What a Redirect Cannot Carry:** 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](/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. *[Diagram: What a Redesign Can Break, From the Address Down to the Links]* Layer 2, Content The Words, Headings, and Answers That Earned the Ranking Redesigns love less text. Long service pages get trimmed into short cards, FAQs get cut for a cleaner look, and 3 detailed pages get merged into 1 summary. Those words were what Google ranked and what AI assistants quoted. Cut them and a page can keep its address, its redirect, and a beautiful design, and still lose the searches it used to win every day. Layer 3, Signals The Hidden Tags Only Search Engines Read Page titles, descriptions, the canonical tag, the tag that keeps a page out of search results, structured data markup, and the sitemap, which is the list of pages you hand to Google. None of these show on screen, so none of them get checked in a design review. This is the layer where a setting from the test copy slips onto the live site and quietly hides it from search. Layer 4, Pathways The Links That Carry Visitors and Bots Between Pages Menus, footer links, breadcrumbs, and the links inside your copy tell Google which pages matter, and they let bots reach every page you have. A new menu that drops a section, or a rewrite that loses its internal links, leaves pages stranded with no way in. Pages nobody links to get treated as pages nobody needs, and they slide down the results. Most Redesigns Only Protect Layer 1 The redirect list is the part every launch plan remembers. The other 3 layers are where most of the quiet losses happen, because they are invisible on the screen and never come up in a design review. 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](/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. *[Diagram: When the Visibility Work Happens Decides What You Keep]* Option B The Checklist Launch A redirect plugin and a launch checklist go in on the day. The addresses are covered, which is real progress. But a checklist cannot see a trimmed service page, a test-site tag left switched on, or content that only appears after JavaScript runs. Addresses: covered. Content: unchecked. Signals: partly checked. AI mentions: unwatched. Option C Visibility Built Into the Build A baseline is taken before anything changes, every old address is mapped, and the test copy is audited across all 4 layers the way Google and AI bots read it. Launch day becomes a confirmation, not a gamble, and the changed pages get watched until they settle. Addresses: mapped. Content: protected. Signals: audited. AI mentions: tracked. The Honest Read Options A and B both feel finished on launch day, which is exactly why they are so common. Only option C treats what search engines read as part of the build, and it is the only one where a redesign can come out ahead of where it started. 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. It Will Not Save a Page You Chose to CutIf you delete a page that ranked, the best move is a redirect to the closest remaining page. That keeps most of the value. The exact search the old page won may still go to a competitor who answers it in full. It Will Not Rescue Rankings You Were Already LosingA redesign protects what you have. If traffic was already sliding because the content was thin or out of date, a new look will not reverse it. That is a content problem, and the relaunch is a good moment to fix it, not a fix on its own. It Will Not Make Thin Content Rank Because It Looks NewerSearch engines and AI assistants reward pages that answer the question well, not pages that look modern. A beautiful page with 80 words loses to a plain page with the full answer. Keep the substance, and let the new design carry it. It Will Not Bring AI Mentions Back on Your ScheduleAI assistants re-read the web on their own schedule, and none of them offer a button to ask for a fresh look. What you control is keeping the quoted words on the page and readable without JavaScript. When the assistants come back, those words need to be there waiting. 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. *[Diagram: From Old Site to New Site Without Losing What Already Ranks]* Before Launch Baseline, address map, and a full audit of the test copy. STAGE 2 Launch Day Redirects, tags, and sitemap go live and get tested together. STAGE 3 After Launch Watch the changed pages, and keep every redirect in place. The Real Order Most of the protection happens in stage 1, before anyone outside sees the site. Stage 2 confirms it. Stage 3 catches what only live traffic can reveal. Inside those 3 stages sit 5 steps. Here is what each one involves, in the order that protects the most. Map Every Old Address to Its Closest New MatchList every page Google knows about, not only the ones in your menu, and pair each with the new page that answers the same question. Nothing goes to the homepage unless the homepage genuinely answers it. Google's own guidance starts every site move with exactly this map. Audit the Test Copy the Way a Bot Reads ItCheck all 4 layers on the test copy: addresses, content, signals, and pathways. Confirm the tag that hides the test site from search is not coming along, the structured data markup is valid, and the important words sit in the page itself, not added later by JavaScript. Launch With Redirects and Signals Live TogetherSwitch the redirects on at the same moment the new site goes live, then test a sample of old addresses by hand. Submit the updated sitemap in Google Search Console so Google finds the new pages quickly, and confirm each key page's canonical tag points at itself. Watch the Pages That Changed, and Keep Redirects OnCheck the pages that changed until their rankings settle, and re-run your AI assistant questions to see whether you are still named. Keep every redirect in place. Google's guidance is to keep them "for as long as possible, generally at least 1 year," because other sites keep sending visitors to your old addresses long after launch. Want a quick way to take that baseline? [Run your site through the free AI search readiness checker](https://entexis.tech/) 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 Will a website redesign always hurt my SEO?No. A redesign hurts search when it changes page addresses, content, or hidden tags without a plan. Done in the right order, rankings usually dip briefly while Google re-reads the site and then settle where they were. A redesign that also fixes old faults can come out ahead. The risk comes from skipping the checks, not from the redesign itself. How long should I keep redirects from my old pages?Google's own guidance on site moves says to keep redirects "for as long as possible, generally at least 1 year." That gives Google time to move every signal to the new addresses, and it covers the links other sites still point at your old pages. In practice, there is rarely a good reason to remove a working redirect at all. Should I redirect deleted pages to my homepage?Usually not. Redirect each removed page to the page that answers the same question, such as a close service page or a newer version of the same topic. Sending everything to the homepage looks tidy, but the visitor and Google both land somewhere that does not match what they were looking for, and the relevance the old page earned fades away. Can a redesign change how ChatGPT and other AI assistants mention my business?Yes, and redirects alone do not protect it. AI assistants mention you based on the words they can read on your pages. If the redesign trims the text they quoted, moves it behind tabs, or builds it with JavaScript that their bots do not run, they may stop naming you. Keep the quoted words, and make sure they sit in the page itself. Is it safer to keep my existing page addresses?Yes, whenever you can. Keeping an address the same removes the need for a redirect, and it keeps every link other sites point at that page working exactly as before. Change addresses only when the old structure is genuinely confusing, and when you do, map each old address to its closest new match rather than starting fresh. Can Entexis redesign our site without losing what already ranks?Yes. We redesign and rebuild sites with the visibility work built in: a baseline before anything changes, a full map of old addresses, an audit of the test copy across addresses, content, signals, and pathways, and close watching of the changed pages after launch. We work on WordPress, Shopify, and custom-built sites. And we are honest when the right move is fixing your current site instead of redesigning it. If the redesign is also a move off WordPress, read [why WordPress will quietly die for small business, and what comes next](/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](/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](/schema-for-ai-search-what-helps-and-what-doesnt). 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. > **Redesigning a Site That Already Brings In Leads?:** 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.