The Agent-Readiness Check

The Agent-Readiness Check: where your site stands, in ten minutes
An Ena Pragma method. No tools to install; one browser tab.

PART 1: THE NEUTRAL YARDSTICK (2 minutes)
Run your homepage through Cloudflare's Agent Readiness Score at
isitagentready.com (also built into the Cloudflare URL Scanner). It grades
the machine-facing basics: structure, markup, crawlability. Save the number
and the category breakdown. This is your baseline, not your grade; the
most-visited sites on the web score poorly today too.

PART 2: THE FORM SELF-CHECK (8 minutes)
Open your most important form (contact, quote, booking) and check five
things. These decide whether TODAY'S agents can use it (they parse the
accessibility tree, like a screen reader) and whether TOMORROW'S tool
layer could be derived from it automatically.

1. Every input has a visible <label> tied to it (click the label text;
   the field should focus). Placeholder text alone fails.
2. Input types are real: type=email for emails, type=tel for phones,
   a <select> with named options instead of free text where choices are
   fixed. Typed inputs become typed schema.
3. Required fields carry the required attribute, not just an asterisk
   in the label.
4. The submit button says what it does ("Request a quote"), not
   "Submit."
5. Fill it with a keyboard only, no mouse. If you cannot complete it,
   neither can most agents; accessibility quality bounds agent success.

Each fix is ordinary web work. It improves conversion and accessibility
for humans now, and it is the exact substrate the WebMCP declarative
layer compiles into agent tools later. Nothing here is wasted if the
spec changes.

PART 3: THE TRIGGER WATCHLIST (re-check quarterly)
Do not follow the news cycle; check three conditions:
- Has a non-Google agent (ChatGPT, Claude, Perplexity) announced it
  consumes WebMCP site tools? (Search their changelogs.)
- Has Chrome posted an Intent to Ship for WebMCP, or has the feature
  shipped past the Chrome 149-156 origin trial?
  (chromestatus.com/feature/5117755740913664)
- Has the spec's consent/security model moved from TODO to normative
  text, has WebKit's oppose position softened, or has Mozilla taken a
  position? (github.com/WebKit/standards-positions/issues/670,
  github.com/mozilla/standards-positions/issues/1412)

Zero of three: keep the free rungs current, spend nothing else.
One of three: scope the tool layer (1-2 days on a modern site) for the
areas where an agent completing a task helps you (booking, quoting).
Two or more: put it on the roadmap with the same governance you would
demand of any automation: human confirmation for state changes, and an
audit record of every agent action.