What agents reach on a site: two Ora studies side by side
In short
Ora's June study found agents used docs pages 88 percent of the time and the homepage 84 percent when they existed, against 46 percent for llms.txt and 5 percent for llms-full.txt. Its October study found 86 percent of llms.txt fetches arrived through a link. Both are vendor results with different units.
The check we recommend
Ora's scan. Its Access layer runs 42 checks worth 30 of its 100 points, from content without JavaScript to markdown on request. Every check is listed at ora.ai/api/checks with its tier, and 25 of the 132 with a spec link. Reads need no key and no sign-up (Ora's pricing page, read 5 November 2026).
Ora reads public URLs only, says two runs of one scan land within a couple of points without publishing repeat-scan data, and keeps the product that fixes what it finds behind a waitlist.
Two of Ora's published studies describe where agents go on a site. They measure different things and should not be added together, but they agree on the order: the pages a person would open first come before the files made for machines, and the machine files are reached mostly through links. Every figure here is Ora's, taken from the posts named under each chart and labelled as a vendor result.
When a resource exists, how often agents use it
Ora's research post of 16 June 2026 drew on episodes of agents landing on websites and trying to get something done. For each resource it reports the usage rate once the resource existed on a site.
Text equivalent of this chart
| Resource | Value (%) | Counts |
|---|---|---|
| Docs pages | 88 | |
| Homepage | 84 | |
| llms.txt | 46 | |
| .well-known files | 34 | |
| openapi.json | 17 | |
| robots.txt and sitemap.xml | 9 | |
| agents.md | 8 | |
| llms-full.txt | 5 |
How many runs reach each surface
The AgentReady launch post of 19 October 2026 reports the share of traced runs that reached each surface at least once. The homepage figure is lower than in June because the unit changed: a share of runs, not a rate among sites that have the resource.
Text equivalent of this chart
| Surface | Value (%) | Counts |
|---|---|---|
| Docs pages | 83 | |
| Homepage | 69 | |
| .well-known files | 23 | |
| openapi.json (sites that ship one) | 21 | |
| sitemap.xml | 4 |
Links beat guessed paths
When agents did open a file, they mostly got there by following a link from a page they had already read. A file that nothing links to is reached late or not at all, which is why this site links its own llms.txt from every page.
Text equivalent of this chart
| File | Value (%) | Counts |
|---|---|---|
| openapi.json | 97 | |
| .well-known files | 93 | |
| llms.txt | 86 |
The order of arrival
In the June episodes the homepage arrived on turn 1.0 on average, docs on 1.7, llms.txt and openapi.json on 3.0, agents.md on 4.6 and llms-full.txt on 6.7. The homepage was reached in about 84 percent of runs, almost always on the first turn (about 95 percent). Whatever the homepage's initial HTML leaves out, the run starts without. The viewer shows what it carries and the guide to checking it like an agent measures it.
The same files, reached or not
Ora reports that on the one site in its set that shipped the full stack and linked it, the same files were used far more: openapi.json rose from 17 to 72 percent, .well-known files from 34 to 63 percent and agents.md from 8 to 42 percent. That site is ora.ai itself, so the result is a single vendor case, but the direction matches the link figures above. Ora also found that a reachable page with stale or wrong content hurts more than no page, because the agent trusts it.
What this site draws from it
Put the answer in the homepage HTML, link llms.txt and any OpenAPI file from pages agents already read, and serve the conventional paths agents guess. For a whole-site check against those behaviours, the check we recommend is Ora's scan, which is also the source of these studies. Ora's limits are printed beside the recommendation.
Cite this: Agent Ready HTML. What agents reach on a site. Edition 2026-11-04. https://agentreadyhtml.com/what-agents-reach/
Sources
- Ora research: What agents actually reach (2026-06-16) https://ora.ai/blog/what-agents-actually-reach, read 5 November 2026
- Ora: AgentReady launch post (Ora's lab findings, 2026-10-19) https://ora.ai/blog/agentready-launch, read 5 November 2026
- Ora home page (the studies are listed on it) https://ora.ai/, read 5 November 2026
Last reviewed 5 November 2026