If you run a home-services or aesthetics marketing agency, every client site you have ever built just got a second user. Not a person. An AI agent, sent by a real customer to book the appointment, compare the quote, or grab the phone number. And most of those sites can't be read by it.
A comment on my last post asked the right question. I had written about agentic browsing, and someone pushed back: isn't chasing the audit a trap? Shouldn't we care about user experience and how AI reads our content, not just checkboxes? Here is my answer, and it's the whole point of this post. For an agent, passing those checks isn't a shortcut around user experience. It is the user experience.
Key Takeaways: Agent Experience (AX) is the experience an AI agent has as the user of your product or site. Netlify's CEO coined the term in January 2025. Google shipped an agentic score in May 2026, but it is not a ranking factor. Design for the human first, make the same content legible to the agent second.
What is Agent Experience (AX)?
Agent Experience is the experience an AI agent has as the user of your product or site. The term isn't mine. In January 2025, Mathias Biilmann, the CEO of Netlify, coined it in a post called Introducing AX. His definition, in plain terms: the whole experience an AI agent has as the user of a product or platform.
In that same post, Biilmann places AX in a line you already know. Don Norman named user experience, UX, in 1993. Developer experience, DX, followed around 2011 for the people building on platforms. AX is the same idea aimed at the software agents those people now send in their place. I'm Eric Forte, an AI Automation Engineer, so this is the layer I live in: systems that other systems have to operate.
Agent Experience vs UX: what's the difference?
No, AX is not UX with a new name. Same site, two users, and they want opposite things. A human needs a clean layout and a button that feels right. An agent needs structured data and output it can predict. One reads the page. The other reads the accessibility tree underneath it.
Passing an agent-readiness check isn't a shortcut around UX. For the agent, it is the UX. Take a home-services agency that ships a sharp client site with the phone number baked into a header image. A person reads it fine. An agent booking a same-day pest or HVAC call on someone's behalf sees nothing there, because an image carries no text it can parse. The job goes to the competitor whose number is real text.
The term already has vendors. Here's the signal and the noise.
AX already has an industry forming around it. You'll start seeing Agent Experience Optimization (AXO) and Agentic AI Optimization (AAIO) marketed, some aimed at exactly this problem. That's fine. But a lot of it is noise: generic think-pieces on designing for agents, written for other designers.
Here is the signal I'd hold onto. One test cuts through all of it: can an agent finish a real job on your site? Book the slot. Pull the quote. Discovery, then citation, then action. If an agent can be sent to your site and complete the task a customer wanted, you have agent experience. If it can't, no amount of vocabulary fixes it.
Is agentic browsing a ranking factor?
No. In May 2026, Google added an Agentic Browsing category to Lighthouse, the engine behind PageSpeed Insights, and Google has been explicit that the category is not a search ranking factor. It's marked experimental and reports a pass ratio like 3 of 3, not a 0 to 100 score. So don't chase a perfect 3 of 3 the way you'd chase Core Web Vitals. It's a lab score. It won't move your ranking. My own site passes it 3 of 3, and I didn't build for the badge. I built for the work underneath, clean structure and readable content, worth doing whether Google scores it or not. Want the mechanics, the checks, and the llms.txt rules? Read the full breakdown of how the agentic browsing checks work.
What AX means for a home-services or aesthetics agency
For a home-services or aesthetics service business, AX means an agent can read your phone number, hours, and price range as real text, and finish a booking or quote request without a mouse. Your client's next customer may send an agent to their site before a human ever lands on it. That isn't a far-off scenario. Back in 2024, Gartner predicted traditional search engine volume would fall 25% by 2026 as people shift to AI assistants and agents. When the agent can't use the site, the booking goes to one it can.
Picture an aesthetics agency running a med spa's site where the whole booking flow is a JavaScript-only widget. A person clicks through it. An agent trying to book a consult hits a wall it can't operate, and moves on. Same story for a solar or roofing lead form that only fires with a live cursor.
This is the same discipline I already build on. A workflow in n8n or GoHighLevel only survives real volume if its data is structured and its output is predictable. I built a voice system for a pay-per-lead network that routes homeowner calls to home-services companies, and it still handles over 16,000 calls a month because it was engineered for machines to run at volume. An agent-ready website is that same principle, moved to the front door. There's even an emerging standard for it, WebMCP, which lets a site hand real actions to an agent instead of hoping the agent guesses its way through the page. That's the same tool-calling shape I already wire into automations.
How to think about AX without the hype
Keep it boring and it works. Design for the human first. Make that same content legible to an agent second. Don't treat any single score as the goal. Here are a few things you can fix on any client site today, no budget required.
- Put the phone number, address, and hours in real text, not baked into an image.
- Use real HTML buttons and links for every action, not click targets that only a mouse can fire.
- Keep the layout stable so elements don't jump around as the page loads.
- Add an llms.txt at the domain root so agents get a clean summary of the site.
None of that hurts your human visitors. All of it helps the agent. That's the trick: AX and UX aren't in a fight. Do the honest version of both.
An agent reading your site and an automation running your business need the same thing: structure a machine can follow. The automation side is what I build, in GoHighLevel and n8n. If yours needs building, book a call.
Frequently Asked Questions
Is Agent Experience the same as UX?
No. UX is for the human visitor. AX is for the AI agent that visits on that human's behalf. Same site, different user, different needs. Netlify's CEO Mathias Biilmann coined the term in January 2025 to name the difference, sitting alongside UX and developer experience.
Did Google make agentic browsing a ranking factor?
No. In May 2026 Google added an experimental Agentic Browsing category to Lighthouse and PageSpeed Insights, and it has said plainly that this is not a search ranking factor. It's a diagnostic score, not a ranking lever. Treat it as early feedback.
What is Agent Experience Optimization (AXO)?
AXO is a vendor term for making a site usable by AI agents. In my framework it breaks into three layers: discovery, so the agent finds you, citation, so the agent trusts and quotes you, and action, so the agent can complete a task like booking or buying. Think of it as AX turned into a checklist, not a certified standard.
Does a small home-services business really need this yet?
It depends on whether customers are sending agents to book. For most local shops that's early, not urgent. The honest move: do the no-cost basics now, readable contact info, real buttons, stable layout, an llms.txt, and skip the paid hype until agent-driven bookings actually show up.
What does AX mean for a service business website?
For a home-services or aesthetics service business, AX means an agent can read the phone number, hours, and price range as real text, use real HTML buttons to book or request a quote, and load a stable layout that doesn't reflow while it reads. A pest, HVAC, or med-spa site that ships those basics lets an agent finish the booking. One that hides that behind an image or a JavaScript-only widget loses it to a competitor the agent can use.
The short version
Your website has a second user now, and it isn't human. Agent Experience is the name for serving it. The term is real, Netlify coined it in 2025, and Google's new score is real but not a ranking factor. Design for the person first, make the same content legible to the agent second, and you've done the job.
PageSpeed Insights