Chrome describes how to prepare a site for agents

On June 22, 2026, the Chrome developer blog published a post about a toolkit for sites that are ready to work with agents. It is the first coherent explanation from the browser team of what it means by such readiness.

What is in the toolkit

• The Agentic Browsing category in Lighthouse. Checks of whether an agent can work with a page.
• WebMCP. A proposed standard by which a site describes the actions available to an agent.
• Chrome DevTools for agents. Debugging tools that an agent can use.

What the checks look at

The post names three areas: accessibility, layout stability and the WebMCP connection.

The main idea is about accessibility. An agent in the browser reads a page through the accessibility tree, the same structure that screen readers use. A button without a name is invisible to both.

The category is called informational: it shows pass, fail and warnings, but gives no overall score.

What the post does not contain

It does not mention llms.txt. The file check exists in Lighthouse, but when the Chrome team describes preparing a site, it talks about something else: the markup of a page and its behavior.

That is a useful correction to the talk about the file. For an agent that acts in a browser, a clear page matters more than a site map.

What a site owner should do

Start with what also helps people: names on buttons and fields, headings in order, a layout that does not jump. The layers of preparing a site in order: A site ready for AI. What exactly Lighthouse checks about the file: Lighthouse and llms.txt.