Is atlassian.com agent ready?

atlassian.com is partly agent ready: it scores 53/100 (grade C) on the w2agent rubric. Weakest areas: Agent Auth (22), Agent Protocols (26), Structured Data (36), Agent Discovery (47).

53/ 100
Grade: C

Last checked

Scored Oct 14, 2026 · Rubric v3.0

Changed since last check

−2 points since the previous check (2026-09-16)

Regressed: llms.txt links resolve, Reachable as Google-Agent

Changed: Response time (partial → fail)

Category scores

Technical
100
Agent Auth
22
Agent Discovery
47
Agent Protocols
26
Content Quality
82
Structured Data
36
Bot Accessibility
79

Agent protocol panel

  • A2A agent cardNot found
  • OAuth discoveryNot measured
  • MCP discoveryNot found
  • llms.txt validityPresent

Check results

Bot Accessibility

  • ✓No error status codespass
  • ✗Response timefail
  • ✓XML sitemap existspass
  • ✓AI agent accesspass
  • ?Edge treatment of agent user-agentstracked, not scorederror
  • ✓robots.txt existspass
  • ✗Content negotiation (Markdown)fail
  • —Declared AI usage preferencestracked, not scoredskip

Structured Data

  • ✓OpenGraph meta tagspass
  • ~Semantic HTML elementspartial
  • ✗Appropriate Schema.org typefail
  • ✗JSON-LD validfail
  • ~Heading hierarchypartial
  • ~Schema.org JSON-LD presentpartial
  • ✗Schema.org completenessfail

Content Quality

  • ✓FAQ contentpass
  • ✓Answer-first contentpass
  • ✓Content lengthpass
  • ✓Token efficiency (HTML-to-text ratio)pass
  • ✗Freshness signalsfail
  • ✓Author attributionpass
  • ✓Citation readinesspass
  • ✓Lists and tables for structured infopass

Agent Discovery

  • ✓llms.txt follows specpass
  • ✓llms.txt existspass
  • —MCP server cardtracked, not scoredskip
  • ✗Markdown alternate linksfail
  • ✗/.well-known/agent-card.jsonfail
  • ~llms.txt links resolvepartial

Agent Protocols

  • ✗Discoverable API endpointsfail
  • ✗MCP endpointfail
  • ✗Action schemasfail
  • —/.well-known/ucpskip
  • ~Structured formspartial
  • —WebMCP imperative APItracked, not scoredskip
  • —WebMCP declarative APItracked, not scoredskip
  • ✗Reachable as Google-Agentfail
  • ✓Reachable as ChatGPT-Userpass
  • ✓Reachable as Perplexity-Userpass

Agent Auth

  • —MCP authorization (401 challenge → protected resource metadata)skip
  • ✗PKCE S256 supportfail
  • ✗Public API surfacefail
  • —Client ID Metadata Documents (bonus)skip
  • —OpenAPI specificationskip
  • ✗Agent/bot auth documentationfail
  • —OAuth discovery chain (RFC 9728 → RFC 8414)skip
  • ✓Developer portalpass
  • ✗Scoped API permissionsfail
  • —API catalog (RFC 9727)skip
  • —Agent operator signing directorytracked, not scoredskip

Technical

  • ✓HTTPSpass
  • ✓UTF-8 charsetpass
  • ✓Canonical URLspass
  • ✓Mobile viewportpass
  • ✓Content accessible without JSpass
  • ✓Security headerspass

Other

  • —local-business-hours-jsonldskip
  • —local-business-nap-structuredskip
  • —local-business-booking-accessibleskip

Score history

  • 53/100 · rubric v3.0
  • 55/100 · rubric v3.0
  • 54/100 · rubric v3.0
  • 52/100 · rubric v2.0
  • 52/100 · rubric v2.0
  • 51/100 · rubric v2.0
  • 51/100 · rubric v2.0
  • 45/100 · rubric v2.0

Related websites