The hidden version of your website that AI actually reads
There is a version of your website you have never looked at, and it is the one that decides whether an AI can use your site or not.
It is called the accessibility tree. It has existed for twenty years, quietly powering screen readers for blind and partially sighted users. Almost nobody in marketing has ever thought about it. And in April, Google published a developer guide that made it suddenly, unexpectedly commercial.
Here is why it matters, and how to look at yours in about thirty seconds.
What Google actually said
The guide is called Build agent-friendly websites, and it opens with a line worth reading twice:
“Many of our websites are designed to be beautiful for humans, with complex hover-states, shifting layouts, and fluid motion. This is functionally broken for agents.”
Functionally broken. Google’s words, about a great many perfectly nice-looking websites.
The guide explains that AI agents view your site in three ways: by taking screenshots, by reading the raw HTML, and by reading the accessibility tree. Google describes that tree as the page’s semantic summary, and says that for an agent it works as “a high-fidelity map that ignores the visual noise of CSS to focus on pure utility.”
In plain English: it is a stripped-back version of your page that describes what everything is and what it does, with all the styling thrown away. No colours, no layout, no hero image. Just structure and meaning.
That is the version an AI is working from.
Why this is suddenly about money
For twenty years, accessibility was treated by most businesses as either a legal obligation or a decent thing to do. Both true, and neither has ever got it onto a marketing budget.
That has changed, because a new visitor arrived. AI agents that book the appointment, compare the prices, fill in the form, and increasingly complete the purchase on somebody’s behalf. And they read your site the same way a screen reader does.
There is now research putting a number on it. A study presented at CHI 2026 by UC Berkeley and the University of Michigan measured how often AI agents could successfully complete tasks on websites. On accessible sites, 78%. On inaccessible ones, 42%.
That is a 36-point gap, based entirely on how the site was built. Not on the copy, the offer, or the price. On whether a machine could work out what the buttons did.
Check yours in thirty seconds
You do not need a developer for this bit. Open your website in Chrome and:
- Right click anywhere on the page and choose Inspect
- In the panel that opens, find the Accessibility tab (it may be hiding under the double arrow, next to Elements and Console)
- Tick Enable full-page accessibility tree
- Click the little accessibility icon that appears in the Elements toolbar
You will now see your page as a structured outline rather than a design.
What a healthy one looks like: your headings appear in a sensible order. Your text is there and readable. Buttons say what they are, and are labelled with what they do. Links describe their destination. Images have descriptions.
What a broken one looks like: a long list of generic entries. Lots of things called “group” or “generic” with no names attached. Buttons with no label. Whole sections of your content simply absent.
If you scroll through and cannot find your own content, an AI agent cannot find it either.
The usual suspects
When it goes wrong, it is nearly always one of these.
Buttons that are not buttons. This is the big one. A designer styles a div to look like a button and wires it up with JavaScript. It looks perfect and works fine for a person clicking it. But Google’s guidance is explicit: prefer real button and a tags, because agents recognise those as interactive. A styled div is, to the machine, just a box with words in it.
Unlabelled icons. A magnifying glass, a hamburger menu, a phone icon with no text. You know what they mean. The tree just sees an image with no name.
Form fields with nothing attached. Google specifically recommends using the for attribute on labels so the field is properly connected to its description. Without it, an agent filling in your contact form is guessing which box is which.
Headings used for looks rather than structure. Text made big and bold with CSS instead of being an actual heading. Visually identical, structurally invisible.
Content that only appears on hover or scroll. If an action only exists after somebody hovers over something, an agent may never find it at all.
The honest caveats
Two things, because I would rather be accurate than dramatic.
The tree is not the only thing agents read. Google is clear that modern agents combine all three: the accessibility tree and DOM for clean structure, then a screenshot to understand layout and grouping. Anyone telling you the tree is the only thing that matters is oversimplifying. It is one of three channels, and the job is to be clean on all of them.
This is not a ranking hack. A tidy accessibility tree will not lift you up Google’s results. What it affects is whether an agent acting for a real customer can actually use your site once it gets there. Different problem, and arguably a more important one, because that is the point at which somebody was about to give you money.
Why I think this one is worth your attention
I am fairly sceptical about most of what gets sold as AI optimisation, and I have written about how to spot the chancers. So it is worth saying why this one is different.
It comes from Google directly, not from an agency’s sales deck. It is measurable, in a tool you already have, for free. It is not a trick that stops working when an algorithm changes, because it is just building things properly. And it does something genuinely good regardless: the same work that lets an AI agent use your site lets a blind person use it too.
That is a rare thing in this trade. A tactic where the commercial argument and the right thing to do point in exactly the same direction.
As Google puts it at the end of that guide, making websites agent-friendly is really just an incentive to recommit to building well-structured, accessible, semantic websites. Which is what we should all have been doing anyway.
Go and have a look at yours. It takes thirty seconds and you may not like what you find.
Want us to check what an AI actually sees when it looks at your site? Get your free audit, or email hello@inkon.co.uk. I read every message myself.