Understand how AI agents evaluate your business

The Agent
Readiness Platform

Measure, benchmark, and improve how AI agents find and act on your website.

Accessibility tree/Schema/Booking flows/Agent discovery/WebMCP

Based on Google's agent-friendly guidance, WCAG, Schema.org, the Model Context Protocol, and WebMCP. Built for agencies, SEOs, and local businesses preparing for AI search.

Reading your site like an agent
fetching your page…
example-hvac.com — report
Agent readiness score
72/100
Above average · top 28% of local sites
Your score72
Typical HVAC site38
Top 10%84
Accessibility treepass
Schema markuppass
Booking workflowfail
Agent discoverywarn
01
Scan
Enter your domain. We read your homepage the way an agent does, in seconds.
02
Score
A 0–100 agent-readiness score across all five categories, with benchmarks.
03
Fix
Take the free fix list to your developer, grab the $49 kit, or have us implement it.

How an agent reads your site

Agents don't experience your design. They read the structure under it. We grade what decides whether an agent can find your site, understand it, and get something done.

01

Accessibility tree

Do agents know what's clickable? Real buttons and links instead of styled divs. These are Google's seven agent-friendly rules.

02

Forms & semantic HTML

Labeled fields, real submit buttons, required attributes. Without them, an agent can't fill out your form.

03

Structure & schema

Heading hierarchy, landmarks, and JSON-LD so agents parse your services, hours, and ratings.

04

Booking & pricing

Online scheduling, and prices an agent can read. "Call us" is a dead end.

05

Agent discovery

llms.txt, AI crawler rules, markdown access, and WebMCP-readiness for what's coming next.

+

Done for you

The scan shows the problems. We can implement every fix and keep you current as the standards move.

What that looks like in practice, with one button built two ways:

What a person seesWhat an agent reads
Book now
<div onclick="…">generic · no name, agent skips it
Book now
<button>Book now</button>button "Book now" · agent can act
Identical to a person. Opposite to an agent. The markup is the only difference.

Your GBP is agent-ready. Your website probably isn't.

Google spent years pushing you to fill out every field of your Business Profile: services, hours, booking, reviews. That data was meant for humans. Now it does a second job: it's what AI agents read. Your GBP is agent-ready by accident.

Your website is the gap. Unlabeled contact forms, "call us" instead of real booking, services buried in paragraphs, divs dressed up as buttons. An agent lands, can't read your services, can't check availability, can't book, and leaves for a competitor whose site works. UC Berkeley found agent task success falls from 78% to 42% on poorly structured pages. For years that was a screen-reader statistic businesses ignored. Now it's lost revenue.

The fix is the accessibility and structured-data work the industry has recommended for twenty years. The only thing that changed is the business case. Read the full guide →

Being agent-ready has two halves: getting found by agents, and being usable once they arrive. You need both.

Guides to getting agent-ready

Plain-English explainers. What each thing is, why agents care, how to fix it.