Agent experience (AX): can an AI shopper finish the job on your store?

AX next to the things you already know

Three ways AI shoppers arrive

AX is hard to judge from your own browser because agents don't all see your store the way you do. There are three routes in, and a store can work on one and fail on another.

• Code-reading agents drive a real browser but read the page's accessibility tree instead of looking at it. Unlabelled buttons and controls built from plain <div>s are invisible to them.
• Screen-reading agents work from screenshots, the way a person would. They need the page to look finished: search results that render, popups they can close, buttons that look like buttons.
• Protocol agents skip your pages entirely. Google's AI Mode and Gemini shop Shopify stores through the Universal Commerce Protocol (UCP): they search your catalogue, build a cart and ask for a checkout as data. Your theme never loads. Your product data and checkout settings are all they get.

Where AX breaks on Shopify

When we sent all three kinds of agent to ten well-known Shopify stores, four lost at least one browser agent before the order total. None of the problems was exotic:

• Bot walls. A checkpoint that challenges cloud traffic turned both browser agents away from one store before it loaded.
• Buttons that aren't buttons. One store's cart drawer showed a big Checkout button that wasn't in the accessibility tree, so the code-reading agent found nothing to press.
• Search that won't load from the cloud. Four stores showed grey placeholders or blank results to cloud browsers, and on three of them the screen-reading agent gave up.
• Popups and login walls. Sign-up popups on the first click and a login prompt before guest checkout slowed agents down.
• Hidden shipping costs. In an earlier five-run test, agents asked for the standard shipping price before checkout couldn't reliably find it on three stores.
• Protocol hand-backs. Every store sent the protocol agent's checkout back to the buyer to finish on the store's own page.

An AX checklist for Shopify stores

1. Let AI agents in

   Open yourstore.com/robots.txt and look for rules that block AI agents such as ChatGPT-User, PerplexityBot, Claude-User or Meta's crawlers. Shopify lets you change it with a robots.txt.liquid template.

2. Don't wall out the cloud

   Hosted AI agents browse from data centres. Ask whoever runs your bot protection, whether that's an app, a CDN or a firewall, what it does to traffic from cloud servers, and make sure a real shopping session can get through.

3. Make every button a real button

   Checkout, Add to cart and the cart drawer's controls should be <button> or <a> elements with a readable name. Check the cart drawer first: it's often built by an app, and it's where we found the worst problem.

4. Make sizes and colours readable

   Variant pickers should be labelled radio buttons or a labelled select, visible without opening a menu first, with sold-out options marked as such.

5. Make search and collections show up

   Products should appear in the page itself, not only after a search app's script finishes. Load your search results from a cloud browser, not just your laptop, and see whether the products are there.

6. Keep popups off the first click

   Delay sign-up and recommendation popups, and give each one a close button with a name. An agent that can't dismiss a popup can't shop behind it.

7. Offer guest checkout and show shipping early

   Agents check out as guests. Don't ask for a login before guest checkout, and show the shipping cost and a delivery estimate before the payment step.

8. Put shipping and returns in your product data

   Protocol agents only know what your data says. Fill in your shipping rates and return policy in Shopify's settings, and make sure your product pages' structured data carries shippingDetails and hasMerchantReturnPolicy.

9. Check where a hand-back lands

   When a protocol checkout needs the buyer, Shopify sends them to your checkout page. Checkout apps and extensions that ask the buyer for input are one reason it happens. Make sure the buyer arrives on a checkout already filled in, with only payment left to do.

How to test your store's AX

You can check a lot by hand. Chrome's DevTools has an accessibility tree view under Elements, which shows roughly what a code-reading agent sees. A screen reader, like VoiceOver on a Mac, will tell you fast whether your cart drawer's Checkout can be reached. Loading your store from a cloud machine shows what hosted agents get.

Or run the free test. Three agents, one of each kind, try to buy a real product from your store, stop before paying, and show you where each got stuck, with the reason. It takes about five minutes.

Questions

Is agent experience the same as accessibility?

They overlap a lot. Code-reading agents use the accessibility tree, the same structure screen readers use, so a button a screen reader can't find is usually one those agents can't find either. Screen-reading and protocol agents add problems accessibility doesn't cover, like bot walls, search that won't load from the cloud, and product data that leaves out shipping.

Is AX the same as AI SEO or GEO?

No. AI SEO, also called GEO or AEO, decides whether an AI assistant recommends your store. AX decides whether the agent can buy once it has. A store can be recommended in every answer and still lose the sale at a cart drawer.

Does AX matter if AI agents don't buy much yet?

Nobody can tell you yet what share of your traffic is AI agents, and we won't pretend to. What's cheap to find out is whether the agents that do arrive can finish. Most AX fixes are accessibility and checkout fixes that help human shoppers too.

Do I need an app to improve AX?

Usually not. Most fixes are theme and settings changes: real buttons, readable variant pickers, guest checkout, visible shipping costs, and policies in your product data. The work is finding which ones your store needs.