Clay

Subjects

• A
  robots.txt rules for AI agentsGood work.All 11 AI agents checked may fetch every key page. No AI agent is named, so they all fall back to the * group.Extra credit: Add explicit User-agent groups for the AI agents you want, so your policy is a decision rather than a default.
• F
  llms.txt and llms-full.txtNo llms.txt. Please see me after class.No /llms.txt (HTTP 404).Extra credit: Publish /llms.txt: a markdown file with an H1 product name, a one-paragraph > summary, and sections of links to your most useful docs. Add /llms-full.txt with the full docs inlined if they fit in a model context.
• B
  SitemapGood work.Sitemap at https://www.clay.com/guides/sitemap.xml (from robots.txt) with 109 entries. 1 key page(s) not listed.Extra credit: Add these key pages to the sitemap: /.
• A
  Server-rendered readable HTMLGood work.All 1 key page(s) return readable HTML without running JavaScript.
• B
  Markdown versions of key pagesGood work.Every key page has a markdown version.Extra credit: Advertise the markdown versions of / with <link rel="alternate" type="text/markdown">.
• A
  Structured data (JSON-LD)Good work.Every key page has valid JSON-LD.
• F
  OpenAPI and API docs discoverabilityCouldn't find the API docs. Neither could the robot.No API spec at /openapi.json, /openapi.yaml, /swagger.json, /api/openapi.json, /.well-known/api-catalog and no API docs link on key pages or in llms.txt.Extra credit: Publish an OpenAPI spec at /openapi.json and link API docs from your homepage and llms.txt. If the product has no API, disable this check in config ("api-docs": { "enabled": false }).
• F
  MCP server discoverabilityNo MCP server in sight. Ironic, for an agent company.No MCP server found: no /.well-known MCP document and no mention on key pages or in llms.txt.Extra credit: If you offer an MCP server, document its URL, transport, and auth in llms.txt and your docs. If you do not, an MCP server is the most direct way for agents like Claude Code to use your product. Disable this check in config ("mcp": { "enabled": false }) if it does not apply.
• C
  Auth, signup, and bot-challenge frictionToo many doors need a badge. Agents don't have one.1 of 1 key page(s) put friction in front of an agent: / (CAPTCHA widget).Extra credit: Keep docs, pricing, and the product overview public. Let verified AI agents past bot challenges (most WAFs allowlist known agent user agents), and offer API keys or OAuth that an agent can use without a browser CAPTCHA.
• A
  Page weight and token costGood work.Key pages are light enough to read in one pass.