Is your website ready for AI agents? These tools now browse sites for people. They click buttons, fill forms, and work through booking steps.
Google's own guidance says the fixes are mostly good web basics. Clear code helps agents, screen readers, and customers alike. This checklist turns that guidance into plain steps.
Reporting note: We checked Google's web.dev and Chrome documentation on October 6, 2026. Agent tools change fast. This guide can't promise bookings, rankings, or sales.
Key takeaways
- AI agents act on websites, so they need clear buttons, links, and forms
- Most agent-friendly fixes are basic accessibility work that helps people too
- Hidden overlays and layout shifts can cause agents to misclick
- Chrome's Lighthouse has an experimental agentic browsing category
- WebMCP is still a proposal, so most small sites can wait
What is an AI agent, and why does it matter for your website?
An AI agent is a tool that takes actions for a person. Someone might ask one to book a cleaning or request a quote. The agent then opens websites and tries to finish the job.
Google's web.dev team has published guidance on how agents read sites. Some agents look at screenshots. Others read the page's code and its accessibility tree.
The accessibility tree is a simple map of your page. Screen readers use it to describe buttons and fields. Agents use it to work out what they can click.
That's why the same fixes pay off twice. A clearer site serves visitors who use screen readers. It also serves the agents acting for your future customers.
Use real buttons and links
Many sites build buttons from plain boxes styled to look clickable. People can see them, but software can't always tell. Google's guidance says to use real button and link elements in the code.
Here's what to ask your web designer to confirm:
- Buttons for actions, like Submit, Book now, or Add to cart
- Links for moving to another page
- A pointer cursor on anything people can click
- Controls big enough to see and press, not tiny icons
Size matters more than you might think. Google notes that agents may skip very small elements. A tiny icon with no text can vanish from an agent's view.
Sometimes a developer can't use a real button. Then the guidance suggests adding a button role and a tab stop. Those tell software that the box acts like a button.
Label every form field
Forms are where an agent does its real work. A field with only gray placeholder text gives it little to go on. A visible label tied to the field tells people and agents what belongs there.
In the code, each label should point to its field. Contact, quote, booking, and checkout forms matter most. Those are the forms that turn visitors into customers.
Use this quick check on each form:
- A visible label on every field
- Labels linked to their fields in the code
- A clear name on the submit button, not just an arrow
- Error messages that say what to fix
These points also line up with the W3C's accessibility guidelines. That's the common reference for sites that work for people with disabilities.
Remove hidden overlays that cover buttons
Some sites lay a clear layer over the page. Chat widgets, cookie banners, and pop-up scripts can all do this. Google warns that agents may ignore elements under a transparent overlay.
To a person, the button looks fine. To an agent, it may look blocked or missing. Check that nothing invisible sits on top of your main buttons.
Visual cues help too. Google's guidance points to color, size, and spacing. A bold Book now button and a small Help link send different signals.
Why do shifting layouts trip up agents?
Picture an agent about to click Book now. A late banner loads and pushes the page down. The click lands on the wrong thing.
Google measures this movement with Cumulative Layout Shift, or CLS. It's one of the Core Web Vitals. It also shapes how steady a page feels to people.
Chrome's documentation names a few common causes:
- Images without set dimensions
- Ads that load after the content
- Content that scripts add above what's already there
Google's guidance also asks for layouts that stay consistent. Keep your main buttons in the same place from page to page. That helps agents and returning visitors alike.
How do you check your site with Lighthouse?
Chrome's free Lighthouse tool now has an Agentic Browsing category. It needs Chrome 150 or later. Google labels it experimental and based on proposed standards.
It doesn't give a 0 to 100 score. Instead, it shows a pass ratio and a pass or fail for each check. The Chrome team says it aims for signals you can act on.
Scroll sideways to read the full table.
| Check | What it looks at | Who should act |
|---|---|---|
| Accessibility for agents | Names and labels on buttons, links, and fields | Every site |
| Layout stability | Cumulative Layout Shift as the page loads | Every site |
| llms.txt | A summary file at your domain root | Optional for most small sites |
| WebMCP | Tools a site registers for agents to call | Most small sites can wait |
Our guide to llms.txt covers the third check. In short, Google Search says it doesn't use the file.
You can also see what agents see. Chrome DevTools can show the full accessibility tree. Here's how:
- Open your booking or contact page in Chrome.
- Open DevTools and go to the Elements panel.
- Open the Accessibility tab.
- Turn on Show accessibility tree.
- Look for buttons and fields with no name.
Do you need WebMCP yet?
WebMCP is a proposal that lets a site hand agents clear tools. A booking form could tell an agent exactly which details it needs. Google's guidance says purchases and other sensitive steps should still ask the person to confirm.
It's not a finished standard. The latest draft carries an October 2, 2026 date. It says it isn't on the W3C Standards Track.
Chrome only tests it through a trial program for now. So for most small businesses, the basics come first. Fix buttons, labels, overlays, and layout shifts before you think about WebMCP.
Does an agent-friendly site help SEO or AI search?
Google hasn't said agent readiness is a ranking factor. Chrome's toolkit says normal SEO principles still apply when agents search. That SEO work is what helps customers find you.
So treat agent readiness as a usability project. Search brings people to your site. A usable site helps them book once they arrive.
Our GEO work covers the other side: helping customers find your business in AI answers. Our web design work aims to make every page easy to use.
Accessibility can also raise legal questions. This is general marketing information, not legal advice. Talk to a lawyer about any compliance concerns.