Is craigslist.org agent ready?
craigslist.org is not yet agent ready: it scores 34/100 (grade D) on the w2agent rubric. Weakest areas: Agent Discovery (0), Agent Auth (20), Structured Data (27), Agent Protocols (37), Content Quality (37), Bot Accessibility (49).
Changed since last check
+3 points since the previous check (2026-09-15)
Fixed: Citation readiness, Reachable as ChatGPT-User
Category scores
Technical
81
Agent Auth
20
Agent Discovery
0
Agent Protocols
37
Content Quality
37
Structured Data
27
Bot Accessibility
49
Agent protocol panel
- A2A agent cardNot found
- OAuth discoveryNot found
- MCP discoveryNot found
- llms.txt validityNot measured
Check results
Bot Accessibility
- ~No error status codespartial
- ~Response timepartial
- ✗XML sitemap existsfail
- ✓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 hierarchyfail
- ~Schema.org JSON-LD presentpartial
- ~Schema.org completenesspartial
Content Quality
- ✗FAQ contentfail
- ~Answer-first contentpartial
- ~Content lengthpartial
- ✓Token efficiency (HTML-to-text ratio)pass
- ✗Freshness signalsfail
- ✗Author attributionfail
- ✓Citation readinesspass
- ✓Lists and tables for structured infopass
Agent Discovery
- —llms.txt follows specskip
- ✗llms.txt existsfail
- —MCP server cardtracked, not scoredskip
- ✗Markdown alternate linksfail
- ✗/.well-known/agent-card.jsonfail
- —llms.txt links resolveskip
Agent Protocols
- ✗Discoverable API endpointsfail
- ✗MCP endpointfail
- ✓Action schemaspass
- —/.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 supportskip
- ✓Public API surfacepass
- —Client ID Metadata Documents (bonus)skip
- ✗OpenAPI specificationfail
- —Agent/bot auth documentationskip
- ✗OAuth discovery chain (RFC 9728 → RFC 8414)fail
- ✗Developer portalfail
- —Scoped API permissionsskip
- ✗API catalog (RFC 9727)fail
- —Agent operator signing directorytracked, not scoredskip
Technical
- ✓HTTPSpass
- ✓UTF-8 charsetpass
- ~Canonical URLspartial
- ✓Mobile viewportpass
- ✓Content accessible without JSpass
- ✓Security headerspass
Score history
- 34/100 · rubric v3.0
- 31/100 · rubric v3.0
- 31/100 · rubric v3.0
- 50/100 · rubric v2.0
- 50/100 · rubric v2.0
- 49/100 · rubric v2.0
- 49/100 · rubric v2.0
- 43/100 · rubric v2.0