AI Search Visibility & GEO Guides by Platform
Learn how to configure raw-HTML readability, /llms.txt, and crawler directives across your tech stack.
Free diagnostic No account needed Up to 40 pages, fetched as GPTBot would
Integration guides
Step-by-step walkthroughs with code you can paste: what goes wrong on each platform, and the files that fix it.
Next.js
App Router pages that render their content only after mount, plus llms.txt and robots rules written as code.
COMMON PITFALLS
- Content fetched in
useEffectnever reaches the HTML next/dynamicwithssr: falsedrops whole sections- A default robots.ts names no AI crawler at all
- Content fetched in
Shopify
A store you cannot put files in the root of, a robots file that names no AI bot, and apps that stack schema.
COMMON PITFALLS
- No arbitrary files at the domain root
- Default robots rules name no AI crawler
- Theme and apps each emit their own Product schema
WordPress
Server-rendered by default. The trouble is stacked plugins, slow uncached pages and a missing llms.txt.
COMMON PITFALLS
- Two plugins, two conflicting Article entities
- Slow first byte on uncached pages
- No /llms.txt: the request lands on the theme’s 404
Every other platform
Most AI crawlers fetch raw HTML and never run JavaScript, so how much of your site they can see depends on the platform and how you configured it. Each baseline below counts raw-HTML readability only (up to 35); schema, llms.txt and AI-crawler rules depend on your setup and start at zero. The second number is the most the Fix Kit can lift it to.
v2 scoring
Astro
Astro is about as good as it gets for AI readability: zero JavaScript by default means everything ships as HTML.
Out of the box35up to 100 with the Fix KitStatic HTMLGatsby
Gatsby builds static HTML per route, so content is readable — the risk is components that only render after hydration.
Out of the box35up to 100 with the Fix KitStatic HTMLWebflow
Webflow publishes static HTML with the content baked in, which makes it genuinely good for AI crawlers — the weak spot is CMS collection pages with thin content.
Out of the box35up to 100 with the Fix KitStatic HTMLFramer
Framer publishes static HTML with text included, so it reads reasonably well — though heavy use of effects and CMS components thins out the raw content.
Out of the box25up to 90 with the Fix KitStatic HTMLSquarespace
Squarespace serves most page content in HTML but loads galleries, summary blocks and some newer sections client-side, so parts of the page go missing for AI crawlers.
Out of the box15up to 80 with the Fix KitHybridVue & Nuxt
Nuxt with SSR on is readable; a plain Vue SPA or Nuxt with ssr:false is not.
Out of the box15up to 80 with the Fix KitHybridWix
Wix has improved a great deal but still ships a heavily script-driven page, so raw-HTML content is thinner than what a visitor sees.
Out of the box15up to 80 with the Fix KitHybridAngular
A default Angular application renders entirely in the browser, so AI crawlers receive an empty <app-root> and nothing else.
Out of the box0up to 65 with the Fix KitClient-renderedReact (create-react-app / Vite SPA)
A plain React SPA is close to invisible to AI crawlers: the served HTML is a near-empty div and everything else arrives via JavaScript they do not run.
Out of the box0up to 65 with the Fix KitClient-rendered
Baselines are not your score
A Next.js site that renders every page's content after mount scores worse than a plain WordPress blog. The platform sets the ceiling; your configuration decides where under it you land. A client-rendered app tops out at 65 however good its schema and llms.txt are, because raw-HTML readability is the one pillar files cannot fix.
Scan your actual siteFurther reading
- How to Make React Apps Crawlable for AI Search: SSR, Prerendering and Dynamic Rendering
Google can render React; ChatGPT, Claude and Perplexity crawlers can't. Code for Vite SSR, Next.js and Astro prerendering, dynamic rendering, and a curl check.
- What GPTBot Actually Sees When Your Site Relies on Client-Side JavaScript
AI crawlers like GPTBot and OAI-SearchBot fetch raw HTML without executing client-side JS. Here is what they actually extract from SPAs.
- Why AI Search Engines Can’t Read Client-Side Rendered (CSR) Sites
Most AI crawlers fetch raw HTML and never run your JavaScript. Here's what they actually see on a client-rendered site, how to test it, and how to fix it.
- What is Generative Engine Optimization (GEO)? The Complete 2026 Guide
How ChatGPT Search, Perplexity and Claude find, read and cite pages, why that differs from Googlebot, and what the research says actually improves AI visibility.