WebMCP Readiness Checklist: 14 Things to Do Before the Full Rollout

Fourteen concrete checkpoints between "never heard of WebMCP" and "agent-ready." Most teams can knock out the first ten in a single sprint.

WebMCP hits Chrome Stable in mid-2026 (confirmed by Google at I/O 2026). If you wait for the stable launch to start, you'll be shipping alongside your competitors who have already been testing in Canary for six months. This is the shortest useful checklist to get ahead.

Phase 1 — Discoverability (1 hour)

1. Allow AI crawlers in robots.txt. Explicitly allow GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot, Googlebot, and GoogleOther. Blocking them is the most common reason a site disappears from AI answers.
2. Publish llms.txt at the domain root. Follow the llmstxt.org spec: H1 title, blockquote summary, H2 sections with linked resources. See ours as a reference.
3. Add Organization schema with sameAs. Link every social profile the site operates — agents use sameAs to verify entity identity when citing.

Phase 2 — HTML semantics (2-4 hours)

4. Clean up non-semantic markup. Replace <div class="btn"> with <button>, <div class="link"> with <a>. Agents lean on semantic tags for intent inference.
5. Ensure every form has name attributes on every input. No name="", no unnamed inputs. Agents use the name as the parameter key.
6. Add required and type attributes correctly. A required email field should be type="email" required, not type="text".

Phase 3 — Declarative API (1-2 hours)

7. Pick your top 3 conversion forms. Signup, contact, checkout, search — whatever drives revenue.
8. Add toolname and tooldescription. camelCase name, natural-language description of when to use the form. See the implementation guide for examples.
9. Test in Chrome Canary. Enable chrome://flags#webmcp, open DevTools → Application → WebMCP, confirm your tools are visible.

Phase 4 — Manifest and Imperative API (half day)

10. Publish /.well-known/webmcp. Serve it with Content-Type: application/json, list your declared tools, include a version field.
11. Register dynamic tools via navigator.modelContext. Anything that isn't a form (modal, stepper, React drawer) needs the Imperative API.
12. Call provideContext() on route changes. Helps agents disambiguate "which product is the user on?"

Phase 5 — Analytics and auditability (1-2 hours)

13. Log SubmitEvent.agentInvoked. Tag every form submission in your analytics stack as agent vs human. Over 2026 this becomes a core business metric.
14. Set up agent-specific alerts. Unusual agent traffic patterns (sudden volume spike, same tool called by many distinct users) are early warning signals for abuse or misconfiguration.

Optional but recommended

• Ship a polyfill. @mcp-b/global brings WebMCP to non-Canary browsers immediately.
• Author bylines on all content. E-E-A-T signals help both traditional SEO and AI citation.
• Add FAQPage schema to every page with three or more Q&A pairs. LLMs cite FAQPage-structured answers disproportionately often.

Time budget for a typical team

A small team (1 engineer, 1 marketer) can complete the first 10 items in about 6-8 hours spread across a sprint. Phases 4 and 5 add another day. Everything else (content restructure, analytics overhaul) is ongoing.

If you want a score-based summary of where you stand, run the free WebMCP audit. It evaluates all 14 items and tells you which ones are failing. For strategy, start with AEO.

Frequently Asked Questions