AI models are becoming how people find things. If your site cannot be parsed by LLMs and autonomous agents, you are invisible to the next generation of search. Here is what we know so far, based on Google recommendations and the new Lighthouse Agentic Browsing audits.
For twenty years, website optimization meant one thing: rank higher on Google. You optimized keywords, built backlinks, and chased Core Web Vitals. That model is being remodeled.
People are no longer typing queries into a search box and clicking through results. They are asking ChatGPT, Gemini, and Claude to find products, compare services, and complete tasks. These AI models do not browse your site like humans do. They read it through screenshots, raw HTML, and the accessibility tree. If your site is not structured for machine consumption, the model cannot recommend it.
Google recognized this shift in May 2026 with Lighthouse 13.3, introducing the Agentic Browsing category. It is a new set of automated checks that evaluate whether your website is constructed for machine interaction. Not as a 0 to 100 score, but as a pass ratio: how many of the applicable AI-readiness checks does your site actually pass.
The same practices that make your site readable to AI models also make it more accessible to humans. Semantic HTML, stable layouts, clean structure. The incentives finally align.
AI agents do not look at your site on a monitor. They operate on machine-readable representations. The quality of these representations determines whether your site gets recommended or ignored. This is based on Google web.dev guidance on how agents interpret web content.
The agent captures a visual snapshot and uses a vision model to identify elements. Color, size, and proximity signal importance. A large Delete button gets more caution than a small Help link. But screenshot analysis is slow and token-expensive, making it a fallback when structure is unclear.
The agent parses the DOM directly, reading element nesting, IDs, classes, and data attributes. A Buy Now button inside a product container is understood to belong to that product. Clean semantic HTML gives the agent a clear structural map of your content hierarchy.
The browser distills the DOM into roles, names, and states of interactive elements. It is a high-fidelity semantic map that ignores CSS noise and focuses on pure utility. AI agents use this as their primary data model for navigation and interaction.
For the last few years, page speed was primarily a ranking signal and a human UX concern. With AI search, it becomes something else entirely: a resource constraint.
AI agents operate on a limited token budget per session. Every byte of HTML, every delayed server response, every unnecessary script consumes part of that budget. A page with a 200ms TTFB lets the agent start parsing immediately. A page with a 3-second TTFB forces the agent to wait before it can even begin reading your content. By the time it finishes, it may have burned through enough of its token budget that downstream pages never get evaluated.
Slow response times and bloated payloads do not just frustrate human visitors. They make your site economically unviable for an AI agent to process at scale. Fast TTFB, lean HTML, and minimal blocking resources are no longer just performance best practices. They are discoverability signals.
notiduck tracks TTFB from three geographic locations every 5 minutes. If your server response time regresses, you will know before an AI agent decides your site is too expensive to read.
Lighthouse has always been a website quality testing tool, covering performance, accessibility, SEO, and best practices. Version 13.3 added a fifth category: Agentic Browsing.
Unlike other Lighthouse categories, Agentic Browsing does not produce a weighted 0 to 100 score. Because the standards for the agentic web are still emerging, the current focus is on gathering data and providing actionable signals. The report displays a fractional pass ratio showing how many AI-readiness checks your site passes, along with specific pass or fail statuses for individual audits.
Source: Chrome for Developers, Lighthouse agentic browsing scoring
Actionable steps based on Google web.dev recommendations and the Lighthouse Agentic Browsing audit spec. None of this is guaranteed to improve your AI discoverability, but it is the best guidance available today.
Place a file named llms.txt at your domain root. It should contain an H1 heading, a concise description of what your site offers, and links to your most important pages. AI models use this file to quickly understand your site without parsing the full HTML. Keep it focused and updated. Lighthouse checks that the file exists, has an H1, is not too short, and contains links.
Prefer <button> and <a> tags over styled <div> elements. Agents recognize semantic elements as interactive. If you must use divs, add appropriate role and tabindex attributes. Set cursor: pointer in CSS as an actionability signal.
Every interactive element needs a programmatic name. Use aria-label where text labels are insufficient. Link <label> tags to inputs with the for attribute. Avoid ghost elements or transparent overlays that hide interactive content from the accessibility tree. Lighthouse validates tree integrity as part of the agentic audit.
Agents that take screenshots get confused when content shifts between the time they identify an element and the time they attempt to interact with it. Set explicit dimensions on images and embeds. Avoid injecting content above existing elements. Reduce cumulative layout shift not just for Core Web Vitals, but for agent reliability. This audit reuses the existing CLS score.
WebMCP is a proposed standard that lets websites expose their functionality to AI agents. You can annotate HTML forms declaratively so agents understand what each field does, or register tools programmatically via navigator.modelContext.registerTool. This is still experimental and in early preview, but early adopters will have an advantage as the standard matures. Lighthouse validates WebMCP schema correctness when present.
notiduck runs the Google Lighthouse Agentic Browsing test automatically as part of every audit cycle. You get a pass ratio displayed on your dashboard, trend history showing how your score changes, and alerts when your AI readiness regresses. Because the number of applicable checks varies per site, we show it as a fraction like 3 out of 3, not a percentage.
An AI-friendly website is structured so that AI models, LLMs, and autonomous agents can easily discover, understand, and interact with its content. This means providing machine-readable files like llms.txt, using semantic HTML, maintaining a clean accessibility tree, and implementing stable layouts that do not shift during loading.
Add an llms.txt file at your domain root with an H1 heading, a summary of your site, and key links. Use semantic HTML elements like button and a tags instead of divs. Ensure every interactive element has a programmatic name in the accessibility tree. Reduce cumulative layout shift. Consider implementing WebMCP to expose your site logic to AI agents.
It is a new experimental category in Lighthouse 13.3 that evaluates how well a website is constructed for machine interaction. It checks for llms.txt presence, WebMCP integration, accessibility tree integrity, and layout stability. The score is displayed as a pass ratio like 3 out of 3 rather than a 0 to 100 score.
llms.txt is a proposed standard file placed at the root of a domain that provides AI models and crawlers with a concise, machine-readable summary of what a website offers. It should include an H1 heading, a brief description of the site, and links to key pages. AI models use this file to quickly understand your site without parsing the full HTML.
WebMCP is a proposed web standard that lets websites expose their functionality to AI agents through a machine-readable API. It allows agents to discover and execute actions on your site, such as filling forms, searching, or completing transactions. It can be implemented declaratively through HTML form annotations or programmatically via the navigator.modelContext.registerTool API.
Yes. Everything that makes a website agent-friendly also makes it better for humans. Semantic HTML improves screen reader accessibility. Stable layouts reduce visual confusion. Clean accessibility trees help all assistive technologies. The practices overlap almost entirely.
The sites that show up in AI model recommendations will be the ones that are machine-readable, structurally clean, and agent-accessible. notiduck monitors your AI readiness alongside performance, so you never fall behind.
Get started for free