Is your site readable to AI?
13 technical checks for crawl access, structured data, authorship, sharing metadata, and optional AI discovery signals. The score is a diagnostic, not a ranking forecast.
Takes about 5 seconds. We don't store anything.
How should you read the score? Google does not use llms.txt, FAQ rich results have been retired, and there is no ideal word count. Use the 13 technical checks as a prioritized diagnostic. Read the postScanning site for AI
your site
Did you know?
AI engines like ChatGPT and Perplexity are answering more questions without sending users to your site.
What this audit checks
Thirteen checks, 66 points, run against the live HTML of the URL you enter. Every weight below is the one the scorer actually uses. The audit reads what a crawler can read: it does not judge whether the writing is any good, and it is a technical diagnostic rather than a ranking or citation forecast.
| Check | Points | Severity |
|---|---|---|
| Optional llms.txt discovery file | 2 | nice |
| AI search and user-retrieval crawlers in robots.txt | 8 | important |
| JSON-LD schema present | 5 | critical |
| FAQPage parity when visible Q&A exists | 2 | nice |
| Organization or LocalBusiness schema depth | 10 | important |
| Article or BlogPosting completeness | 8 | important |
| Named authorship and accountability | 8 | important |
| Single H1 on the page | 4 | important |
| Meta description, 120 to 160 characters | 5 | nice |
| Open Graph title, description, and image | 3 | nice |
| sitemap.xml at root with URLs and lastmod | 4 | important |
| Crawlable content available | 3 | nice |
| BreadcrumbList schema | 4 | important |
Two penalties apply on top of the 66 points. FAQPage schema with no visible questions and answers on the page is scored as schema spam, and a page set to noindex is flagged outright. Both describe a page telling engines something the page does not support.
How the score is banded
- Strong85% and aboveThe technical foundation is in place. Relevance, originality, authority, and demand still decide visibility.
- Decent65% to 84%Most technical signals are present. Prioritize the gaps that match this page and its readers.
- Behind40% to 64%Several discovery signals need work before visibility work compounds.
- LimitedBelow 40%Core crawlability and page-context signals need review first.
Questions about the score
What does the AEO audit check?
Thirteen technical checks worth 66 points in total. They cover crawler access in robots.txt, JSON-LD schema presence and depth, Organization or LocalBusiness detail, Article or BlogPosting completeness, named authorship, a single H1, meta description length, Open Graph tags, sitemap quality, crawlable content, BreadcrumbList, FAQPage parity, and the optional llms.txt discovery file. Two penalties also apply: FAQ schema with no visible questions and answers, and a page set to noindex.
Does a high score mean the page will rank or get cited?
No. The score measures whether a page is technically legible to search and answer engines. It says nothing about relevance, originality, authority, or demand, and those decide visibility. Treat a strong score as the floor being in place, not as a forecast.
Do I need an llms.txt file to score well?
No. llms.txt is worth 2 points of 66 and is marked optional for a reason: no major answer engine has confirmed it is required for retrieval. Crawler access, schema depth, and named authorship carry far more weight and are worth fixing first.
The same rubric runs on our own pages. For the reasoning behind each check, read how the AEO audit works, or start with answer engine optimization explained.