Why Your Shop Is Invisible to AI Agents

AI agents are starting to shop online. A user tells their assistant what they are looking for, and the agent works through shops, compares products and makes suggestions. Many shop owners assume they will show up, after all they have product data, prices, images, all maintained.

And yet the agent often sees none of it. The data is not missing, it just sits somewhere the agent cannot reach. This is the most common and hardest-to-spot gap in commerce, and it almost always has the same cause.

The difference between seeing and loading

When you open a product page in your browser, everything looks complete: name, price, variants, availability. What you do not see is how it got there. On many modern shops the page first arrives almost empty, and only then does JavaScript fetch the actual product data and fill it in. For you this happens in milliseconds, you never notice.

An AI agent works differently. Many agents read the HTML the server delivers, and in that first state the JavaScript-loaded product data is not there yet. The agent sees a page where the important part is missing. From its point of view the product page is half empty, even though it looks complete to you.

The tricky part is that nothing in the shop seems broken. The page loads fast, looks good, ranks on Google. The gap only becomes visible once you read the page from a machine's perspective.

How to check this in two minutes

You do not need a tool for this. Open a product page, right-click and choose "View page source". That is the raw HTML as the server delivers it, before any JavaScript runs. Search it for your product name, the price or the SKU.

If you find those values, your foundation is solid. If the search comes up empty even though the browser shows everything, your product data sits behind JavaScript, and an agent most likely does not see it.

What to do about it

The fix is to deliver the key product data server-side, so it is already in the first HTML. Technically this usually happens through structured markup, typically JSON-LD following the schema.org standard, right in the page. It states in machine-readable form what the name, price, variant and availability are, and it sits in the delivered HTML rather than appearing only after a later fetch.

For the common shop systems this is not a big project. Many support it out of the box or have extensions that output structured product data server-side. The work is more about checking and setting it up cleanly than about rebuilding anything.

Why this is worth doing now

Most mid-market shops do not have this on their radar yet. That is not a weakness, the topic is new. But it is shifting. As AI agents become a serious way for customers to find products, the machine-readable layer helps decide who shows up in the selection and who does not.

The first step is an honest status check. You can do the source-code check above yourself. For a closer look, our free Readiness Check shows how well an agent understands your shop today. And if you need a prioritized roadmap, the AI Agent Readiness Audit for Commerce gives you one.

Your product data is there. The only question is whether an agent can find it.