zenrows.com
Strong technical baseline
Technical readiness score
Starting an observed agent task
This run is collected separately from the technical score and will appear here as the agent moves through the public site.
Critical access needs attention
These checks describe whether an ordinary agent can enter, read, and operate the public site.
- 3 / 3 passed
Agents can reach the site
Crawler access, bot defenses, and explicit agent policy.
- 1 / 1 passed
Core content is available
Useful content remains accessible without a fragile browser-only path.
- 1 / 2 passed
Navigation fails safely
Redirects and missing pages give agents a recoverable path.
- 3 / 3 passed
Controls are understandable
Forms and interactive controls expose usable names and structure.
Advertised capabilities have material gaps
Optional surfaces appear only when the scan finds positive evidence that the site offers them.
Public website
Ready with gaps
14 of 20 mature checks passed
API
Needs work
5 of 9 mature checks passed
Authentication
Strong
3 of 3 mature checks passed
MCP
Strong
2 of 3 mature checks passed
Fix these gaps first
Critical access gaps come first, followed by gaps in capabilities the site advertises.
- 01Critical access
Agent-friendly 404s
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.
- 02Advertised capabilities
OpenAPI spec published
Publish an OpenAPI (Swagger) specification at /openapi.json or /api/openapi.yaml. This is how agents understand your API surface automatically.
- 03Advertised capabilities
API schema complexity analysis
Make your API spec self-describing: a unique operationId and a description on every operation, typed parameters, and response schemas. For GraphQL, a fully typed schema with a documented cost or rate limit reads best.
- 04Advertised capabilities
Content crawl depth signals
Add <link rel="next"> and <link rel="prev"> tags on paginated pages (blog archives, product listings, docs) so AI crawlers can traverse beyond the first page.
- 05Advertised capabilities
Developer resource discoverability
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.
Audit the checks behind the score
Applicable evidence is grouped by how it contributes to this preview model. Bonus checks appear only when they add points.
Essential10 of 12 passed · 70 / 80 points
- Content without JavaScriptPassed
- Not blocked by bot detectionPassed
- robots.txt agent-user policyPassed
- Redirect hygienePassed
- OpenAPI spec publishedFailed
- Markdown content negotiation (acceptmarkdown.com)Passed
- Agent crawler reachabilityPassed
- OAuth 2.0 supportPassed
- Scoped permissionsPassed
- JSON error responsesPassed
- MCP resources exposedPassed
- Agent-friendly 404sPartial (50%)
Recommended14 of 23 passed · 15.7 / 20 points
- Developer resource discoverabilityPartial (33%)
- Brand name discoverabilityPassed
- robots.txt AI crawler policyPassed
- Sitemap existsPassed
- Content efficiencyPassed
- Content crawl depth signalsFailed
- JSON-LD structured dataPartial (50%)
- Public API/docs linked from homepagePassed
- Agent instruction / when-to-usePartial (67%)
- Metadata completenessPassed
- Organization schema completenessPartial (50%)
- Trust anchor pagesPassed
- Page token budgetPassed
- Code fence validityPassed
- Developer portalPassed
- Public API with reachable endpointsPassed
- Agent onboarding frictionPassed
- MCP server / manifestPartial (83%)
- CLI tool availablePassed
- Multi-language SDK packagesPartial (67%)
- API schema complexity analysisFailed
- Function calling compatibilityPartial (50%)
- MCP resource qualityPassed
Bonus signals38 positive · +5 points
- Listed in MCP registriesPassed
- NPM/PyPI SDK packagePassed
- Registry brandingPartial (50%)
- Agent discovery filePassed
- Agent Skills index conformance (v0.2.0)Passed
- pricing.md existsPassed
- MCP well-known discoveryPassed
- HTTP Link headers (RFC 8288)Passed
- Sitemap freshness (lastmod)Passed
- llms.txt existsPassed
- llms.txt formattingPartial (50%)
- JSON-LD entity linking (sameAs)Passed
- Schema type breadthPartial (50%)
- llms.txt links resolvePassed
- Markdown frontmatter metadataPassed
- API catalog (RFC 9727)Partial (50%)
- Markdown agent docsPassed
- MCP tool descriptionsPassed
- MCP parameter schemasPassed
- MCP server identityPassed
- MCP tool listingPassed
- MCP tool namingPassed
- MCP auth mechanismPassed
- MCP OAuth metadataPassed
- MCP PKCE S256 supportPassed
- OAuth Protected Resource metadata (RFC 9728)Passed
- auth.md structurePartial (50%)
- auth.md walkthrough simulationPartial (50%)
- Agent auth discovery metadataPartial (33%)
- MCP error handlingPassed
- MCP modern transportPassed
- MCP tool annotationsPassed
- MCP server-card.jsonPartial (75%)
- Product + docs MCP coveragePassed
- Accessible document structurePassed
- Native interactive controlsPassed
- Accessible names on controlsPassed
- Accessibility-tree injection safety (bonus)Passed
Inspect the underlying audit
The complete Ora audit uses evidence from the scan on . After applying changes, run another scan from the homepage to refresh these recommendations.
Score alerts
A weekly report with ranking changes, new agent feedback, and score alerts for zenrows.com.
Source: Ora API
Snapshot 2026-08-20T18-08-08-502Z