Is Your Site Agent-Ready? The Lighthouse Agentic-Browsing Audit and How to Pass It

AI agents are starting to do things on websites, not just read them: search a catalog, fill a form, book a slot, add to a cart. And as of May 2026, Google ships a way to measure whether your site is ready for them. It is a new category in Lighthouse called Agentic Browsing, and it quietly grades how usable your pages are to an automated agent. If you have wondered "is my site agent-ready, and how would I even know," this is the answer: what the audit checks, how to pass each part, and how much of it actually matters yet.

🤖 What "agent-ready" actually means

An agent-ready page is one an AI agent can understand and operate without guessing. A human looks at your page and infers what the "Buy" button does and which field is the email. An agent cannot rely on that visual intuition reliably. It needs the meaning to be declared: clear labels, declared actions, a stable layout it can target. Lighthouse's Agentic Browsing category is Google's first attempt to score exactly that, and it landed in Lighthouse 13.3 in May 2026.

Worth being honest up front: this is a Chrome and web-platform initiative, not a Search ranking system. That is why you get the slightly confusing situation where Google Search says you do not need llms.txt, while Google's own Lighthouse checks for it. Different teams, different goals. It is a little WTF when you first see it, and the confusion is on them, not you. The resolution: the audit is about agent usability, not rankings.

✅ The four checks, and how to pass each one

1. llms.txt: discoverability

Lighthouse checks whether your domain root serves an llms.txt, a Markdown summary that points an agent at your key content. How to pass: publish a valid /llms.txt. The honest caveat: Google Search's own May 2026 AI optimization guide says llms.txt is not needed for AI Overviews or AI Mode, and the major AI crawlers largely ignore it for content. Lighthouse measures it anyway, for agent discovery. So pass the check if you like, but do not expect search visibility from it. The full story is in our llms.txt explainer.

2. WebMCP: declared actions

The audit looks for forms that are not declared through WebMCP and flags them, because an undeclared form is a black box to an agent: it has to guess what the fields mean. If you do declare tools, Lighthouse validates the input schema and fails it if the schema is invalid. How to pass: expose your key forms and actions with WebMCP, starting with the lightweight declarative form attributes, and make sure any input schemas are valid. This is the newest and highest-effort check. Details and code are in our WebMCP explainer.

3. Accessibility tree: the machine-eye view

This is the one to care about most, and it is not new. Agents use the accessibility tree as their primary model of your page, the same structure screen readers use. Lighthouse checks that interactive elements have programmatic names and labels, that the tree is valid, and that interactive content is not hidden from assistive systems. How to pass: use semantic HTML (real button, label, nav elements), give every control an accessible name, and add ARIA only where semantics fall short. The bonus: this is plain good accessibility, so it helps humans and screen readers too. It is the same idea as our Forgotten HTML thesis: machines act on the structured layer, not the pixels.

4. Layout stability (CLS): stay still

Agents need stable DOM positions to click reliably. If your layout shifts while content loads, an agent can click the wrong thing, and it fails silently. Lighthouse reuses Cumulative Layout Shift here. How to pass: reserve space for images and embeds, avoid inserting content above existing content, and keep CLS low. If you have already done Core Web Vitals work, you are most of the way there.

🏛️ Who is behind it, and what that signals

The Agentic Browsing category comes from Google's Chrome and Lighthouse team, and it builds on standards being developed in the open: WebMCP at the W3C, the accessibility tree as a long-standing web standard, and llms.txt as a grassroots proposal. That mix matters. The accessibility and CLS parts rest on mature, stable foundations, so investing there is safe regardless of how the agentic web shakes out. The WebMCP and llms.txt parts are newer and still moving, so treat them as forward bets, not settled requirements. Google itself underlines this by refusing to give the category a single score and labeling it experimental, with the note that the standards for the agentic web are still emerging. That is a healthy signal: even the vendor is telling you not to over-commit yet.

🔎 Does passing this help your SEO?

Directly, no. Google Search has stated that none of these signals affect your rankings, and the Lighthouse category produces no ranking-relevant score. So if someone is selling "pass the agentic audit to rank higher," that is the BS to walk past. What it genuinely affects is whether an AI agent can complete a task on your site, which is a conversion and future-readiness question, not a discovery one. The honest framing is the same one that applies across this whole space: search and AI answers help agents find you, agent-readiness helps them finish the job once they arrive.

⚖️ Should you invest now? Pros and cons

🧭 Who benefits most

Most: transactional sites where an agent completing a task equals revenue, ecommerce, travel, booking, SaaS, local services. For them, agent-readiness is a real competitive edge as agentic shopping grows. Least, for now: purely informational and content sites. Your value is being read and cited, which lives in the content and entity layers, so focus the agentic work on the accessibility tree and CLS and skip the heavy WebMCP build until you have a reason.

🛠️ How to make your site agent-ready, step by step

1. Run the audit. Open Lighthouse in Chrome (the Agentic Browsing category is in 13.3 and later) and see which of the four checks you fail.
2. Fix the accessibility tree first. Highest leverage, helps everyone. Semantic HTML, an accessible name on every control, ARIA only where needed.
3. Tame layout shift. Reserve space for media, avoid late-injected content. Reuse any Core Web Vitals work.
4. Add llms.txt if agents or developer docs matter to you. Low effort, useful for agent discovery, not for rankings.
5. Pilot WebMCP on your top one or two actions. Start with the declarative form attributes, validate the schemas, and expand only if it earns its keep.
6. Re-run and re-check. Treat it as a living target, since the category is still evolving.

❓ Agent-readiness FAQ