Content accessibility
Explore checks for server-rendered content, structured data and Markdown alternatives that help AI agents read and understand your site.
Once an agent has found a page, these checks look at how cheaply and reliably
it can read it: whether the content is in the HTML the server sends, whether a
Markdown version is on offer, whether /llms.txt points somewhere useful, and
whether structured data says what the page and its publisher are.
Content accessibility carries a weight of 3 in the overall score, three times that of Discoverability or Agent experience. It is one of the two categories where a site only scores by doing something deliberately for agents.
Checks in this category
- Content without JavaScript
Most agents read the HTML your server sends and do not run JavaScript. Whatever is not in that HTML does not exist to them. Top 100 adoption 94% - Markdown content negotiation
Serving a Markdown version when an agent sends Accept: text/markdown makes your content cheaper and cleaner for it to read. Top 100 adoption 2% - Markdown negotiation caching (Vary)
Without Vary: Accept, a cache may return the wrong response, sending browsers Markdown instead of HTML. Top 100 adoption 2% - llms.txt links resolve
An llms.txt should not contain links that return a 404. Top 100 adoption 15% - JSON-LD entity linking (sameAs)
sameAs ties your entity to ones an agent already knows, such as Wikipedia, Crunchbase, and your own profiles. Top 100 adoption 36% - Organization schema completeness
The Organization node is what an agent reads to tell who publishes a site. Top 100 adoption 31% - Schema type breadth
Generic types tell an agent less than specific ones such as articles, products, and FAQs. Top 100 adoption 36% - Structured data (JSON-LD)
Schema.org JSON-LD gives agents typed data about your page that is easy to process. Top 100 adoption 37% - Emerging checkMarkdown URL fallback (.md)
A .md twin of each page lets an agent fetch Markdown by convention when the server does not negotiate. Top 100 adoption 3% - Emerging checkMarkdown alternate link
A rel="alternate" link pointing to text/markdown tells an agent a Markdown copy exists, so it does not have to guess. Top 100 adoption 2% - Emerging checkllms.txt present
An /llms.txt file gives agents a hand-picked Markdown map of your most important content. Top 100 adoption 28% - Emerging checkModular llms.txt
Per-section llms.txt files let an agent pull more granular context. Top 100 adoption 2% - Emerging checkSpeakable content markup
speakable marks the sections worth reading aloud, which is what a voice agent reaches for first. Top 100 adoption 0%