Live audit score while evidence arrives
The completed evidence will be reorganized into Essential, Recommended, and Bonus signals when the scan settles.
This run is collected separately from the technical score.
The latest completed checks appear here while the full report is assembled.
agentmail.to
Technical readiness score
This run is collected separately from the technical score and will appear here as the agent moves through the public site.
These checks describe whether an ordinary agent can enter, read, and operate the public site.
Agents can reach the site
Crawler access, bot defenses, and explicit agent policy.
Core content is available
Useful content remains accessible without a fragile browser-only path.
Navigation fails safely
Redirects and missing pages give agents a recoverable path.
Controls are understandable
Forms and interactive controls expose usable names and structure.
Optional surfaces appear only when the scan finds positive evidence that the site offers them.
Ready with gaps
13 of 20 mature checks passed
Ready with gaps
11 of 16 mature checks passed
Ready with gaps
0 of 1 mature checks passed
Critical access gaps come first, followed by gaps in capabilities the site advertises.
Return a real HTTP 404 (or 410) status for nonexistent paths - never a 200 with your app shell, which makes agents believe every path exists. For full credit, give the 404 response a short markdown body pointing agents at your sitemap, llms.txt, or docs index. Verify with `curl -s -o /dev/null -w "%{http_code}" https://yourdomain.com/some-path-that-does-not-exist` - it must print 404.
Server-side render your homepage so AI crawlers see meaningful content without JavaScript. Ensure an H1 and 500+ chars of text in raw HTML.
Make your developer resources (API docs, OpenAPI spec, auth docs, webhooks, MCP server) discoverable by name. Publish them at predictable URLs, list them in llms.txt, and include your product name in page titles and headings so search engines surface them for name-based queries.
Reduce markup overhead so readable text is at least 5% of your HTML. Strip unused inline scripts/styles, server-render content instead of shipping large JSON hydration blobs, and keep wrapper nesting shallow.
Publish real /about, /contact, and /privacy pages with at least 500 characters of content each. These are the pages AI agents check to verify your business is legitimate before recommending you.
Applicable evidence is grouped by how it contributes to this preview model. Bonus checks appear only when they add points.
The complete Ora audit uses evidence from the scan on . After applying changes, run another scan from the homepage to refresh these recommendations.
A weekly report with ranking changes, new agent feedback, and score alerts for agentmail.to.
Source: Ora API
Snapshot 2026-08-20T19-41-06-394Z
One run shows how an agent performed, but it does not determine the technical score.
Task
24 steps9 reasoning steps5 searches