What an “AI agent-ready” website actually means in 2026. Spoiler: it is mostly accessibility.

Direct answer

An agent-ready website is one that software acting for a customer can read and use: every button and link has a real name, forms have real labels, the page does not jump around while loading, your business facts are written in a machine-readable format, and nothing important is hidden until a script runs. Chrome published a toolkit and a Lighthouse audit for this in June 2026, and four of its six checks are accessibility and layout stability. The new part, WebMCP, is optional and only worth adding when you have a booking or quote action an agent should complete.

Who the visitor is now

Three things happened in 2026 that make this real rather than theoretical. Google announced at I/O in May that Search can call local businesses on a user’s behalf and book appointments for local services. Chrome published an “agent-ready website” toolkit on June 22 with a new Lighthouse category to test it. And Perplexity’s Comet browser, which browses sites for you, has been free to everyone since October 2025.

The traffic is still small. SE Ranking measured all AI referrals at about a third of one percent of website visits in early 2026. But the visitor is unusual: it arrives with a job, it does not scroll around admiring your hero image, and if it cannot find the button it leaves and tries your competitor.

What Chrome says agent-ready means

Chrome’s toolkit is the closest thing to an official definition, because it comes with an audit you can run. The Lighthouse “Agentic browsing” category checks six things. In plain English:

1. Every control has a nameAn agent reads the accessibility tree, the same structure a screen reader uses. A button that is just an icon with no label is invisible to both.
2. The page holds stillLayout shift, the same thing Google measures as Core Web Vitals, is a problem for an agent that located a button and then clicked after the page moved.
3. Forms are properly labeledEach field has a label tied to it, a sensible name, required fields marked, and errors written in words rather than a red border.
4. Business facts are machine-readableYour hours, address, phone, services and prices in structured data, so the agent does not have to guess from a paragraph.
5. Actions can be declaredA new protocol called WebMCP, in testing in Chrome, lets a site say “here is how to request a quote” in a form software can call. Optional.
6. A file called llms.txt does not errorThat is the whole check. Chrome calls the file an “emerging convention,” and Google says Search does not use it.

Read that again. Items one through four are accessibility, layout stability and structured data. They were best practice in 2019. The agent did not invent new requirements; it made the old ones unavoidable.

Why most Denver business sites fail it

We run this audit on sites that come to us for a redesign. The same four failures appear on nearly all of them:

• Icon-only buttons (the hamburger menu, the phone icon, social icons) with no label.
• Contact forms where the placeholder text is the only label, and the field names are field_3.
• A reviews widget or chat bubble that loads late and pushes the whole page down.
• No structured data beyond whatever the theme emitted, usually an organization name and nothing else.

None of those is a technology problem. They are a care problem. A template bought for $59 was never checked against a screen reader, and now it is being checked by software with a customer behind it.

What we do on every site we build

Agent readiness is not a line item on our quotes because it is not separate work. Every site we hand-code ships with a 100 accessibility score, named controls, labeled forms, reserved space for anything that loads late, and one connected block of structured data describing the business. We test the quote form with an automated browser before launch, which is the closest thing to the real visitor. The technical write-up, including the exact audit results on a client site, is on our engineering property: agent-ready websites, engineered.

WebMCP we add only when it earns its place: a business with an online booking flow, and staff who can act on a request that arrived from software. For most Denver service businesses, a labeled form and a working phone number is the right amount of agent readiness this year.

How to check your own site in ten minutes

1. Open your contact page on your phoneTry to use it with your eyes closed, using the phone’s screen reader (VoiceOver on iPhone, TalkBack on Android). If you cannot tell what a button does, neither can an agent.
2. Run LighthouseIn desktop Chrome, open DevTools, pick Lighthouse, tick Accessibility and, in Chrome 150 or later, Agentic browsing. Run it on the contact page.
3. Check the formClick into each field. Does a label stay visible, or does it disappear with the placeholder?
4. Watch it loadReload on a slow connection. Does anything jump after the page first appears?

If the answers are bad, you do not need an “AI readiness package.” You need the site fixed properly, and a rebuild that treats accessibility as part of the build rather than a plugin. Our AI-ready websites page explains how we price that, and the small business website checklist has the full list.