Agentic
Browsing
The new PageSpeed score
Run a Google PageSpeed report today and you'll notice something new alongside the familiar Performance, Accessibility, Best Practices and SEO scores: a fifth category called Agentic Browsing. Not a number from 0 to 100, but a simple ratio such as 2/3 or 3/3.
This score measures something fundamentally different from the rest of the report: not how fast or accessible your site is for people, but whether an AI agent — a system acting on a person's behalf, such as shopping, comparing or gathering information — can read, understand and use your page without a human at the wheel.
Ready for AI agents.
Why Google suddenly measures this
Google added the Agentic Browsing category to Lighthouse 13.3 in May 2026, and it now appears in PageSpeed Insights by default. The reason behind it is a shift you've probably already noticed: a growing share of web traffic no longer comes from people clicking around themselves, but from AI systems doing it on their behalf.
According to figures from Adobe, AI traffic to US retail sites grew 393% year over year in the first quarter of 2026. ChatGPT, Perplexity and Google's own Gemini research products, compare prices and complete tasks across multiple websites — and those agents need to be able to understand your pages to do that well.
This ties directly into something we've been emphasising at DYKZ for a while: a website that's easy to find on Google is no longer enough on its own. Findability and usability for AI systems is becoming just as important a part of technical quality.
What exactly
does it check?
What exactly does it check?
The Agentic Browsing score is a pass ratio, not a separate 0–100 number, and 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 site aloud to visually impaired visitors. Do buttons, links and interactive elements have clear, programmatically recognisable names? That's exactly what an AI agent needs to understand what an element does.
2. Layout stability (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 located.
3. The presence and validity of an llms.txt file
A text file at your domain root that gives an overview of your main 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 (such as search or add-to-cart) directly for generative AI agents. PageSpeed Insights usually reports three of these four checks, since WebMCP audits only apply to sites that have actually implemented the protocol — which is why you'll often see "3/3" rather than "4/4".
Is this an official ranking factor?
Not yet. It's experimental and not a confirmed ranking factor, and Google itself still describes the category as "under development" — so the exact checks may still change.
But the direction is clear: Google is building a permanent home for AI readiness inside the tools every developer and SEO specialist already uses daily. Waiting until it becomes an "official" ranking factor isn't a good strategy — by then you'll already be behind.
How do you score 3/3?
The good news: for most well-built websites, the required changes overlap with things you should already be doing — solid accessibility, a stable layout and clean 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 recognisable names. A button with only an icon and no
aria-labelis just as meaningless 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 around as content loads.
- Add an llms.txt file at your domain root with a short, structured overview of your main pages.
Why DYKZ already
scores well here
Why DYKZ already scores well here
At DYKZ, we build with W3C-valid, semantic HTML from the very first line of code — without a CMS, without plugins, without the messy, generic <div> soup that many template-based websites produce. That same principle — clean, meaningful markup that says exactly what each element is and does — happens to be exactly the foundation the Agentic Browsing score relies on.
Accessibility tree
We already build with accessibility and WCAG in mind, so 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 already pay close attention to Cumulative Layout Shift — it's a core part of the Core Web Vitals we optimise for regardless.
- Read more about Google PageSpeed ↗
llms.txt
Adding a simple, static text file fits naturally with our CMS-free approach — no plugin needed, just a file in the right place.
- Read more about findability ↗
In other words: a website built on our philosophy doesn't need a separate "AI-proofing" pass. The quality we already aim for — valid HTML, speed, accessibility — is the same quality an AI agent needs to "read" your site.
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 increasingly process information through agentic browsing rather than through a human clicking and reading by hand. Websites that aren't prepared for this — with messy HTML, shifting layouts or confusing interactive elements — simply become invisible or unreliable to those agents, no matter how good they look to a human visitor.
The Agentic Browsing score is still experimental and will likely keep evolving, but the message behind it is clear: technical quality — clean HTML, stable layouts, accessible interaction — is no longer relevant only to human visitors and classic SEO. It's now also the foundation for how AI agents assess and use your website.
At DYKZ, we build websites that already score strongly on this foundation — not because we optimised specifically for this one score, but because our approach (no CMS, no plugins, 100% W3C-valid semantic HTML) happens to be exactly what both people and AI agents need to use a website well.
Curious how your current website scores on Agentic Browsing? 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 webpage. The score is shown as a ratio, such as 2/3 or 3/3, rather than a number from 0 to 100.
What exactly does it check?
Three default 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 sites that have implemented that protocol.
Is Agentic Browsing an official SEO ranking factor?
Not yet. The category is experimental and Google itself still describes it as under development. It isn't 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 and programmatically recognisable names, prevent unexpected layout shifts by setting image dimensions, 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 containing a short, structured overview of its main pages, specifically intended to help language models and AI crawlers quickly understand a site.
Sources
DYKZ values transparency and clarity. This article was written based on recent, specialist publications about the Agentic Browsing category in Google Lighthouse and PageSpeed Insights. Feel free to get in touch with any questions or feedback.
Get in touch
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.