Atlassian

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.
• A
  llms.txt and llms-full.txtGood work./llms.txt found (26567 chars, 105 link(s)). /llms-full.txt found.
• A
  SitemapGood work.Sitemap index at https://www.atlassian.com/sitemap.xml (from robots.txt) with 8 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 discoverabilityThe API docs are hiding. Agents shouldn't need a treasure map.Key pages link to API docs (/developers), but no machine-readable spec was found at /openapi.json, /openapi.yaml, /swagger.json, /api/openapi.json, /.well-known/api-catalog.Extra credit: Publish an OpenAPI spec at /openapi.json and link it from your API docs and llms.txt. Agents can call an API they can read a spec for. 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.Key pages or llms.txt mention MCP, but no endpoint URL or discovery document was found.Extra credit: Document the MCP server URL and how to connect on a key page and in llms.txt. 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).
• F
  Page weight and token costThis homepage weighs more than my car. 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.