Google’s Agent Friendly Checklist Is the Accessibility Audit Restated

Google's seven rules for building agent friendly websites are the accessibility playbook restated for AI agents. Same audit, two visitor classes. The same pattern also shows up in X Robots Tag, where the practical question is how the signal becomes visible.

The practitioners who already did the work for blind and low vision users are most of the way to passing. I noticed the page because Matt G.

The Seven Agent Friendly Rules Google Published On Web.dev

The full list lives at web.dev/articles/ai agent site ux, introduced by Google with the line, "To help agents navigate your website, consider following:" Reflect every action in the interface. A button click should produce a visible state. The strategic issue is whether automated visitors can understand, trust, and complete the same journey a human visitor can. Agent readiness is partly technical, but it is also about clear tasks, accessible flows, and reliable evidence.

The risk is usually hidden in the execution layer. A page can look fine to a human and still fail for an automated visitor if the form, call to action, rendering path, or confirmation step is not accessible enough for the agent to complete the task.

Six Of Google's Seven Agent Friendly Rules Pass On Nohacks.co (1, 2, 3, 4, 6, 7)

I ran the audit by inspecting the live HTML on the homepage and on a representative article page, the agentic browser landscape guide. The method was unglamorous: curl the page, grep for,,, pointer events none, then pull the compiled. The strategic issue is whether automated visitors can understand, trust, and complete the same journey a human visitor can. Agent readiness is partly technical, but it is also about clear tasks, accessible flows, and reliable evidence.

Rule 5 (Cursor: Pointer) Fails On Every Native Button Under Tailwind V4

elements are fine. Anchors with href get cursor: pointer from the browser default, and that hasn't changed. The failure is button specific. The cause is a Tailwind v4 change. From the official Tailwind CSS v4 upgrade guide: "Buttons now. The strategic issue is whether automated visitors can understand, trust, and complete the same journey a human visitor can. Agent readiness is partly technical, but it is also about clear tasks, accessible flows, and reliable evidence.

Every Rule On Google's List Maps To An Existing WCAG Recommendation

The accessibility community has been writing the same list for two decades. Five of Google's seven rules map directly to a WCAG criterion: Rule 2 (stable layout) overlaps with WCAG 2.4.3 (Focus Order) and WCAG 3.2 (Predictable). Rule 4. Local visibility depends on whether the details across pages, profiles, categories, reviews, photos, and service descriptions reinforce the same answer for a specific location based query.

The operational question is whether the public business data is complete enough to support the query. Hours, categories, services, reviews, photos, and page content need to reinforce each other so Google can understand the business in a specific situation, not only as a generic listing.

Run One Accessibility Audit, Recover Both Visitor Classes

Stop running accessibility audits and AI agent readability audits as separate disciplines on separate quarterly cycles. They are the same audit. Web professionals who already invested in WCAG conformance are most of the way to passing. The strategic issue is whether automated visitors can understand, trust, and complete the same journey a human visitor can. Agent readiness is partly technical, but it is also about clear tasks, accessible flows, and reliable evidence.

Search Interest In "Web Accessibility" Barely Moved When The EAA Took Effect, Then Quadrupled

Search interest was flat for four years. Through 2024. Through most of 2025. Through the European Accessibility Act becoming applicable on 28 June 2025, which is the regulatory event that should have moved this curve more than anything. The strategic issue is whether automated visitors can understand, trust, and complete the same journey a human visitor can. Agent readiness is partly technical, but it is also about clear tasks, accessible flows, and reliable evidence.

The Convergence Is A Decade Old; Google's Vendor Weight Is What's New

The last decade of accessibility work was carried by a community that mostly didn't have the weight to make it the dominant audit discipline. The work was the right work. The audience didn't show up. Then AI agents arrived with budget,. The strategic issue is whether automated visitors can understand, trust, and complete the same journey a human visitor can. Agent readiness is partly technical, but it is also about clear tasks, accessible flows, and reliable evidence.

The Seven Agent Friendly Rules Google Published On Web.dev in practice

Introduction Google's seven rules for building agent friendly websites are the accessibility playbook restated for AI agents. Same audit, two visitor classes. The practitioners who already did the work for blind and low vision users are. Local visibility depends on whether the details across pages, profiles, categories, reviews, photos, and service descriptions reinforce the same answer for a specific location based query.

What the visibility signal actually changes

What the visibility signal actually changes: google’s Agent Friendly Checklist Is the Accessibility Audit Restated: the Practical Angle should be treated as a visibility signal, not a standalone headline. Introduction Google's seven rules for building agent friendly websites are the accessibility playbook restated for AI agents. Same audit, two visitor classes. The practitioners who already did the work for blind and low vision users are most of the way to. This connects with New Data Suggests when the same signal needs a clearer operating decision. A useful companion note is Agent Transactions Change AI Visibility, because it looks at a nearby part of the same system.

What the visibility signal actually changes: the practical question is whether the page, brand evidence, and surrounding content make the answer easier to trust. If that support is weak, search systems can still understand the topic but fail to connect it confidently to the brand.

What the visibility signal actually changes: that is why the response should begin with an audit of the evidence already on the site before creating a new asset. The fastest improvement is often a clearer page, a better internal link, or a stronger explanation of why the brand belongs in the answer.

Where the evidence needs to be tested

Where the evidence needs to be tested: a single study or ranking observation should not become a strategy by itself. It should become a diagnostic prompt: which source is being trusted, which query pattern is affected, and which part of the site would make that trust easier to earn?

Where the evidence needs to be tested: that keeps the response grounded. The goal is to improve the evidence chain around the topic rather than publish another summary that repeats what every other page already says.

Where the evidence needs to be tested: the important distinction is between a useful signal and a fashionable talking point. A useful signal changes the brief, the page structure, the linking plan, or the measurement view.

How to avoid overreacting to one data point

How to avoid overreacting to one data point: for content teams, the strongest move is to map the claim to existing assets before creating anything new. The right page may already exist, but it may need clearer headings, stronger internal links, fresher proof, or a better explanation of why the brand belongs in the answer.

How to avoid overreacting to one data point: this is also where title rewriting matters. A title should not copy the source headline; it should frame the practical implication so readers immediately know why the topic deserves attention.

How to avoid overreacting to one data point: the same standard should apply to every section. Each heading needs to earn its place by moving the reader through the evidence, not by repeating the outline in a more polished voice.