Agent Readiness Score Explained: How We Calculate It

If you've run a scan on AgentReady, you've seen a single number come back — your Agent Readiness Score (ARS). This post explains exactly what goes into that number: the three pillars we score, why each one matters to an AI agent specifically (not just a search engine), and how to read a low score without guessing at what to fix first.

Why a single score, and why now

Every emerging technology creates its own wave of "readiness" scanners — mobile-friendliness checks, Core Web Vitals, accessibility audits. Each one exists because the underlying shift (mobile traffic, page speed, assistive technology) changed how a meaningful share of visitors actually experienced the web, and site owners needed a fast way to know where they stood.

Browser-based AI agents are the same kind of shift. An agent visiting your site isn't a search engine crawler indexing text for later retrieval, and it isn't a human reading your layout — it's a third kind of visitor with its own requirements: it needs to parse your content efficiently, understand what actions are available, and act on the page reliably. A site can rank perfectly in Google and still be effectively unusable to an agent trying to complete a task on it. The Agent Readiness Score exists to measure that gap directly.

The three pillars

Your overall score is a weighted average of three pillars: Browser Readiness (40%), Agentic Orchestration (40%) and MCP Presence (20%). Each pillar is scored 0–100 on its own, then combined. When a scan covers several pages, each page is scored and the results are averaged.

1. Browser Readiness (40%)

This pillar measures how usable a page is for an agent working in the browser. It is itself a blend of five signals:

Interactive readiness (30%) — whether your forms declare WebMCP tools (toolname, tooldescription, auto-submit), and how well-written the tool descriptions are
Technical accessibility (20%) — ARIA roles and landmark elements
Semantic density (20%) — JSON-LD structured data and Open Graph metadata
Tool discoverability (20%) — named form tools, plus agent skills, MCP server card, A2A agent card and API catalog files
Content structure (10%) — an h1 and a sensible heading hierarchy

WebMCP is still an early-preview technology, so most sites score low on the interactive part today. It is also where the fastest competitive advantage is available.

2. Agentic Orchestration (40%)

This pillar checks whether an agent can work with your data through a public API instead of scraping pages:

A published OpenAPI/Swagger spec (the biggest single factor)
A link to developer documentation
An API catalog or API link, and rate-limit signals

3. MCP Presence (20%)

A simple check: does your site advertise a Model Context Protocol server that agents can discover and connect to? It is either present (100) or absent (0).

Reading your results

A score in the 80s or 90s means an agent can reliably find, parse, and (where applicable) act on your site's content today. A score in the 40s or 50s usually means some Browser Readiness basics are in place but there is no API surface or MCP server — this is the most common range for established sites that have invested in traditional SEO but haven't yet built for agents specifically. A score below that typically means few agent-facing signals of any kind: no WebMCP tools, no API spec and no MCP server.

Every scan returns prioritized, per-check recommendations rather than just the composite number, specifically so a low score comes with a concrete next step instead of a grade with no path forward.

Run it on your own site

Scores shift as standards evolve and as your site changes — a redesign that drops structured data, a new page shipped without semantic markup, will move your number even if nothing else about your agent-readiness strategy changed. Run a free scan at AgentReady to see where your site currently stands across all three pillars, and track your score over time as you make changes.