what agents see
example.com
useful to agents--%
Human view
Agent viewsending the agent to your site...
▌
visiting example.com twice: once in a real browser, once as an agent. takes about ten seconds.
what agents see
scan example.com on ora
example.com
useful to agentsHow much of your real content an agent can read. Content that only appears after JavaScript runs is what costs points; unusually heavy UI noise (menus, buttons, cookie banners) trims a few more. The cards below show each part on its own.100%healthy
Agents see exactly what humans see: a clean, simple page with no hidden content or noise.
Human view0 actions
Agent view~140 tokens
This domain is for use in documentation examples without needing permission. Avoid use in operations.
Content agents can read
100%
1 of 1 content blocks survive the trip. This drives the score up top; heavy UI noise only trims a few points.
What agents can use
0 of 0
actions on this page agents can call
Humans get 0 buttons and forms here. Agents get none of them. WebMCP is the emerging standard that fixes this, and being early stands out.
webmcp audit on ora →Who can view
- ChatGPTwelcome
- Claudewelcome
- Apple (AI)welcome
- Geminiwelcome
- Common Crawlwelcome
Your robots.txt turns no one away. Good.
How agents quote you
Example Domain
[ no description. agents improvise one for you. ]
This is your entire elevator pitch to an agent deciding whether to read on.
Weight vs words
559 B shipped · 127 B of words
Everything beyond the words is code and markup an agent downloads and throws away.
Where the tokens go
~140 tokens to read this page
- code & markup108 · 77%
- ui chrome & boilerplate7 · 5%
- your actual content25 · 18%
An agent pays for every token. Only the green ones are what you actually want it to read.
checked sun, 06 sep 2026 07:48
This was one page and one check.
Ora runs the full agent-readiness audit: can agents find you, read you, use you end to end, and pay you. Free, public, no signup.