Agent-ready website toolkit

Best fit

Website owners and small teams

• People who got a low score from a checker and need a roadmap
• Teams that can edit HTML and want a clean first implementation
• Operators who need a practical path before paying for a custom audit

Also useful for

Developers and agencies

• Technical teams building the first agent-readable forms on a site
• Freelancers who want a repeatable implementation flow
• Agencies that want a lower-cost audit starting point

Not a fit

People looking for a scanner or a warranty

• Anyone expecting a certification or a permanent compatibility promise
• Teams looking for a vulnerability scanner or compliance report
• Buyers who want the site done for them with no implementation involvement

WebMCP tools

Expose site actions as tools

Use the annotation templates to make contact, booking, product search, and support flows discoverable to agents without rebuilding the entire site.

• Declarative HTML templates first
• Imperative JavaScript examples for richer flows
• Names and descriptions that agents can actually parse

Readable context

Give agents the missing context

The audit checklist covers llm.txt, schema, robots.txt, and the visible copy around the tool so agents know what the site does before they call it.

• Audit the crawlable surface
• Check schema and robots hygiene
• Keep the tool copy aligned with the page

Chrome 149 testing

Test the current origin-trial surface

The testing instructions walk through Chrome 149 setup, discovery checks, prompt-based verification, and the common mistakes that break tool use.

• Origin-trial setup
• Inspector and discovery checks
• Validation before launch

Audit

Agent-readiness audit checklist

A practical review path from "I ran the checker" to "I know what to fix next." Use it to decide what to annotate, what to rewrite, and what to leave alone.

• See the current gaps
• Prioritize the first fixes
• Map the work before you pay for help

Templates

Declarative API annotation templates

Copy-paste HTML annotation templates for the common website actions the pack targets, with the boring bits explained so the markup stays editable.

• Contact and support forms
• Booking and appointment flows
• Product search and other common actions

Writing

Tool description copywriting guide

Rules and examples for writing tool descriptions that agents can discover and invoke instead of skipping over vague or overstuffed labels.

• Write for discoverability
• Avoid certification language
• Keep the tool intent narrow

Testing

Chrome 149 testing instructions

Step-by-step instructions for enabling the current trial, checking discovery, and confirming that the tool behaves the way the template says it should.

• Flag and origin-trial setup
• Prompt-level validation
• What to check when discovery fails

Launch

Setup walkthrough video script

A scene-by-scene screencast script you can use to ship the pack, train a teammate, or turn the workflow into future sales material.

• Visual walk-through
• Voiceover beats
• Reusable implementation demo

Digital pack

$29

The DIY toolkit itself: templates, checklist, copywriting guide, and Chrome testing instructions.

• Best if you can edit HTML yourself
• Start with the roadmap and the templates
• Downloadable product pack

Implementation audit

$300

A paid review that tells you what to annotate, what to rewrite, and what to test first.

• Site-specific prioritization
• Audit against the current surface
• Clear next-step recommendations

Full implementation

$750-$1,500

Hands-on implementation for teams that want the toolkit applied for them instead of doing it themselves.

• 3-5 forms or flows
• Tool descriptions and schema alignment
• Testing and handoff support

FAQ

What is an agent-ready website?

A site that exposes useful actions and supporting context in a way AI agents can discover and use: WebMCP tools, readable labels, schema, llm.txt, and a testing loop that verifies the result.

FAQ

Is this a certification?

No. This page and toolkit are preparation for the agent-ready web, not a certification or a permanent-compatibility promise. WebMCP is still evolving.

FAQ

Do I need JavaScript to use the toolkit?

Not for the first path. The pack is designed to start with declarative HTML templates. The imperative JavaScript examples are for sites that need richer interactions.

FAQ

Why not just use a free checker?

Because a checker tells you whether your site is ready. It does not give you the template files, the tool-description wording, or the testing instructions needed to actually fix it.

FAQ

What does Chrome 149 testing cover?

How to enable the current trial, verify discovery, exercise the inspector, and catch description or schema mismatches before you publish.

FAQ

What happens if the spec changes?

You still keep the workflow: audit, annotate, write better descriptions, and test again. The current pack is aligned to the origin-trial-era surface, so it is meant to be adapted as the standard evolves.