sazabi.com
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.
Optional surfaces appear only when the scan finds positive evidence that the site offers them.
Needs work
22 of 47 mature checks passed
Blocked
3 of 9 mature checks passed
Blocked
0 of 1 mature checks passed
Critical access gaps come first, followed by gaps in capabilities the site advertises.
Server-side render your homepage so AI crawlers see meaningful content without JavaScript. Ensure an H1 and 500+ chars of text in raw HTML.
Publish an OpenAPI (Swagger) specification at /openapi.json or /api/openapi.yaml. This is how agents understand your API surface automatically.
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.
Add JSON-LD structured data to your homepage (Organization, Product, or SoftwareApplication schema) so AI can parse your identity programmatically.
Support streaming responses (SSE or chunked transfer) for long-running operations. Agents need progress feedback, not just final results.
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 sazabi.com.
Source: Ora API
Snapshot 2026-04-19T01-42-24-716+00-00