The most important SEO doc Google has shipped in years
Google just published a developer guide called Build agent-friendly websites. On the surface, it reads like a tidy little tutorial about semantic HTML, stable layouts, and ARIA roles. Read it in context and it is something else entirely: the most important piece of SEO guidance to come out of Mountain View in years.
Because what Google is describing — the arrival of a new visitor type that does not see your hero image, does not respect your hover states, and does not care about your scroll-triggered animations — is a structural change in the audience for the open web. And the playbook it lays out is the exact one accessibility advocates have been begging us to adopt since the Bush administration.
If you are an SEO, this is your moment to stop treating accessibility as a side quest. If you are a marketing leader, this is your moment to stop greenlighting redesigns whose only requirement is that they look good in Figma.
Search engines crawled your site. Agents use it.
That sentence is going to do a lot of work over the next two years. A crawler looks at your page and decides whether to index it. An agent looks at your page and decides whether it can complete a task on it: book the flight, return the order, submit the form, pull the spec sheet. The crawler was a passive observer. The agent is a user — one with a job to be done and a thin patience for ambiguous interfaces.
Google's developer post outlines the three lenses an agent uses to see your site: screenshots, raw HTML, and the accessibility tree. The accessibility tree is the headline. It is the same browser-native API that screen readers have used for two decades to tell blind and low-vision users what is on the page. It is, in other words, the most direct semantic representation of your interface that exists. And it turns out that what works for a screen reader works for an LLM-driven agent. Same data, different consumer.
What works for a screen reader works for an agent. Same data, different consumer.
This is not a coincidence. It is a forcing function.
The first is that traditional search optimization — the discipline of rendering your site to be ranked by Googlebot — is becoming a subset of a much larger problem. The new question is not "can the crawler parse my page?" but "can an autonomous system act on my page?" Indexing is table stakes. Actionability is the prize.
The second is that the people who already had the answer were not in the SEO chair. They were in the accessibility chair, and most organizations have spent the last twenty years treating that chair as an afterthought, a compliance line item, or a thing to bolt on after launch.
Google's checklist for agent-readiness reads like a copy-paste from any WCAG primer ever written. Use semantic HTML. Use real button and anchor elements, not divs decorated with click handlers. Add for attributes to your labels. Keep layouts stable. Make interactive targets a sensible size. Apply roles and tabindex when the markup falls short.
Every one of those bullets has been on accessibility-audit reports since the iPod was new. The difference is that, this time, ignoring the advice is going to cost you traffic, conversions, and — increasingly — placement in the agent ecosystems that will mediate a growing share of commercial intent.
Three shifts are coming, and the operators who get ahead of them will own the next cycle.
aria-describedby.Get the free AEO Quick-Start Checklist — the 12 things to check before agents become your biggest visitor.
Sent instantly. No spam — unsubscribe any time.
Stop approving redesigns whose only success metric is "looks premium."
The next 18 months of web strategy is a question about resilience, not aesthetics. Can an agent buy from your site on behalf of a customer? Can it pull a quote? Can it confirm availability? Can it identify the right contact form? If the answer involves a vision model squinting at your custom-styled dropdown, you have already lost to the competitor whose form is wired to a real select element.
The good news is that the work to fix this is not exotic. It is craft work. It is hiring developers who care about semantic HTML. It is paying down the accessibility debt your last three agencies told you to ignore because the timeline did not allow for it. It is treating your design system as load-bearing infrastructure rather than a Pinterest board.
The better news is that every dollar you spend here pays out twice. Once for the agents that will increasingly mediate your customer relationships. Once for the human users — including users with disabilities — who have been quietly bouncing off your site for years.
The honest read of Google's post is that the open web's foundational principles were never wrong. We just did not have a strong enough business case to follow them. SEO budgets did not require it. Conversion-rate teams did not push for it. Design leadership treated it as a constraint rather than a brief.
Agents change the math. The site that works for a screen reader is the same site that works for a Claude, a ChatGPT operator, a Gemini agent, and whatever comes next. Semantic HTML is not retro. It is forward-compatible.
This is the rare moment in our industry where the strategic frontier and the ethical baseline converge on the same answer. Build the accessible site. Use the real elements. Label your inputs. Stabilize your layouts. The crawlers will reward you, the agents will trust you, and the humans you have been quietly excluding will finally be able to use your product.
The new SEO is not new. It is the old accessibility, finally given a P0.
If you want a starting point for building this into your own practice, the AEO + GEO Strategy Framework walks through how to brief leadership on these shifts and where to focus first. The SEO Audit Report Card includes the technical and semantic-markup checks you will need to fold accessibility-tree health into your standard audit.
Frameworks for SEO practitioners getting their sites — and their leadership — ready for what comes next.