GEO Readiness Scanner: can AI search engines read your site?
Before ChatGPT, Claude, or Perplexity can recommend you, their crawlers have to reach your pages, read your content in raw HTML, and understand your schema. This scanner runs the same checks we run at the start of every AI and GEO engagement.
What the scanner checks, and why each one matters
Crawl access comes first because nothing else matters behind a locked door: robots.txt rules for the AI bots (OAI-SearchBot, ClaudeBot, PerplexityBot, and friends) decide whether each engine can see you at all. Most sites inherited these rules from a template and never made the decision deliberately.
The render gap test checks whether your body content exists in raw HTML. AI crawlers mostly never execute JavaScript, so a React or Vue shell that renders content in the browser is invisible to them. This is the single most common failure we find, and it is fixable with JavaScript SEO work like prerendering or server injection.
Response headers are the newest failure mode: a strict Content-Security-Policy can silently kill your analytics and your prerender service. The scanner flags the configuration we watched take a real property dark. The full list lives on our technical SEO checklist.
Frequently asked questions
- Is the GEO Readiness Scanner really free?
- Yes. Run it as often as you like. The full done-for-you version is our AI visibility audit, which adds the prompt panel and the fix roadmap.
- What does GEO readiness mean?
- Generative engine optimization readiness: whether AI search engines (ChatGPT, Claude, Perplexity, Google AI Overviews) can crawl, render, and extract your pages. If they cannot read you, they cannot cite you.
- My site failed the render gap test. How bad is that?
- For AI search, close to fatal: most AI crawlers never execute JavaScript, so content that only exists after rendering does not exist for them. The fix is prerendering or server injection, which is standard work for us.
- Why does the scanner check my response headers?
- Because a strict Content-Security-Policy can silently block your analytics tag and your prerender service while every surface check looks fine. We have watched a client property stay dark in GA4 for weeks from exactly this.
