Is your site agent-ready? →
Spoke · Agentic Browsing

The Three WebMCP Lighthouse Audits (and How to Pass Them)

Inside Google's agentic browsing category sit three WebMCP audits. Here is what registered-tools, form-coverage, and schema-validity actually check — and why they are Not Applicable until you adopt WebMCP.

Vijay Vasu May 29, 2026 6 min read
Definition

What Are the WebMCP Lighthouse Audits?


The WebMCP audits are the part of Lighthouse's agentic browsing category that check whether your site exposes its tools to AI agents through the navigator.modelContext API. There are three of them, and they only apply once you have adopted WebMCP — until then, Lighthouse marks them Not Applicable and they do not affect your pass-ratio[1].

If you want the full picture of the category they live in, start with the Lighthouse Agentic Browsing guide.

The Audits

The Three WebMCP Audits


Lighthouse monitors tool registration via the Chrome DevTools Protocol, covering both declarative (HTML-defined) and imperative (JavaScript-defined) tools.

AuditWhat it checksStatus type
webmcp-registered-toolsInventory of WebMCP tools your page exposesInformational
webmcp-form-coverageForms missing declarative WebMCP attributes (toolname + tooldescription)Informational (likely to become a warning)
webmcp-schema-validityFails on asymmetric tool attributes, inputs without a name, and missing toolparamdescriptionCan FAIL
How to Pass

How Do You Pass the WebMCP Audits?


Three steps clear all three audits:

  • Register your tools. Call navigator.modelContext.register() for each capability you want agents to use, or declare tools in HTML with toolname and tooldescription.
  • Cover your key forms. Add declarative WebMCP attributes to high-intent forms — quote requests, search, sign-up.
  • Validate every schema. Give each input a name, every parameter a toolparamdescription, and keep tool attributes symmetric. This is the only one of the three that can fail outright.

For the standard itself, the API, and what to ship first, see the deep dive: WebMCP: The W3C Standard That Makes Your Website Agent-Ready.

Indexable's Technical SEO Agent Fixes This Automatically

The Technical SEO Agent audits every template against Google's agentic browsing checks and hands engineering a line-level fix sheet — CLS, accessibility tree, llms.txt, and WebMCP.

FAQ

Frequently Asked Questions


Do the WebMCP audits lower my score if I have not adopted WebMCP?

No. Lighthouse marks all three as Not Applicable when no WebMCP is detected, so they are excluded from your pass-ratio. You can still score 3/3 on the applicable stability and accessibility audits.

Which WebMCP audit can actually fail?

Only webmcp-schema-validity emits a failure. It fails on asymmetric tool attributes, inputs without a name, and missing toolparamdescription. The other two are informational.

VV

Vijay Vasu

Founder & Chief AI Officer, Indexable AI

Vijay leads Indexable AI, which builds AI SEO Agents and AI-optimized websites for brands running $1B+ in revenue. He was the first SEO hire at Uber Eats and has led SEO at Zendesk and Williams-Sonoma. He writes on the operator's lens of the agentic web.

Ship an Agent-Ready Site

Most Sites Pass 1 of 3 Agentic Checks. Yours Could Pass All Three.

Indexable's ten-agent system audits agentic browsing readiness across every template, fixes the gaps, and monitors your score as the standard evolves.

Sources

Primary Sources Cited


  1. Google / Chrome Developers. Lighthouse Agentic Browsing scoring documentation. Published May 5, 2026. developer.chrome.com/docs/lighthouse/agentic-browsing/scoring
  2. W3C Web Machine Learning Community Group. WebMCP (navigator.modelContext) draft. webmcp.link
Copied ✓