Retool

Subjects

• A
  robots.txt rules for AI agentsGood work.All 11 AI agents checked may fetch every key page. robots.txt names 6 AI agent(s) explicitly.
• B
  llms.txt and llms-full.txtGood work./llms.txt found (6094 chars, 43 link(s)). No /llms-full.txt.Extra credit: Improve llms.txt: publish /llms-full.txt with the full docs inlined.
• A
  SitemapGood work.Sitemap index at https://retool.com/sitemap.xml (from robots.txt) with 5 entries.
• 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 }).
• C
  MCP server discoverabilityMentions MCP, never shows up with it.An MCP endpoint is documented (https://dqpcjghenxt8u.cloudfront.net/icons/mcp-connections/mcp), but no /.well-known MCP discovery document.Extra credit: Publish /.well-known/mcp.json describing the server. Discovery through /.well-known/mcp.json is still a draft proposal, so also document the server URL, transport, and auth in llms.txt and your docs.
• A
  Auth, signup, and bot-challenge frictionGood work.No login walls, bot challenges, or CAPTCHAs on 1 key page(s).
• A
  Page weight and token costGood work.Key pages are light enough to read in one pass.