Is asana.com agent ready?
asana.com is largely agent ready: it scores 61/100 (grade B) on the w2agent rubric. Weakest areas: Agent Protocols (35), Structured Data (39).
Changed since last check
−3 points since the previous check (2026-09-16)
Fixed: Schema.org JSON-LD present, llms.txt links resolve
Regressed: Response time, Content negotiation (Markdown), Reachable as Perplexity-User
Changed: Heading hierarchy (partial → fail)
Category scores
Technical
94
Agent Auth
71
Agent Discovery
50
Agent Protocols
35
Content Quality
60
Structured Data
39
Bot Accessibility
79
Agent protocol panel
- A2A agent cardNot found
- OAuth discoveryPresent
- MCP discoveryPresent
- 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 hierarchyfail
- ✓Schema.org JSON-LD presentpass
- ✗Schema.org completenessfail
Content Quality
- ✓FAQ contentpass
- ✗Answer-first contentfail
- ✓Content lengthpass
- ✓Token efficiency (HTML-to-text ratio)pass
- ✗Freshness signalsfail
- ✗Author attributionfail
- ✓Citation readinesspass
- ✓Lists and tables for structured infopass
Agent Discovery
- ✓llms.txt follows specpass
- ✓llms.txt existspass
- —MCP server cardtracked, not scoredskip
- ✓Markdown alternate linkspass
- ✗/.well-known/agent-card.jsonfail
- ✓llms.txt links resolvepass
Agent Protocols
- ✗Discoverable API endpointsfail
- ✓MCP endpointpass
- ✗Action schemasfail
- —/.well-known/ucpskip
- ✗Structured formsfail
- —WebMCP imperative APItracked, not scoredskip
- —WebMCP declarative APItracked, not scoredskip
- ✓Reachable as Google-Agentpass
- ✓Reachable as ChatGPT-Userpass
- ✗Reachable as Perplexity-Userfail
Agent Auth
- —MCP authorization (401 challenge → protected resource metadata)skip
- ✓PKCE S256 supportpass
- ✗Public API surfacefail
- —Client ID Metadata Documents (bonus)skip
- —OpenAPI specificationskip
- ✓Agent/bot auth documentationpass
- ✓OAuth discovery chain (RFC 9728 → RFC 8414)pass
- ✓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
- ✗nextjs-metadata-apifail
- ~nextjs-static-generationpartial
- ✗nextjs-well-known-servedfail
- —local-business-hours-jsonldskip
- ~local-business-nap-structuredpartial
- —local-business-booking-accessibleskip
Score history
- 61/100 · rubric v3.0
- 64/100 · rubric v3.0
- 54/100 · rubric v3.0
- 51/100 · rubric v2.0
- 51/100 · rubric v2.0
- 51/100 · rubric v2.0
- 51/100 · rubric v2.0
- 45/100 · rubric v2.0
- 46/100 · rubric v2.0
- 45/100 · rubric v2.0
- 44/100 · rubric v2.0
- 45/100 · rubric v2.0
- 46/100 · rubric v2.0
- 54/100 · rubric v2.0
- 56/100 · rubric v2.0
- 56/100 · rubric v2.0