what agents see
doordash.com
useful to agents--%
Human view
Agent viewsending the agent to your site...
▌
visiting doordash.com twice: once in a real browser, once as an agent. takes about ten seconds.
what agents see
scan doordash.com on ora
doordash.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.0%blocked
Agents see a security wall, not your site: DoorDash blocks all bot traffic with a 403 error before any content loads.
what the agent hit: HTTP 403 for a bot request
Human view0 actions
Agent view~70k tokens
Performing security verification
This website uses a security service to protect against malicious bots. This page is displayed while the website verifies you are not a bot.
Verification successful. Waiting for www.doordash.com to respond
Ray ID: a36bde442b2bdc03
Performance and Security by Cloudflare Privacy
■ content the agent gets■ ui noise it skims past■ good content the agent never sees (needs js)
Fix this first
Work with your security team to allow legitimate AI agents (like search crawlers and accessibility tools) through your bot detection system, or you'll remain invisible to them.
Content agents can read
0%
0 of 3 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
checked sun, 06 sep 2026 07:47
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.