Is figma.com agent ready?
figma.com is partly agent ready: it scores 52/100 (grade C) on the w2agent rubric. Weakest areas: Structured Data (29), Agent Discovery (36), Content Quality (38).
Changed since last check
+1 points since the previous check (2026-09-16)
Fixed: Response time
Category scores
Technical
71
Agent Auth
50
Agent Discovery
36
Agent Protocols
53
Content Quality
38
Structured Data
29
Bot Accessibility
93
Agent protocol panel
- A2A agent cardNot found
- OAuth discoveryPresent
- MCP discoveryPresent
- llms.txt validityPresent
Check results
Bot Accessibility
- ✓No error status codespass
- ✓Response timepass
- ✓XML sitemap existspass
- ✓AI agent accesspass
- ✓Edge treatment of agent user-agentstracked, not scoredpass
- ✓robots.txt existspass
- ✗Content negotiation (Markdown)fail
- —Declared AI usage preferencestracked, not scoredskip
Structured Data
- ~OpenGraph meta tagspartial
- ~Semantic HTML elementspartial
- ~Appropriate Schema.org typepartial
- ✓JSON-LD validpass
- ~Heading hierarchypartial
- ~Schema.org JSON-LD presentpartial
- ~Schema.org completenesspartial
Content Quality
- ✗FAQ contentfail
- ~Answer-first contentpartial
- ✓Content lengthpass
- ✓Token efficiency (HTML-to-text ratio)pass
- ✗Freshness signalsfail
- ✗Author attributionfail
- ✓Citation readinesspass
- ~Lists and tables for structured infopartial
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 endpointpass
- ✗Action schemasfail
- —/.well-known/ucpskip
- —Structured formsskip
- —WebMCP imperative APItracked, not scoredskip
- —WebMCP declarative APItracked, not scoredskip
- ✓Reachable as Google-Agentpass
- ✓Reachable as ChatGPT-Userpass
- ✓Reachable as Perplexity-Userpass
Agent Auth
- —MCP authorization (401 challenge → protected resource metadata)skip
- ✓PKCE S256 supportpass
- ~Public API surfacepartial
- —Client ID Metadata Documents (bonus)skip
- ✗OpenAPI specificationfail
- ✗Agent/bot auth documentationfail
- ✓OAuth discovery chain (RFC 9728 → RFC 8414)pass
- ✓Developer portalpass
- ✗Scoped API permissionsfail
- ✗API catalog (RFC 9727)fail
- —Agent operator signing directorytracked, not scoredskip
Technical
- ✓HTTPSpass
- ✗UTF-8 charsetfail
- ~Canonical URLspartial
- ✗Mobile viewportfail
- ✓Content accessible without JSpass
- ✓Security headerspass
Other
- ✗nextjs-metadata-apifail
- ~nextjs-static-generationpartial
- ✗nextjs-well-known-servedfail
Score history
- 52/100 · rubric v3.0
- 51/100 · rubric v3.0
- 52/100 · rubric v3.0
- 47/100 · rubric v2.0
- 47/100 · rubric v2.0
- 45/100 · rubric v2.0
- 45/100 · rubric v2.0
- 52/100 · rubric v2.0