Claude
- Rank
- 518 scoredNot ranked among 518 scored domains
- None
- SaaS rank
- Avg 71.3Sector average 71.3
- None
- Benchmark runs
- 3 providersAcross 3 providers
- 1
Where agents get stuck33 issues10 high severity. Worst: Homepage did not return 2xx (status 403) to a standard client.Technical readiness4/1006 essential checks failing, of 6. Protocol baseline by Is Agentic.
Our checks were blocked, so claude.ai is not scored
claude.ai turned our requests away. Sites that block automated requests often block agents too, but a blocked request alone is not a score. claude.ai stays out of rankings and averages until our checks or an agent get through.
Own claude.ai? Claim it to request a re-run.
Agents
Each provider’s model and every session behind its score.
Agents
Each provider’s model and every session behind its score.
How these are scored
The score beside each provider is its session quality over a rolling 30 days, from at least 10 sessions per provider.
Scores run 0 to 100. Each is one agent on one task, graded against that task’s fixed rubric, so no agent marks its own work. The median under a score is the sector median: the middle score for the same category, or the same provider, across the other SaaS sites the Index has sent agents to.
- Excellent85+
- Good72-84
- OK58-71
- Poor40-57
- Critical<40
No agent sessions yet
These scores come from probes only. Run the sessions and Claude, ChatGPT and Gemini each work through the sector’s tasks on the live site. The score updates when every session has finished.
ClaudeAnthropic62.3
ClaudeAnthropic
62.3
No Claude sessions in the latest run, so its score comes from earlier runs and the protocol probes.
ChatGPT AgentOpenAI26.0
ChatGPT AgentOpenAI
26.0
No ChatGPT Agent sessions in the latest run, so its score comes from earlier runs and the protocol probes.
GeminiGoogle26.0
GeminiGoogle
26.0
No Gemini sessions in the latest run, so its score comes from earlier runs and the protocol probes.
Where agents get stuck
33 issues, worst first.
Where agents get stuck
33 issues, worst first.
HighInformation retrieval
Homepage did not return 2xx (status 403) to a standard client.
HighInformation retrieval
Homepage ships little text to server-rendered HTML. Agents without a browser see an empty shell.
HighAccuracy
Brand name not present in server-rendered HTML. Non-JS agents may not associate the domain with the product.
HighTask completion
Homepage returns a bot-challenge / CAPTCHA. Agents can’t complete a task if they can’t load the site.
Evidence: HTTP 403 + cf-mitigated: challenge
Show 29 more issuesShow fewer
HighDelegated access
No discoverable MCP server. ChatGPT apps and Claude connectors have no scoped way to call your product; agents must drive a browser instead.
HighDelegated access
No public API docs detected. Agents have no scoped way in; they must drive a browser.
HighContact & communication
No contact page linked or reachable. Agents acting on a user’s behalf have nowhere to send a message.
HighTask completion
Claude hits a bot-challenge page on the homepage.
HighTask completion
ChatGPT Agent hits a bot-challenge page on the homepage.
HighTask completion
Gemini hits a bot-challenge page on the homepage.
MediumBrand awareness
No Organization JSON-LD. Agents can’t tell who owns the site at a glance.
MediumBrand awareness
Homepage meta description is missing or too short for agent snippets.
MediumDiscovery
No sitemap.xml. Agents can’t enumerate indexable pages.
MediumInformation retrieval
No JSON-LD structured data. Agents must infer entities from markup.
MediumMarket ranking
No Product/Service schema on the homepage. Agents can’t easily compare offerings.
MediumMarket ranking
No price visible to non-JS clients. Agents may report "pricing not disclosed".
MediumAccuracy
No freshness headers. Agents can’t tell when content was updated.
MediumAccuracy
No JSON-LD at all. Every factual claim must be inferred from prose.
MediumTask completion
No visible primary call-to-action in the server-rendered HTML. Agents have nothing concrete to click on behalf of a user.
MediumTask completion
The homepage has no link an agent can follow to start a task (pricing, sign-up, cart, booking). Links rendered only by JavaScript are invisible to agents that read the HTML.
MediumTask completion
No mention of delegated auth primitives (passkey, OAuth, MCP). Agents must drive a full browser session.
MediumDelegated access
No OAuth/OIDC discovery metadata. Agents cannot bootstrap a scoped, revocable session; any delegation falls back to password sharing.
MediumContact & communication
No contact email visible in server-rendered HTML. Agents can’t fall back to email.
MediumDiscovery
ChatGPT Agent is disallowed by robots.txt.
Evidence: Tokens checked: gptbot, chatgpt-user, oai-searchbot
MediumDiscovery
Gemini is disallowed by robots.txt.
Evidence: Tokens checked: google-extended, googlebot
LowBrand awareness
Missing Open Graph tags. Link previews degrade in agent chats.
LowBrand awareness
Fewer than two social profiles linked. Agents struggle to triangulate the brand.
LowDiscovery
No canonical URL. Agents may conflate duplicate pages as separate entities.
LowMarket ranking
No review or aggregateRating schema. Agents have no signal for ranking vs peers.
LowAccuracy
No canonical URL. Agents may cite ephemeral query-string variants.
LowAccuracy
No privacy policy linked from the homepage. Agents can’t cite policy when asked.
LowTask completion
No detectable agentic-commerce rail (Stripe SPT, Shopify/UCP, PayPal ACP). Agent-initiated payment needs custom work.
LowContact & communication
No help, support, or FAQ hub linked. Agents can’t self-serve an answer before reaching out.
Want to find these in your own flows before an agent does? Read how to test your product for AI agent users.
Technical readiness
The protocol baseline: robots, sitemaps, llms.txt, structured data and more.
4/100
Technical readiness
The protocol baseline: robots, sitemaps, llms.txt, structured data and more.
Protocol baseline by Is Agentic
- Score
- 4/ 100
- Agents are likely to struggle
- Essential
- 0/ 80
- 0 of 6 passing
- Recommended
- 2.7/ 20
- 1 of 15 passing
- Bonus
- +1
- 5 positive signals
Fail
Content without JavaScriptessential
Homepage blocked by WAF/security challenge - content not accessible to agents
Fix: Serve at least 500 characters of meaningful homepage content in raw HTML. Add a clear H1, keep deeper heading levels sequential, and remove excessive non-content markup.
Fail
Not blocked by bot detectionessential
Bot management challenged GPTBot, ClaudeBot, ChatGPT-User, PerplexityBot, Google-Extended, Applebot-Extended. A challenge is an identity check that verified crawlers pass, so this is not proof agents are blocked - but unverified agents will not get through.
Fix: Allowlist known AI agent User-Agents (ChatGPT-User, ClaudeBot, Google-Extended, DeepSeekBot) in your WAF or bot-detection rules.
Fail
Agent crawler reachabilityessential
Bot management challenged ChatGPT-User, ClaudeBot, Google-Extended, ora-agent, DeepSeekBot - a challenge is an identity check verified crawlers pass, so reachability is undetermined rather than blocked (ChatGPT-User: challenged, ClaudeBot: challenged, Google-Extended: challenged, ora-agent: challenged, DeepSeekBot: challenged)
Fix: Verify that major agent User-Agents can reach the homepage. If your WAF or bot rules block them, remove or narrow the blocking rule. Add an allow rule only when your security setup denies them by default.
Show 17 more issuesShow fewer
Fail
OpenAPI spec publishedessential
No OpenAPI/Swagger specification found
Fix: Publish an OpenAPI (Swagger) specification at /openapi.json or /api/openapi.yaml. This is how agents understand your API surface automatically.
Fail
JSON error responsesessential
API does not return JSON error responses (or no API detected)
Fix: Return structured JSON error responses with error codes, messages, and resolution hints. Agents can't parse HTML error pages.
Fail
Markdown content negotiation (acceptmarkdown.com)essential
Homepage https://claude.ai does not meet the Markdown negotiation requirements: Accept: text/markdown returned text/html; charset=utf-8; Vary header missing Accept (got "accept-encoding")
Fix: Enable Markdown negotiation on the scanned homepage. Supporting it only on /docs or a separate .md URL does not satisfy this check. Requests with Accept: text/markdown must receive a nonempty Markdown body with Content-Type: text/markdown and Vary: Accept. Keep serving HTML for Accept: text/html. Adding Vary alone does not create a Markdown response. Verify both with `curl -sS -L -i -H 'Accept: text/markdown' https://yourdomain.com/` and `curl -sS -L -i -H 'Accept: text/html' https://yourdomain.com/`. Check the final response headers and body: Markdown with Vary: Accept for the first request, HTML for the second.
Fail
Developer resource discoverabilityrecommended
Agent searched for "claude" developer resources but found nothing relevant
Fix: Check whether your developer resources (API docs, OpenAPI spec, auth docs, developer portal, MCP server, SDK documentation) surface in name-based searches. If they do not, use predictable URLs, link them in llms.txt, and include your product name in page titles and headings. This result reflects one search sample.
Fail
Developer portalrecommended
No developer portal found
Fix: Create a developer portal at /developers with API keys, documentation, quickstart guides, and a sandbox environment.
Fail
JSON-LD structured datarecommended
Homepage blocked by WAF - cannot check structured data
Fix: 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.
Fail
CLI tool availablerecommended
No CLI tool found
Fix: Publish an official CLI tool on npm, PyPI, or Homebrew. A CLI lets agents and developers script interactions with your product without building API integrations from scratch.
Fail
Public API/docs linked from homepagerecommended
Homepage blocked by WAF - cannot check for docs links
Fix: Publish API documentation at a discoverable URL (/docs, /api, /developers). Include authentication, endpoints, and example requests.
Fail
Rate limit response headersrecommended
GraphQL introspection auth-gated and no header convention documented on GraphQL-tagged pages
Fix: Return standard rate-limit headers on your API responses (the RFC RateLimit headers, plus Retry-After on a 429) so agents can self-throttle in real time, and document the conventions alongside your API.
Fail
API schema complexity analysisrecommended
GraphQL: introspection auth-gated and no schema evidence in docs
Fix: 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.
Fail
Function calling compatibilityrecommended
No API spec found - function calling requires discoverable endpoints
Fix: Ensure API endpoints have unique operation IDs, typed schemas, and descriptions compatible with LLM function-calling formats.
Fail
Sitemap existsrecommended
No sitemap found
Fix: Add a valid XML sitemap at /sitemap.xml listing all indexable URLs. Include lastmod dates and keep it under 50MB.
Fail
Metadata completenessrecommended
Homepage blocked by WAF - cannot check metadata
Fix: Add all four signals to your homepage: <link rel="canonical">, <html lang="...">, <meta property="og:image">, and <meta property="og:type">. Agents use these for entity resolution and attribution.
Fail
Organization schema completenessrecommended
Homepage blocked by WAF - cannot check Organization schema
Fix: Add Organization JSON-LD that includes both contactPoint (with email/phone and contactType) and address (PostalAddress). This lets AI verify your business legitimacy and answer contact queries.
Fail
Trust anchor pagesrecommended
No trust anchor pages found with sufficient content (About, Contact, Privacy)
Fix: 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.
Partial
Brand name discoverabilityrecommended
claude.ai appears once in brand-name search results for "claude ai ml" (position #8 out of 9)
Fix: Make sure a clean search for your brand name returns your own domain in the top results. If it does not, your brand may be too generic, conflict with a more established term, or not yet indexed. Strengthen brand-name search by claiming consistent NAP across listings, earning press mentions that link to the canonical domain, and avoiding redirect chains that mask the apex domain in search results.
Partial
Agent instruction / when-to-userecommended
Agent instruction file at /agent.txt but no explicit when-to-use guidance
Fix: 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.
21 checks · scanned 26 Sept 2026
Embed
Put this score on your site
A live badge for your footer, docs or README. It updates after every run and links back to this report.
Copy as