Is xiaohongshu.com agent ready?
xiaohongshu.com is not yet agent ready: it scores 24/100 (grade F) on the w2agent rubric.
Changed since last check
−11 points since the previous check (2026-09-15)
Fixed: Content length, Content accessible without JS
Regressed: FAQ content, UTF-8 charset, Mobile viewport, Citation readiness, Lists and tables for structured info, Schema.org completeness
Changed: Answer-first content (partial → fail), Semantic HTML elements (partial → fail), Canonical URLs (partial → fail), Appropriate Schema.org type (partial → fail), Freshness signals (partial → fail), Heading hierarchy (partial → fail), Author attribution (partial → fail), Schema.org JSON-LD present (partial → fail)
Category scores
Category breakdown not recorded for this audit.
Agent protocol panel
- A2A agent cardNot found
- OAuth discoveryNot measured
- MCP discoveryNot found
- llms.txt validityNot measured
Check results
Bot Accessibility
- ✓No error status codespass
- ~Response timepartial
- ✓XML sitemap existspass
- ✗AI agent accessfail
- ✓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 elementsfail
- ✗Appropriate Schema.org typefail
- —JSON-LD validskip
- ✗Heading hierarchyfail
- ✗Schema.org JSON-LD presentfail
- ✗Schema.org completenessfail
Content Quality
- ✗FAQ contentfail
- ✗Answer-first contentfail
- ✓Content lengthpass
- ✓Token efficiency (HTML-to-text ratio)pass
- ✗Freshness signalsfail
- ✗Author attributionfail
- ~Citation readinesspartial
- ✗Lists and tables for structured infofail
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 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 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 portalpartial
- ✗Scoped API permissionsfail
- —API catalog (RFC 9727)skip
- —Agent operator signing directorytracked, not scoredskip
Technical
- ✓HTTPSpass
- ✗UTF-8 charsetfail
- ✗Canonical URLsfail
- ✗Mobile viewportfail
- ✓Content accessible without JSpass
- ✗Security headersfail
Score history
- 24/100 · rubric v3.0
- 35/100 · rubric v3.0
- 33/100 · rubric v2.0
- 33/100 · rubric v2.0
- 32/100 · rubric v2.0
- 32/100 · rubric v2.0