About LLM Readability
What is LLM readability?
LLM readability is how much of your page an AI assistant can actually read once it has been rendered. Not what a visitor sees, and not what is in your source file, but the text that survives when the page is loaded and the markup is stripped away.
Those three things diverge more than people expect. A page that looks content-rich can render to a few hundred usable words once navigation, cookie notices, related-post widgets and script tags are discounted.
This checker loads your page in a real browser, the same way our audit does, and reports how much readable content is there. A page a system can read thoroughly can be quoted; one it can barely read is passed over for a competitor it can.
Why the rendered version is what counts
Content assembled by JavaScript after load may not exist for anything reading the page. Not every crawler executes scripts, and those that do give up quickly, so a page whose main text arrives late can be read as almost empty.
The reliable fix is to serve meaningful content in the initial HTML through server rendering or static generation. A slow script then degrades an experience rather than erasing a page.
Ratio matters as much as volume. A page where the real text is buried under layers of presentational markup is harder to extract cleanly from, even though it renders perfectly for a person.
This is the least glamorous part of getting cited and among the most decisive, because everything else assumes it. Structure, headings and schema all take for granted that the text is reachable, and it is the part most likely to break quietly in a redesign - the page still looks right to anyone who checks it in a browser.
What tends to be missing
- Text injected by JavaScript after the initial response.
- Content behind tabs, accordions or "read more" toggles that never opens.
- Anything inside an iframe, which is a separate document.
- Copy that only exists inside an image, with no equivalent in text.
- Pages that are mostly interface, where the substance is a paragraph.
What this tool checks
It renders your page in a headless browser and reports the readable content that results, so you are seeing roughly what a machine reading the page would have to work with.
Compare it against what you believe is on the page. A large gap points at content that depends on scripts, or at a page carrying less substance than its layout suggests.
Where to go next
Readable text is the raw material; structure is what makes it usable. Check the
header tags give the page a sensible outline, confirm the
word count matches what you intended to publish, and look for
JavaScript errors that could be stopping content from arriving.