See your page the way an AI answer engine does
Search is splitting in two. Alongside the classic blue links, people now get answers from ChatGPT, Perplexity, Google AI Overviews and Claude, and those answers cite a handful of sources. Getting cited is the new front page. This free GEO auditor fetches your page the way an AI crawler would and scores how citable it is, then tells you exactly what is holding it back.
The six things it scores
- AI crawler access: are GPTBot, ClaudeBot, PerplexityBot, OAI-SearchBot and Google-Extended allowed in your robots.txt? Block them and you are invisible to those engines.
- Content in the HTML: most AI crawlers do not run JavaScript. If your text is rendered client-side, the crawler sees an empty page. The auditor measures how much real text is in the served HTML.
- Structured data: schema.org markup (Article, FAQPage, HowTo) helps AI systems parse and trust your content.
- Answer-unit structure: an H1, descriptive and question-style subheadings, lists and an FAQ. AI engines quote clear, self-contained answer units.
- Trust signals: author markup and visible dates, which AI systems favour.
- Basics: a well-sized title and meta description, and whether you publish an llms.txt.
What GEO is, and why it is different from SEO
GEO (Generative Engine Optimization), sometimes called AEO (Answer Engine Optimization), is optimising content so AI answer engines can find, understand and cite it. It builds on classic SEO but adds AI-specific factors. Two stand out: you must actually let AI crawlers in, and you must serve your content in the HTML rather than only in JavaScript, because that is what the crawlers can read. On top of that, content that is written as clear answer units, a direct answer first, then supporting detail in short chunks and lists, is far easier for a model to quote accurately.
How to use the report
- Fix the red items first. A blocked crawler or JavaScript-only content are the two issues that can make a page invisible to AI, so they cost the most points.
- Add structured data and structure. Article and FAQPage schema, question-style headings and lists move you from accessible to genuinely quotable.
- Then win on substance. Once the technical blockers are gone, being cited comes down to relevance, quality and authority for the question at hand.
Good to know
The auditor reads the HTML your server returns, which is what most AI crawlers use, so a JavaScript-heavy page can score lower here than it looks in a browser. That gap is the point: it is what the crawler sees. A high score removes the technical blockers to being cited; it is guidance, not a guarantee. Pair it with the llms.txt generator and the AI crawler access checker to complete the picture.