Agent-Readiness Grade

Agent-Readiness Grade / weibo.com

F

weibo.com

4/12 · 33% (scaled from 5 measurable areas)

Graded 2026-10-03 00:40 UTC in 5.8s · JSON · re-grade now

Top fixes

  1. Crawler access (+2 points): Add a group for GPTBot, ClaudeBot, OAI-SearchBot and the others with "Allow: /" (or drop the blanket "Disallow: /") if you want answer engines to cite you. How to fix
  2. Structured data (+2 points): add a JSON-LD block (Organization or WebSite, plus Product, FAQPage or Article where relevant); add og:title and og:description so answer engines describe you accurately. How to fix
  3. MCP census entry (+2 points): Expose a Streamable HTTP MCP endpoint at /mcp (or a paid x402 route) so agents can call you, not just read you. How to fix

Ordered by points recoverable. Each area: 2/2 pass, 1/2 warn, 0/2 fail.

weibo.com is graded F. The $49 AI Visibility Full Report turns the 2 failing checks above (crawler access, structured data) into a prioritized, specific fix list for weibo.com, and tests 8 real buyer questions across ChatGPT-class models to show what AI answers say about you today.

Get the full report — $49 Stripe checkout asks for your brand name and category; the report is ready about 60 seconds after payment. Legal notices and the MCP census entry are not in this report (free: Compliance Desk check, census claim).

Crawler access (robots.txt)

0/2 · fail

0 of 8 AI crawlers may read the site, 8 disallowed

  • GET /robots.txt -> HTTP 200, 968 B, 4 user-agent groups
  • Disallowed: GPTBot (via *), ClaudeBot (via *), OAI-SearchBot, PerplexityBot (via *), Google-Extended (via *), Amazonbot (via *), CCBot (via *), Bytespider
  • "User-agent: *" disallows the whole site; only crawlers named explicitly may read it
  • Content-Signal: search=yes, ai-input=yes, ai-train=no; search=yes, ai-input=yes, ai-train=no; search=yes, ai-input=yes, ai-train=no; search=yes, ai-input=yes, ai-train=no
  • Sitemap declared: https://weibo.com/sitemap.xml

Fix: Add a group for GPTBot, ClaudeBot, OAI-SearchBot and the others with "Allow: /" (or drop the blanket "Disallow: /") if you want answer engines to cite you.

Machine-readable surfaces

1/2 · warn

1 of 7 surfaces present (/sitemap.xml)

  • /llms.txt: HTTP 200 but an HTML page (catch-all route, not a real file)
  • /sitemap.xml: HTTP 200, sitemap index (1.5 KB)
  • /.well-known/x402: HTTP 200 but an HTML page (catch-all route, not a real file)
  • /.well-known/agent-card.json: HTTP 200 but an HTML page (catch-all route, not a real file)
  • /.well-known/mcp-registry-auth: HTTP 200 but an HTML page (catch-all route, not a real file)
  • /openapi.json: HTTP 200 but an HTML page (catch-all route, not a real file)
  • /ai.txt: HTTP 200 but an HTML page (catch-all route, not a real file)

Fix: Publish /llms.txt (a short Markdown guide to your key pages); one agent surface: /openapi.json, /.well-known/agent-card.json, or /.well-known/x402 if you sell to agents.

Readable without JavaScript

2/2 · pass

Home page is readable

  • GET https://weibo.com/ -> HTTP 200 after 1 redirect (final: https://weibo.com/us), text/html, 89 KB
  • 551 characters of visible text with scripts, styles and tags removed; <title>: "微博北美站"
  • 2 external scripts, 16 inline; <noscript> absent
  • first words: "微博精彩 热门微博 热门话题 微博会员 微相册 微游戏 微指数 手机玩微博 扫码下载,更多版本 戳这里 认证&合作 申请认证 链接网站 企业微博 广告服务 微博标识 广告代理商 开放平台 微博帮助 常见问题 自助服务 企业&商业热线 4000-980-980 微博客服 客服热线4..."

Fix: Nothing to fix here.

Structured data

0/2 · fail

No JSON-LD, Open Graph incomplete

  • 0 JSON-LD blocks
  • Open Graph: no og:title; no og:description
  • meta description: absent

Fix: add a JSON-LD block (Organization or WebSite, plus Product, FAQPage or Article where relevant); add og:title and og:description so answer engines describe you accurately.

MCP census entry (index.agentexchange.work)

0/2 · fail

Not selling to agents: no census entry, no /mcp endpoint

  • census unavailable (refused index.agentexchange.work: hosts on agentexchange.work cannot be graded from inside the same Cloudflare zone; every check would time )
  • GET /mcp -> HTTP 200 HTML page (catch-all route, not an MCP endpoint)

Fix: Expose a Streamable HTTP MCP endpoint at /mcp (or a paid x402 route) so agents can call you, not just read you.

Share this result

Permanent link; it re-grades the site live when opened:

https://grade.agentexchange.work/grade?url=weibo.com

Public profile with grade history and an embeddable badge: https://grade.agentexchange.work/site/weibo.com (badge: https://grade.agentexchange.work/badge/weibo.com.svg).

$49 AI Visibility Full Report

This grade is free and automated. The paid next step is the $49 AI Visibility Full Report (which brands a representative AI model, standing in for ChatGPT-class assistants, names when buyers ask about your category, with a prioritized fix list) from aivisibility.agentexchange.work, run for weibo.com. It includes:

Get the Full Report — $49 Stripe checkout asks for your brand name and category; the report is ready about 60 seconds after payment. Legal notices and the MCP census entry are not in this report (free: Compliance Desk check, census claim).

Grade another site