Free GEO Audit Tool — AI Visibility Check

What Is the GEO Audit Tool?

GEO — generative engine optimisation — is the work of being findable and citable by AI assistants, not just ranked by search engines. Those systems read the web differently: they parse structure, lean on pages they can extract clean answers from, and can only cite what their crawlers are allowed to fetch in the first place.

This audit checks the mechanical layer honestly. Access: the robots.txt decision for each major AI crawler, read from your live file. Structure: schema types present, and semantic landmarks (header, nav, main, article, footer) that help a parser find the content. And llms.txt — reported as what it is: a community proposal some AI tools read, not an official standard; Google has said it does not use the file. Nothing here guarantees a citation; it tells you whether the door is open and the page is parseable. Test the file itself with the Robots.txt Tester.

How to Use It

1. Enter the page URL (the site root works best for access checks).
2. Click Run GEO Audit.
3. Read the AI crawler table first — blocked bots cannot cite you.
4. Then check llms.txt, schema types and the semantic structure score.

What You Get

What AI answer systems actually read on a page

AI answer systems do not browse your site the way a person does. Their crawlers fetch pages as raw documents, extract the text and structure, and decide what can be quoted, summarised or cited in an answer. Clean semantic structure helps that process: headings that describe their sections, landmarks such as header, nav, main and article that label each region, and machine-readable schema that states plainly what the page is about. When that scaffolding is missing, the content may still be good, but it is harder for a machine to parse with confidence.

This audit gathers the evidence in one pass. It fetches your page, your robots.txt and your llms.txt file, then reports which AI crawlers are allowed, blocked or simply not mentioned, whether an llms.txt exists, which JSON-LD schema types the page carries, and whether the main semantic landmarks are present. The results roll up into a simple readiness score. One honesty note: llms.txt is a community proposal, not an official standard, and Google has stated that it does not use the file, so treat it as an emerging convention rather than a requirement.

The AI-crawler decision: what blocking or allowing really trades off

The robots.txt results deserve a careful read, because allowing or blocking an AI crawler is a genuine trade-off, not a technicality. Blocking bots such as GPTBot keeps your content out of the training and retrieval pipelines behind AI answers, which some publishers prefer. The cost is visibility: the same systems cannot cite or surface pages they are not allowed to fetch. Allowing them does the opposite, trading wider exposure in AI answers for less control over how your material is absorbed and reused.

There is no universally right setting, and this tool will not pretend otherwise. What matters is that the setting is deliberate and consistent. Many sites inherit robots.txt rules from a plugin or a template and block crawlers they never meant to block, or allow everything without ever deciding. Use the per-bot breakdown — GPTBot, ChatGPT-User, ClaudeBot, PerplexityBot, Google-Extended, CCBot and Applebot-Extended — to see exactly where you stand today, then set each rule on purpose and record why, so a future edit does not quietly undo the decision.

Privacy: to run this check, our server fetches the public URL you enter — the same request any browser or crawler makes. The URL and its results are not stored; close the tab and they are gone.