wordpress.com
This is how AI agents (not browsers) experience wordpress.com. The score weights five categories of machine-readability; the ticks on the arc are the 31 individual checks behind it.
Top fixes
Checks tagged “emerging” are 2026 agent-protocol standards most of the web hasn’t adopted yet — adopting early is an edge, not a defect.
1 required-field error(s). First: WebSite requires "name".
Fix: Validate your JSON-LD with Google Rich Results test. Fix missing required properties.
No HTTP Link: response headers. Emit canonical/alternate/describedby relations so HEAD-only or stream-rendering agents get them without parsing HTML.
Fix: Emit `Link:` headers for canonical, alternate-language, and describedby relations. Agents that fetch HEAD-only or stream-render rely on these.
Visible text is 1.7% of HTML weight (5864/351224 bytes). Low. Markup may be crowding out agent-usable text.
Fix: Heavy ad or navigation markup crowds out agent-usable text. Aim for a text-to-DOM ratio above 15%.
<html lang="en"> is valid, but 1 hreflang alternate(s) are malformed ("pt-br"). Malformed alternates are ignored by consumers, so those translations are invisible to agents routing users by market.
Fix: Add `lang` to your `<html>` element (`<html lang="en">`, `<html lang="de-DE">`). If you publish translations, declare them with `<link rel="alternate" hreflang="..." href="...">` using BCP 47 tags — language[-Script][-REGION], hyphens not underscores.
No Content-Signal directives. Add e.g. `Content-Signal: ai-train=no, ai-summarize=yes` to declare granular AI usage policy beyond binary allow/disallow.
Fix: Add `Content-Signal:` directives to your robots.txt. This is the emerging standard (Cloudflare-driven) for declaring fine-grained AI usage policy beyond a binary allow/disallow.
No valid MCP Server Card at /.well-known/mcp/server-card.json. Publish one so agents can discover your tools without HTML scraping.
Fix: Publish an MCP Server Card describing the tools your site exposes. Agents discover capabilities via `/.well-known/mcp/server-card.json`. See modelcontextprotocol.io for the schema.
Get it in your inbox now — and a heads-up whenever wordpress.com’s agent-readiness score changes. Free, unsubscribe anytime.
This scan shows whether an agent can read the site. One free probe asks a real assistant a real buying question and records who it cited.
This graded your homepage. Your pricing, docs, and checkout live on other pages — the ones assistants actually quote when they recommend you — and a 74/100 here means agents are already missing things on the page you polish most. The $29 Deep Scan audits the whole site against all 31 checks, then emails a PDF with every failing check and its exact fix, ranked by what costs you the most visibility. One-time, delivered in minutes, no subscription.
Right now, only you know this score. Your buyers ask AI before they buy — certification is how you show them, and anyone comparing you to a competitor, that assistants can actually read, quote, and use your site.
- A public verification URL you can drop into a sales deck, a procurement questionnaire, or a partner review — anyone can check it, dated and signed.
- An embeddable badge for your site — the visible version of a property competitors can’t claim without earning the score.
- Weekly re-checks for a full year. A deploy that breaks agent access gets caught before it costs you recommendations — and before the certificate would lapse.
Sites under 70 can’t buy this at any price — that’s what makes displaying it mean something.
Certify wordpress.com — $199/year →What the agent receives
Show your score
Embed this badge on your site. It links back to this live scan and updates on every rescan.
<a href="https://agentspeed.com/scan/wordpress.com"><img src="https://agentspeed.com/badge/wordpress.com" alt="AgentSpeed agent-readiness score" height="56"></a>Track this score
Get this report by email, then a heads-up when wordpress.com’s agent-readiness actually changes — a check regressing, or the composite dropping.
Two things never trigger an email: a score change caused by us publishing a new rubric, because that is a different instrument rather than a change to your site, and movement explained only by timing-derived checks, which shift run to run on a site nobody touched.
Want it on your own schedule, with Slack or a webhook instead of email? Score-drift monitoring is on every paid plan.
This score says whether an AI agent could read wordpress.com. AI traffic analytics says whether one actually came — and which pages turned it away.
Full breakdown
Running AI agents of your own? AgentSpeed also monitors them in production — every run, its latency, cost, and failures, with alerts when something breaks. Free for 10,000 events a month, no credit card.