The Agent-Ready Website: What Breaks When Your Visitor Is Software

Your website was designed for someone who scrolls. Who hovers over a spec to see more, waits half a second for the price to fade in, opens the returns PDF if it matters enough, and emails you when something is unclear. Every good instinct in modern web design assumes that visitor.

A second kind of visitor is now reading the same pages. It does not scroll, does not hover, does not wait for your scripts to finish, and will never send you a question. It makes one pass, fills in the fields it can, and leaves with whatever it got. If the fields are empty, you were not rejected. You were unreadable.

What actually changed, and how much

The plumbing arrived faster than the behaviour. Stripe and OpenAI published the Agentic Commerce Protocol in September 2025, an open Apache-licensed standard for checkout flows between buyers, agents, and businesses, launched alongside ChatGPT Instant Checkout. Google announced the Universal Commerce Protocol on 11 January 2026, co-developed with Shopify, Etsy, Wayfair, Target, and Walmart. Two rival standards for the same idea, both open, both shipped inside twelve months.

The behaviour is further out, and the honest version of this argument depends on saying so. Bain’s December 2025 forecast puts agentic commerce at 300 to 500 billion dollars in the US by 2030, which is 15 to 25 percent of e-commerce, and notes that most consumers are still uncomfortable letting AI complete a purchase end to end. What is already common is the step before the purchase: Bain puts 30 to 45 percent of US consumers using generative AI for product research today.

That is the useful shape of it. Software is already doing the shortlisting, and shortlisting is where you get eliminated.

What a person forgives and software cannot

A person who cannot find your price scrolls, then guesses, then asks. An extractor records price: unknown and moves to a competitor who stated it. The gap between those two behaviours is where almost all of the damage happens, and it is invisible in your analytics because nothing was clicked.

None of those five is a design failure by human standards. A price set in the hero image looks better than a price in a paragraph. Loading the spec table on scroll makes the page faster. A PDF policy is what your lawyer sent you. Every one of them is a reasonable decision that happens to be invisible to a reader who cannot run your JavaScript.

The fork

A visitor lands on your product page. Which one is it?

A person

Scrolls, waits for the script, hovers for the spec, and emails you when the price is unclear. Forgiving, and slow.

An agent

One pass, no scrolling, no waiting, no follow-up question. It takes what is stated and leaves with the rest blank.

Everyone loses at the same step

Watch the sequence an agent has to complete to be any use to the person who asked it something. Find the page. Resolve the facts. Compare against the alternatives. Find a route in. Act.

Most sites pass step one comfortably. Search engines have been finding pages for twenty five years, and the same work that makes you citable in an AI answer gets you found here too. Step two is where it ends for almost everyone, and steps three through five are never reached, not on their merits but because there was nothing to compare.

That is why “we rank well” is no longer reassurance. Being found and being usable are now separate problems, and only one of them shows up in your reports.

Being found and being usable stopped being the same problem. Only one of them shows up in your analytics.

The fixes are unglamorous, and they pay twice

Nothing on this list requires a redesign, a rebuild, or a new platform.

State the price in text, not only in an image or a script-rendered element. Say stock and lead time in words, because a disabled button is not a fact. Put the returns, cancellation, and warranty terms on a page instead of in a PDF. Move key specs out of tabs and accordions that only populate on interaction. Give every bookable or buyable thing a direct URL. Then mark it all up with structured data so the facts are labelled rather than inferred.

Here is the part that makes this an easy decision rather than a bet. Every one of those changes helps a human in a hurry, on a phone, on a bad connection, or using a screen reader. A page that states its price plainly converts better with people too. If agent traffic never materializes for your business, you are left with a faster, clearer, more accessible site, which is the same thing you would have wanted anyway. That asymmetry is rare enough to act on.

The same logic runs through the end of forms: the interface stops being the product, and the facts underneath it start being the product.

What this does not mean

Four things worth refusing, because the vendor pitch around this is already ahead of the evidence.

Do not rebuild for agents. Agent-completed transactions are a small share of trade today and Bain’s own forecast is five years out. Anyone proposing a platform migration for this is using a trend to sell you a project.

Do not generate hundreds of thin pages to feed the machines. That is the old content-farm play in new clothes, and it degrades the site for both audiences.

Do not hand over pricing authority. If you do open a checkout to agents, the terms stay yours: the ACP specification explicitly lets a merchant accept or decline on a per-agent, per-transaction basis, and that control is the point. An agent should read the rules you published, never set its own.

And do not confuse readable with persuasive. Making your facts extractable gets you into the comparison. It does not win the comparison. If your price and terms are simply worse, clarity will surface that faster, which is uncomfortable and also useful.

What to do Monday

Open your most important product or service page and read it as software would: ignore anything that needs a click, a scroll, or a script. Write down what you can still learn. If price, availability, or how to buy is missing from that list, you have your first three tickets, and they are content edits, not a project.

Then measure it rather than assuming. The probe method for AI search visibility works the same way here: ask an assistant to compare you against two named competitors and see which facts about you it gets right. For a worked version of the whole thing on a storefront, the agentic commerce case study walks through the layers end to end.

---

Want to know what an agent can actually read on your site? Book a free consult and we will pull your key pages apart the way an extractor does, and hand you the list of fixes ranked by what they cost and what they unlock.