WHAT IS AGENTIC BROWSING.
New metric in Google PageSpeed.
The new PageSpeed score
Run a Google PageSpeed report these days, and since June 2026 you'll see a fifth category alongside the familiar Performance, Accessibility, Best Practices and SEO scores, called Agentic Browsing. Not a number between 0 and 100, but a simple ratio like 2/3 or 3/3.
This score measures something fundamentally different from the rest of the report. Not how fast or accessible your website is for people. It measures whether an AI agent can read, understand and use your page well, without a human at the wheel.
DYKZ builds maintenance-free websites with maximum Google PageSpeed scores. Good for usability and discoverability.
Ready for AI agents.
Why Google measures this
Google added the Agentic Browsing category to Lighthouse 13.3 in May 2026. It now appears by default in Google PageSpeed Insights. The reason behind it is a shift you've probably already felt coming. A growing share of web traffic no longer consists of people clicking themselves, but of AI systems doing it on their behalf.
According to Adobe figures, AI traffic to US retail websites grew 393% year-over-year in the first quarter of 2026. ChatGPT, Perplexity, and Google's own Gemini research products, compare prices, and carry out tasks across multiple websites. Those agents need to be able to make sense of your pages to do that well.
This fits directly with something we've been emphasizing at DYKZ for a while: a website that's easy to find for Google is no longer enough these days. Discoverability and usability for AI systems, also known as Generative Engine Optimization (GEO), has become an equally important part of technical quality.
3/3 metric
What exactly gets checked?
The Agentic Browsing score is a pass ratio. Not a separate 0-to-100 number. It consists of a small number of concrete, deterministic checks.
1. The integrity of your accessibility tree
The same structure screen readers use to read your website aloud to visually impaired visitors. Do buttons, links, and interactive elements have clear, programmatically recognizable names? That's exactly what an AI agent needs too, to understand what an element does.
2. Layout stability (CLS, or Cumulative Layout Shift)
Does your page stay visually still while an agent reads through it, or do elements jump around? An unstable layout makes it harder for an automated system to reliably determine where something is.
3. The presence and validity of an llms.txt file
A text file at your domain root that gives an overview of your most important pages and what they're about. Specifically intended for language models and AI crawlers.
There's also a fourth, optional check for WebMCP integration, an experimental protocol that lets developers register interactive forms and functionality (like search or add-to-cart) directly for generative AI agents. PageSpeed Insights typically reports three of these four checks. Because WebMCP audits only apply to websites that have actually implemented that protocol, a good result often shows "3/3" instead of "4/4."
Is this an official ranking factor?
No. Not yet. It's experimental and not a confirmed ranking factor. Google itself currently still calls the category "under development." So the exact checks may still change.
But the direction is clear. Google is building a permanent place for AI readiness into the tools every developer and SEO specialist already uses, or should be using, daily. Waiting until it becomes an "official" ranking factor is therefore not a good strategy. By then you'll be playing catch-up.
How do you score 3/3?
The good news: for most well-built websites, the changes needed already overlap with things you should be doing anyway. Think good accessibility, a stable layout, and clean, well-structured HTML.
- Use semantic HTML elements instead of generic
<div>s for everything. A button should be a<button>, a link an<a>, navigation a<nav>. - Give interactive elements explicit, programmatically recognizable names. A button with only an icon and no
aria-labelis just as incomprehensible to an AI agent as it is to a screen reader user. - Define explicit width and height for images and banners, so the page doesn't jump and shift as content loads.
- Place a good llms.txt file at your domain root with a short, structured overview of your most important pages.
DYKZ scores well
Why DYKZ naturally scores well here
At DYKZ we've been building from the very first line of code with W3C-valid, semantic HTML for years. Without a CMS, without plugins, without the messy, generic <div> soup that a lot of template-based websites simply produce. That same principle, clean, meaningful markup that says exactly what each element is and does, is precisely the foundation the Agentic Browsing score relies on.
Accessibility tree
We already build with accessibility and WCAG in mind. Buttons, links, and form elements on DYKZ websites already have clear, programmatic names.
Layout stability
Our focus on maximum Google PageSpeed scores (95 to 100) means we pay close attention to CLS, or Cumulative Layout Shift. A core part of the Core Web Vitals we optimize for anyway.
- Read more about Google PageSpeed ↗
llms.txt
Adding a simple, static text file fits seamlessly with our approach, no CMS or plugin needed. Just the right llms file in the right place.
- Read more about our approach as an SEO specialist ↗
In other words: a website built according to our philosophy doesn't need to be made "AI proof" separately. The quality we already pursue, W3C-valid HTML, speed, and accessibility, is the same quality an AI agent needs to be able to "read" your website well.
The conclusion
More than a hype
It's tempting to dismiss new Lighthouse categories as a marketing gimmick, but the underlying shift is real. Search engines and AI systems alike are increasingly processing information through agentic browsing rather than through a human manually clicking and reading.
Websites that aren't prepared for that, with messy or broken HTML, inconsistent layouts, or incomprehensible interactive elements, simply become invisible or unreliable to those agents. Regardless of how good the website looks to a human visitor.
The Agentic Browsing score is still experimental right now (September 2026) and will likely keep changing, but the message behind it is clear. Technical quality, clean HTML, stable layouts, and accessible interaction are no longer relevant only to human visitors and classic SEO. It's now also the foundation for how AI agents evaluate and use your website.
At DYKZ we build websites that already score strongly on that foundation by default. Not because we optimized specifically for this one score. Our approach (no CMS, no plugins, 100% W3C-valid semantic HTML) is exactly what both people and AI agents need to genuinely use a website well.
Curious how your current website scores on Agentic Browsing or usability? Feel free to get in touch.
Frequently asked questions
Frequently asked questions
Open and transparent
What is the Agentic Browsing score?
A category in Google Lighthouse and PageSpeed Insights that measures how well an AI agent can read, understand, and use a web page. The score is shown as a ratio, such as 2/3 or 3/3.
What exactly gets checked?
Three standard checks: the integrity of the accessibility tree, layout stability (Cumulative Layout Shift), and the presence of a valid llms.txt file. An optional fourth check covers WebMCP integration, which only applies to websites that have implemented that protocol.
Is Agentic Browsing an official SEO ranking factor?
No. Not yet. The category is experimental and Google itself still calls it under development. It's not a confirmed ranking factor, but it is a signal that AI readiness is being taken increasingly seriously in Google's tools.
How do I score 3/3 on Agentic Browsing?
Use semantic HTML elements, give interactive elements explicit, programmatically recognizable names, prevent unexpected layout shifts by setting fixed dimensions for images, and place a valid llms.txt file at your domain root.
What is an llms.txt file?
A simple text file at a website's domain root with a short, structured overview of its most important pages, specifically meant to help language models and AI crawlers quickly understand a website.
Sources
DYKZ® is a registered trademark and values transparency and sharing knowledge and sources. This article was written based on recent, specialized publications about the Agentic Browsing category in Google Lighthouse and PageSpeed Insights. For questions or feedback, feel free to get in touch.
Contact us
Ready for
AI agents?
Want to know how your website scores on speed, accessibility, and Agentic Browsing? Get in touch for a no-obligation consultation.
