jestjs.io

Scores

What this costs you

AI agents and answer engines are mostly failing to find, understand, or act on this site today. Every month this stands, AI-referred demand flows to competitors who are machine-ready.

Critical exposures

• Machine interfaces not advertised. Nothing in the HTML or HTTP headers points agents to your machine-readable surfaces. If an agent can't find the interface, the interface doesn't exist to it.
• No machine-readable identity. There's no Organization, WebSite, or Service markup telling engines who you are. AI answers can confuse your brand with others or leave it out entirely.
• API not described as a service. Your API exists but isn't described with WebAPI metadata. Procurement agents comparing vendors can't classify it, so it drops off shortlists.
• SEO score 60/100. The fundamentals classic search uses are also what AI engines ground on. Weak fundamentals here compound every gap above.

Operational friction

• High Integration Tax for AI Procurement Agents: no OpenAPI contract or MCP server. The site takes real inputs, but agents have no typed way to submit them. Each integration needs a human engineer, so autonomous buyers route to vendors who are callable today.

Issues & fixes

• Missing meta description
• No H1 found
• 4/16 images missing alt text
• Missing Content-Security-Policy header

Embed the badge

Show the live score in your README. The badge updates on every re-audit and greys out when the report is older than 30 days.

[![Agent-Ready badge](https://api.santosautomation.com/v1/badge?url=jestjs.io)](https://www.santosautomation.com/reports/jestjs.io)