What is GEO and why measure AI visibility?
GEO (Generative Engine Optimization) is the umbrella term for the work that helps your content be understood correctly and cited as a source in AI-powered search experiences such as ChatGPT, Claude, Perplexity or Google AI Overviews. It does not replace classic SEO; it builds on it. A page first has to be crawlable, readable and understandable; only then does it have a chance to be quoted.
The AI visibility checker measures those prerequisites. Nobody can say for certain whether a page will show up in AI answers, but a page that is closed to crawlers, hides its content behind JavaScript or has an unclear structure clearly has lower odds. The test helps you find those obstacles one by one.
What does the test check?
The tool downloads your page, the site's robots.txt and llms.txt files and its sitemap at the same time, groups 30 checks into four areas and scores each one by its weight:
- Crawler access: whether AI search, user-request and search engine crawlers may fetch this page; noindex and nosnippet directives.
- Content and structure: word count in the initial HTML, H1 and subheadings, question-style headings, title, meta description, language attribute and image alt text.
- Structured data: presence and validity of JSON-LD; Organization, WebSite, BreadcrumbList, Article and FAQPage types.
- Technical: HTTP status, HTTPS, redirects, canonical URL, hreflang, viewport, Open Graph, sitemap, llms.txt, response time and HTML size.
How do AI crawlers read your page?
The crawlers behind AI search products mostly read the HTML the server sends first and generally do not run JavaScript. Single-page apps that build their content later in the browser can therefore look empty or incomplete to them. The “Content in the initial HTML” check measures exactly this by counting the visible text such a crawler sees.
On the access side, one distinction matters: crawlers that collect data for model training and search crawlers that cite sources in answers use different names. Blocking training crawlers is a content policy choice and, according to the providers' documentation, does not affect their search crawlers, so the test shows that item as info and leaves it out of the score. Blocking search and user-request crawlers, on the other hand, directly affects visibility.
How should you read the score?
Passed items earn full points, warnings earn half and issues earn none; info items are not counted. Core checks such as crawler access, content in the initial HTML and JSON-LD carry more weight. The score summarizes technical readiness; it is not a guarantee of rankings or citations.
The quickest wins usually come from removing blockers: a robots.txt rule closed by mistake, a forgotten noindex or content that only loads in the browser. After that, strengthen your structured data and heading structure. Our team can implement GEO and technical SEO fixes for you.