ServiceNow

Subjects

• C
  robots.txt rules for AI agentsLets some agents in and turns others away. Pick a lane.No robots.txt (HTTP 403). Agents are allowed by default, but there is no explicit AI agent policy and no Sitemap line.Extra credit: Publish /robots.txt with explicit groups for the AI agents you want (for example ClaudeBot, Claude-User, GPTBot, ChatGPT-User, and PerplexityBot) and a Sitemap: line.
• F
  llms.txt and llms-full.txtCouldn't check. The robot got a 403 at the door.No /llms.txt (HTTP 403).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.
• F
  SitemapCouldn't check. The robot got a 403 at the door.No valid XML sitemap at /sitemap.xml (HTTP 403).Extra credit: Publish /sitemap.xml listing your key pages and reference it from robots.txt with a Sitemap: line.
• F
  Server-rendered readable HTMLThe page is blank until JavaScript shows up. The robot is still waiting.1 of 1 key page(s) are thin or JS-only for a client that does not run JavaScript: /.Extra credit: Server-render or statically generate / so the main content, <title>, meta description, and <h1> are in the initial HTML. Most agents fetch HTML and never run your bundle.
• 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.
• N/A
  Structured data (JSON-LD)Excused.No key page could be fetched successfully.
• 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.
• F
  Auth, signup, and bot-challenge frictionEverything worth reading is behind a login wall.1 of 1 key page(s) put friction in front of an agent: / (HTTP 403).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.
• N/A
  Page weight and token costExcused.No key page could be fetched successfully.