Automation Anywhere

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.
• B
  llms.txt and llms-full.txtGood work./llms.txt found (8077 chars, 48 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://www.automationanywhere.com/sitemap-index.xml (from robots.txt) with 10 entries.
• A
  Server-rendered readable HTMLGood work.All 1 key page(s) return readable HTML without running JavaScript.
• F
  Markdown versions of key pagesHands in every page as HTML soup. Markdown was on the syllabus.1 of 1 key page(s) have no markdown version: /.Extra credit: Serve markdown for key pages, either at the same path plus .md or when the request sends Accept: text/markdown, and advertise it with <link rel="alternate" type="text/markdown" href="...">. Markdown cuts token cost and removes layout noise for agents.
• 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.
• A
  Auth, signup, and bot-challenge frictionGood work.No login walls, bot challenges, or CAPTCHAs on 1 key page(s).
• D
  Page weight and token costA little heavy. Agents pay by the token.1 of 1 key page(s) cost over 20k tokens for an agent to read: /.Extra credit: Cut the token cost of /: serve a markdown version, move inline scripts, styles, and SVG out of the HTML, and avoid large inlined JSON state.