Google tells web developers to treat AI agents as a distinct ‘visitor’ in new developer guidance

Web development just got a new default user — not a person with a mouse, but an AI agent trying to finish a task. That is the shift sitting underneath Google’s new guidance for site owners. The old assumption was that if a page looked good to humans and maybe indexed well for search, that was enough. Google’s new web.dev article says that assumption is breaking fast, because agents now browse, interpret, and act on behalf of users. ### What did Google actually publish? Google’s Chrome and web.dev ecosystem published a new guide called “Build agent-friendly websites” in April 2026. The piece frames AI agents as “a new type of visitor” and says many modern sites are built around hover states, shifting layouts, and visual flair that work for people but fail for software trying to complete a goal. That is the core news here — Google is not just the wider web to design for being visited by them. ### Why is “visitor” the important word? Because “visitor” changes the job. If agents are visitors, then your site is not only a human interface anymore. It is also an environment another system has to read and operate inside. Google has talked for a while about AI agents as a software pattern, but this guidance moves the emphasis to the public web itself — the website has to be legible to autonomous software, not just beautiful to humans. ### How do agents see a website? Not the way people do. The guide says agents typically consume a site in three forms: screenshots, raw HTML, and the accessibility tree. That means hidden labels, semantic structure, button names, form relationships, and machine-readable content suddenly matter a lot more. A flashy interface can still exist, but the underlying representation has to stay clean and stable or the agent loses the plot. ### So what is Google telling developers to change? Basically — make the path through your site obvious to software. Google’s recommendations lean on familiar web fundamentals: semantic HTML, accessible naming, clear information hierarchy, and layouts that do not constantly reshuffle. The guide also pushes explicit action surfaces, so an agent can tell what “buy,” “book,” “next,” or “submit” actually means without guessing from visual context alone. ### Why does accessibility keep coming up? Because the overlap is huge. If a site is understandable through the accessibility tree, it is already exposing structured meaning instead of just pixels. Google more or less says the same work that helps screen readers also helps agents — strong labels, predictable controls, and semantic markup. This is not identical to accessibility, but it rhymes with it enough that the inclusive web practice. ### What about logins and actions? This is where the advice gets practical. Agents do not just read pages — they may need to sign in, navigate steps, and complete tasks. Google’s broader agent guidance stresses tool use, permissions, session handling, and reliable orchestration, and the web.dev piece brings that mindset to the front end. If authentication is brittle, labels are vague, or flows depend on fragile visual cues, autonomous task completion falls apart. ### Is this really new, or just old best practice renamed? Both. The implementation advice is familiar — semantic markup, progressive enhancement, accessibility, stable structure. But the reason for doing it has changed. Google is effectively saying these practices are no longer just about usability, SEO, or compliance. They are now about whether your site can participate in an agent-driven web at all. Bottom line The big change is conceptual. Google is nudging developers to think in three layers now: human UI, API, and an agent-readable interface in between. If that framing sticks, “agent-friendly” will stop sounding experimental and start sounding like basic web hygiene.