You're planning a website redesign. New design, new site architecture, maybe a CMS change. On the SEO side, you've planned your 301 redirects. But have you thought about your AI visibility?
A poorly prepared redesign can make your site disappear from ChatGPT, Perplexity, and Gemini responses for weeks, even months. And unlike traditional SEO where rankings recover gradually, AI visibility can collapse abruptly if the trust signals AI engines had built up on your old site disappear.
Why a redesign is risky for AI visibility
AI engines don't work like Google
Google recrawls your site regularly and updates its index. If you redesign with proper redirects, Google follows them and transfers SEO equity within weeks.
AI engines work differently:
- LLMs have a frozen memory. Base models (GPT-4, Claude, Gemini) were trained on data at a specific date. If your old site was in the training data, your new site isn't there yet.
- RAG recrawls, but more slowly. RAG systems (Retrieval-Augmented Generation) use a search engine (Bing for ChatGPT, Google for Gemini) to enrich responses with fresh data. If your URLs change, RAG must rediscover your content.
- JSON-LD schemas are trust anchors. If your old site had Organization, Person, FAQPage schemas, and the new site doesn't (or has them differently), AI engines lose the trust signals they had accumulated.
What can break during a redesign
- URLs change — existing citations in AI responses point to 404s
- JSON-LD schemas disappear — loss of E-E-A-T signals and data structure
- Content is reorganized — FAQs, guides, and articles that AI engines cited are moved or merged
- robots.txt changes — AI bots may get blocked without your knowledge
- Author pages disappear — loss of E-E-A-T authority tied to authors
- Sitemap isn't updated — AI crawlers don't discover the new URLs
Before the redesign: the baseline audit
Step 1: run a GEO audit on the old site
Before touching anything, measure your current AI visibility. This is your baseline — the reference score you'll compare the new site against after migration.
Metrics to capture:
- Overall GEO score and score per criterion (7 criteria)
- AI citation test: on which queries is your site cited by ChatGPT, Perplexity, Gemini?
- JSON-LD schema inventory: which schema types are present and on which pages?
- Most-cited pages list: identify your pages that appear in AI responses (often FAQs, guides, detailed product pages)
- robots.txt configuration: which AI bots currently have access?
Run your GEO audit before the redesign — your baseline score
Analyze my site for free →Step 2: map critical AI assets
Identify the pages and elements that contribute most to your AI visibility. These are the elements you must absolutely preserve or reproduce in the new site:
- FAQ pages with FAQPage schema: often the most-cited pages by AI engines
- Author pages with Person schema: carry E-E-A-T authority
- Blog articles with structured data: guides, tutorials, comparisons
- Organization schema: company information, founding date, social networks
- Pages with answer capsules: short paragraphs that directly answer questions
During the redesign: non-negotiable rules
1. Exhaustive 301 redirects
This is rule number 1 in SEO, and it's even more important in GEO. Every old URL that existed must redirect to the corresponding new URL. AI engines may have indexed your old URLs in their retrieval system — a 404 means a lost citation.
Key points:
- Don't redirect everything to the homepage. Each page should redirect to its closest equivalent.
- Test redirects with a crawler (Screaming Frog) before launch
- Keep redirects active for at least 12 months
2. Reproduce all JSON-LD schemas
Before migrating, export the complete list of your JSON-LD schemas. After migration, verify that each schema is present on the equivalent page of the new site.
Priority schemas to verify:
Organization: name, logo, address, social networks, founding datePerson: authors, experts, executivesFAQPage: all pages with questions/answersArticle: withdatePublished,dateModified,authorLocalBusiness: if you have a local presenceHowTo,Review,ItemList: depending on your content
3. Preserve robots.txt and sitemap
Verify that your new robots.txt allows the same AI bots as the old one. This is a frequent oversight: the new CMS generates a default robots.txt that may block GPTBot, ClaudeBot, or PerplexityBot.
The sitemap should be submitted to Google Search Console and Bing Webmaster Tools on launch day. AI crawlers use these sitemaps to discover your new URLs.
4. Preserve citable content
Don't delete pages that AI engines cite, even if they don't fit your new site architecture. If a 20-question FAQ was cited by ChatGPT, don't delete it — move it with a redirect and preserve the content.
If you must merge pages, make sure the citable content (direct answers, data points, lists) is preserved in the merged page.
5. Maintain author pages
Author pages are often sacrificed in redesigns. This is a major mistake for GEO. If your authors had pages with Person schema, bio, credentials, and article lists, recreate them identically on the new site.
After the redesign: verification and monitoring
Launch day checklist
- Test all 301 redirects (zero 404s on old URLs)
- Verify robots.txt (AI bots allowed)
- Submit new sitemap to Google Search Console and Bing
- Validate all JSON-LD schemas with Google Rich Results Test
- Verify author pages are live and indexable
- Test site accessibility with JavaScript disabled (for basic crawlers)
Week 1: first check
- Run a GEO audit on the new site and compare with the baseline score
- Check Google Search Console to verify new pages are indexed
- Manually test 5-10 queries on ChatGPT and Perplexity to see if your site is still cited
Months 1-3: recovery monitoring
AI visibility can take 2-8 weeks to fully recover after a redesign, even with perfect redirects. This is normal: RAG systems need to recrawl your content and rebuild trust signals.
Run a GEO audit every 2 weeks for the first 3 months to track recovery. If the score doesn't bounce back after 4 weeks, check:
- Are all schemas in place?
- Is robots.txt blocking any AI bot?
- Are all redirects working?
- Is the citable content still present and accessible?
Special case: CMS migration
A CMS change (WordPress to Webflow, Shopify to custom, etc.) is the riskiest scenario for AI visibility. The new CMS generates a different HTML structure, different URLs, and often different schemas.
Additional rules for a CMS change:
- Export raw content (text, images, meta) before migration. Don't rely on the new CMS's automatic import.
- Check the HTML structure. Some CMS platforms (Wix, Squarespace) generate HTML wrapped in JavaScript. AI crawlers may not be able to read it.
- Test schemas on the new CMS. Each CMS handles schemas differently. What worked on WordPress (via Yoast) won't be automatically reproduced on Webflow.
- Beware of SPAs. If the new site is a Single Page Application (React, Vue, Angular), content may be invisible to AI crawlers. Use Server-Side Rendering (SSR) or Static Site Generation (SSG).
GEO redesign checklist
Before:
- Baseline GEO audit (score, citations, schemas)
- Inventory of pages cited by AI engines
- Export of all JSON-LD schemas
- Page-by-page 301 redirect plan
During:
- Exhaustive 301 redirects
- All JSON-LD schemas reproduced
- robots.txt with AI bots allowed
- Updated sitemap submitted to search engines
- Author pages preserved
- Citable content preserved
After:
- GEO audit of the new site (comparison with baseline)
- Manual citation test on ChatGPT/Perplexity
- Bi-weekly monitoring for 3 months
Conclusion
A website redesign is an opportunity to improve your AI visibility — as long as you don't lose what you already have. JSON-LD schemas, author pages, structured FAQs, and redirects are the four pillars you must absolutely preserve. Run a GEO audit before the redesign, reproduce trust signals identically, and monitor recovery for 3 months. That's the difference between a redesign that advances your AI visibility and one that makes it disappear.