Free GEO Readiness Score: What It Checks, What It Misses, and How to Fix Low Answers

99Visibility Research · Updated October 21, 2026 · 5 min read

Short answer

A free GEO readiness score rates the practices you control that decide whether AI engines can reach and quote your site. These include crawler permissions in robots.txt, firewall access, server-rendered content, index and snippet eligibility, and clear facts on fetchable pages. It cannot tell you whether ChatGPT, Perplexity or Google will cite you. Read a high score as no known blocks, and each low answer as a specific fix.

Key takeaways

A readiness score grades access gates you control, not whether any engine will cite you.
The checks with real evidence behind them are subtractive: per-bot robots.txt rules, firewall reachability, server-side rendering, index eligibility and snippet controls.
A robots.txt that allows a crawler means nothing if your CDN or firewall returns a 403 to it.
Points for schema, llms.txt, E-E-A-T scores or AI-friendly writing grade things the evidence does not support.
Fix access failures first, because every later step depends on the crawler reaching the page.

What a GEO readiness score measures

A GEO readiness score grades your site against the things you control. In practice that means access: can each AI crawler fetch your pages, read the content without running JavaScript, and show it in an answer.

The evidence supports this focus. A July 2026 critical survey of 45 GEO studies (arXiv:2607.14035) found that no reviewed technique shows a stable, longitudinal, cross-platform causal effect on organic discoverability. What holds up are blocks you can remove: per-bot robots.txt permission, network reachability, server-side rendering, index eligibility and snippet controls.

So a useful readiness check is a list of gates. Each one is pass or fail, and each failure has a known fix. A check that awards points for schema, llms.txt, an E-E-A-T score or AI-friendly writing is grading things the evidence does not back.

Answer the readiness questions by hand

Replace example.com with your domain and pick one money page, such as pricing.

Does robots.txt allow the search bots? Run curl -s https://example.com/robots.txt. Find the rules for OAI-SearchBot, PerplexityBot, Claude-SearchBot, Meta-WebIndexer, Googlebot and bingbot. OpenAI's crawler page says each setting is independent: GPTBot governs training, and OAI-SearchBot governs ChatGPT search. A blanket AI block often removes search eligibility without anyone noticing. The free robots.txt checker for AI crawlers parses this per bot.
Does your firewall or CDN let them through? Request the page with the full user-agent string from each vendor's crawler page: curl -s -o /dev/null -w "%{http_code}" -A "<full UA string>" https://example.com/pricing. A 403, 429 or CAPTCHA page is a fail. On Cloudflare, open the AI crawler settings. From 15 September 2026, Cloudflare blocks Training and Agent crawlers by default on ad-displaying pages for new domains and existing free-tier customers. The free AI crawler checker runs this test for each bot.
Is the key content in the raw HTML? Run curl -s https://example.com/pricing | grep -i "per month", swapping in a phrase from your page. Vercel found ChatGPT and Claude crawlers fetch JavaScript files (11.50% and 23.84% of requests) but don't execute them. Googlebot does render.
Are you suppressing yourself? Search the page source for noindex, nosnippet, max-snippet:0 and data-nosnippet. Bing says content marked data-nosnippet is excluded from snippets and AI summaries.
Are you eligible on Google and present in Bing? Google says a page must be indexed and eligible to show with a snippet to appear in AI Overviews or AI Mode, with no additional technical requirements. Check URL Inspection in Search Console, and check the generative AI inclusion control if your property has it. Check Bing Webmaster Tools separately.
Are your key facts stated plainly and consistently? Your price, a key number and a one-line definition should appear in text on a fetchable page, and match across pricing, about and footer.
Are you named on the sites engines cite for your topic? The evidence shows an association here, not a promised effect.

How to read your answers and turn them into fixes

Order matters. Questions 1 to 4 are gates: if any fails, nothing after it reaches the engine. Fix them before anything else.

Low answer	What it means	The fix
Search bot disallowed	That engine's search can't use the page	Allow the retrieval bot, keep training bots as you choose
403 or challenge to a crawler	Silent block despite robots.txt	Allow the verified bot in your WAF or CDN
Facts missing from raw HTML	Non-Google crawlers see an empty page	Server-render or prerender that content
Stray nosnippet or noindex	Content kept out of AI answers	Remove it from the template
Not indexed in Google or Bing	No supporting link possible on that engine	Fix the indexing issue the tool reports
Facts vague or contradictory	Engines have no clean sentence to quote	State one fact one way, on every page

Most of these fixes are engineering tickets measured in hours. Getting cited is a different timeline, covered in how long AI visibility work takes.

What a readiness score cannot tell you

A perfect readiness score is not a citation. Retrieval is per-query and discretionary on every platform, as of October 2026. ChatGPT decides when to search, and Google AI Overviews often don't trigger. Which retrieved page gets cited is decided inside the model.

The score also misses answers given with search off. Those come from training data frozen at a cutoff (16 February 2026 for OpenAI's GPT-5.6 family), so nothing you fix this quarter reaches them. The search on vs off test shows the gap.

Volume is not readiness either. In Otterly's 2,000 AI blogs experiment, Google deindexed both mass-published sites, and its AI surfaces stopped citing them.

Finally, readiness is not visibility. An AI visibility score measures what engines actually said, which is a separate question.

The free quiz that does it faster

If you'd rather not run curl commands, 99Visibility's GEO Readiness Quiz walks through the same kind of questions and scores your answers. Use the result as a fix list, starting with any access gate that fails.

To see whether engines actually name you, run the free checker on this site. It tests up to three buyer questions as a snapshot, which pairs well with a readiness score: one tells you what's blocked, the other tells you what the answers say.

Frequently asked questions

Does adding schema markup raise my GEO readiness?

Not in any way the evidence supports. Google says structured data isn't required for generative AI search. Ahrefs tracked 1,885 pages that added schema against matched controls and found no major uplift, with AI Overview citations falling 4.6%. That study only covered pages already cited heavily, so effects on new pages are untested. Existing markup does no harm, so there's no reason to remove it either.

Should I allow GPTBot so ChatGPT can find me?

GPTBot only governs whether your content may be used to train OpenAI's models. ChatGPT search uses OAI-SearchBot, and OpenAI says each setting is independent of the others. You can block GPTBot and still allow OAI-SearchBot. Decide on training separately, and make sure the search bot is allowed in both robots.txt and your firewall.

Do I need an llms.txt file to be AI-ready?

No. Google says Search ignores llms.txt and that creating one will neither help nor harm your visibility in Google Search. No other major engine documents reading it. Google also says it's fine to keep one for other services that use it, so it's harmless, but it shouldn't count toward a readiness score.

How often should I re-check my readiness?

Re-check after any deploy that touches rendering or templates, any robots.txt edit, and any CDN or firewall change. Access can also change without you editing anything: Cloudflare's default AI crawler blocking from 15 September 2026 applied to existing free-tier customers. A quarterly check catches drift between those events.

Sources

This page is AI-assisted. It was written from a verified evidence base and checked against our editorial policy. Engine behaviour changes often; facts are as of October 21, 2026.