May 21, 2026 · AI Search

Chrome WebMCP: The Next Layer of AI Visibility After Schema.org

While everyone was reacting to Google I/O, Chrome quietly published a new specification that could define the next phase of AI-native web. Here's what WebMCP is, how it fits into AI visibility, and what to actually do about it.

Three layers of AI visibility

AI-native web visibility is becoming layered. Each layer tells AI something different about your site:

01
Schema.orgTells AI who you are — your business type, location, contact info, products. The foundation. If you have nothing else, start here.
02
llms.txtTells AI what to read about you — which pages matter, in what order. A structured summary at yoursite.com/llms.txt.
03
WebMCPTells AI what it can do with your site — book, search, fill forms, trigger actions. The new layer Chrome is introducing.

What WebMCP actually is

Today, AI agents that interact with websites do so by interpreting the visual interface — reading text, identifying buttons, guessing what clicking something will do. This works, but it's fragile and slow.

WebMCP proposes a different approach: websites explicitly declare their capabilities to AI agents using JSON Schema. Instead of the agent figuring out how your booking form works, your site tells it: here's the form, here are the fields, here's what happens when it's submitted.

Two implementation paths are available: an imperative JavaScript API for complex interactions, and a declarative HTML annotation approach that automatically creates WebMCP tools from existing forms.

What sites can declare with WebMCP

  • Booking and reservation forms with structured field mapping
  • Product search with filterable parameters
  • Support workflows with escalation paths
  • Multi-step interactions that require user confirmation
  • Backend functions triggered by AI agents on behalf of users

Current status: early, but moving fast

WebMCP is available now for developers behind a Chrome flag (chrome://flags/#enable-webmcp-testing). The Origin Trial — when production websites can participate — is planned for Chrome 149.

The spec is still under active discussion and subject to change. This is not a stable standard yet. But it's moving quickly, and the direction is clear.

What to do right now

The honest answer: nothing, regarding WebMCP specifically. The standard isn't finalized, Chrome 149 isn't out yet, and the implementation details will likely change.

What you should do right now is layer 1 and 2 — the foundations that already affect your visibility in ChatGPT, Gemini, Grok, and Claude today:

  • Schema.org markup. The highest-weight signal in AI citation decisions. If you don't have Organization or LocalBusiness schema, start here.
  • FAQPage schema. Research shows +41% citation rate for pages with proper FAQPage JSON-LD. The single highest-ROI technical change for AI visibility.
  • llms.txt. Tells AI agents which pages to prioritize. Creates a structured entry point for any AI crawling your site.

When WebMCP reaches Chrome 149 and stabilizes, we'll add it as a factor in the Causabi AI visibility score. Until then, it's one to watch.

Check your current AI visibility score

See where you stand on Schema.org, FAQ schema, llms.txt, and the other signals that affect your AI visibility today.

Free AI Readiness Check

See your GEO score before reading

Instant score · No email required · Checks ChatGPT, Gemini, Grok signals

Chrome WebMCP: The Next Layer of AI Visibility After Schema.org | Causabi