Stall library · Discover
Plans are sold, but no product page is published for an agent to read
A site that sells by plan sells hosting, software, domains or a subscription from plan cards with a buy button, and publishes no product page. The buy buttons work: they go straight into the site’s own cart. But there is no page per plan, no product feed and no product in the sitemap, so an AI shopping agent that looks for products to read and compare finds nothing it recognises as one.
Why the agent stops
An agent shortlists what it can read. It asks the platform for a feed, reads the sitemap for product pages and follows product links from the home page, then compares names, prices and what each one includes. A plan that exists only as a card on a marketing page has a price a person can read and nothing an agent can cite, so it is left off the list.
The buy button itself is usually fine. A plain link or form into the cart is one of the easiest things on the web for an agent to press. What is missing is the step before it: a page that says what the plan is, what it costs and what it includes, in a form the agent can quote back to the person it is buying for.
How often we see this
Not stated here. A frequency means nothing without the cohort it was counted over, and this page is about one stall rather than one category. Where a category has enough stores measured at every stage, the share of them showing this stall is published on its benchmark page, with the methodology beside it.
See it for yourself
- Open /sitemap.xml and look for one URL per plan. Marketing pages that each show several plans do not count.
- View the source of a plan card’s page and search it for schema.org Product, Service or Offer markup with the plan’s price.
- Ask an AI assistant to compare your plans with a rival’s by price and features, and see which of the two it can quote.
What to change
- Give each plan a page of its own with its name, price, billing period and what it includes in the HTML the server returns.
- List every plan page in the sitemap.
- Add schema.org Product or Service markup with an Offer and its price to each plan page.
- Keep the buy button on each plan page as a plain link or form into the cart.
What Ottom looks at
Ottom reports this instead of “No products found” when the site answered, no wall was detected, no catalogue endpoint, sitemap entry or home page link led to a product, and the home page has buy controls that go into the site’s own cart or order pages: an add to cart address, or a cart, order or checkout address on a control that says buy, in any of the languages the scan reads. The addresses are kept as the evidence. The scan then tests the plan checkout: a browser opens the page the buy buttons are on, chooses a plan, presses its buy button and goes on through the cart.
Questions
Do AI agents treat a hosting or software plan as a product?
Yes. To an AI agent a plan is a product: something with a name, a price and a way to buy it. A site that sells hosting, software or subscriptions is read the same way as a shop. Publish each plan the way a store publishes a product and an agent can compare and buy it like one.
Did the scan test our checkout?
Yes. With no product page to start from, it starts from a plan. A browser opens the page your buy buttons are on, chooses a plan, presses its buy button and goes through your cart the way a shopper would, stopping before payment. The buy stage of your report is that walk, so it tells you whether an agent that has chosen a plan can actually buy it.
Our buy buttons work. Why is this Critical?
Because an agent has to choose a plan before it presses anything, and with no plan page it has nothing to choose from. The severity is the same as a site with no products at all, which is what this site looks like to an agent reading it.