example.com score

Critical access blockers remain

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.
3 / 3 passed
Core content is available
Useful content remains accessible without a fragile browser-only path.
0 / 1 passed
Navigation fails safely
Redirects and missing pages give agents a recoverable path.
1 / 2 passed
Controls are understandable
Forms and interactive controls expose usable names and structure.
1 / 1 passed

Fix these gaps first

Critical access gaps come first, followed by gaps in capabilities the site advertises.

01
Content without JavaScript
Server-side render your homepage so AI crawlers see meaningful content without JavaScript. Ensure an H1 and 500+ chars of text in raw HTML.
Critical access
02
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.
Critical access
03
JSON-LD structured data
Add JSON-LD structured data to your homepage using the identity type that matches your site - SoftwareApplication for products, Organization or LocalBusiness for companies, Person for personal sites, Article for blogs - with name, description, url, and type-appropriate fields (offers, sameAs, author) so AI can parse your identity programmatically.
Advertised capabilities
04
robots.txt AI crawler policy
Add explicit AI crawler directives in robots.txt. Allow the crawlers that feed answer engines ('User-agent: GPTBot' / 'Allow: /', same for ClaudeBot, PerplexityBot, OAI-SearchBot), and restrict training-only crawlers (CCBot, ByteSpider) with 'Disallow: /'. Content Signals ('Content-Signal: search=yes, ai-train=no') earns the same credit.
Advertised capabilities
05
Agent instruction / when-to-use
Tell agents when to reach for you: add a 'when to use this' section to your llms.txt (or a dedicated agent-instructions file) that names your best-fit use cases and how an agent should call you. Be specific about the jobs you are right for - generic marketing copy does not read as guidance.
Advertised capabilities

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.

Essential4 of 6 passed · 60 / 80 points

Content without JavaScriptFailed
Not blocked by bot detectionPassed
robots.txt agent-user policyPassed
Redirect hygienePassed
Agent crawler reachabilityPassed
Agent-friendly 404sPartial (50%)

Recommended1 of 10 passed · 3.7 / 20 points

Brand name discoverabilityPartial (33%)
robots.txt AI crawler policyFailed
Sitemap existsFailed
Content efficiencyFailed
JSON-LD structured dataFailed
Agent instruction / when-to-useFailed
Metadata completenessPartial (50%)
Organization schema completenessFailed
Trust anchor pagesFailed
Page token budgetPassed

Bonus signals3 positive · +0.8 points

Wikipedia / Wikidata entity presencePassed
Accessible names on controlsPassed
Accessibility-tree injection safety (bonus)Passed

Important blockers remain

What should the prompt cover?

How the score adds up

Starting an observed agent task

Critical access blockers remain

Advertised capabilities have material gaps

Public website

Fix these gaps first

Content without JavaScript

Agent-friendly 404s

JSON-LD structured data

robots.txt AI crawler policy

Agent instruction / when-to-use

Audit the checks behind the score

Inspect the underlying audit

Score alerts