Stall library · Compare
Catalog has no category structure to compare within
A category structure stall happens when your products carry no product type and your store publishes no collection pages, so an AI agent asked for a waterproof jacket has no way to narrow your catalogue to jackets. It then compares you on whatever it happened to read, which for most catalogues means the first few products it found rather than the right ones.
Why the agent stops
Agents work under a fetch budget, so narrowing is how they get to the relevant part of a catalogue at all. A category is a cheap filter: one URL that returns the candidates. Without one, the only available filter is reading everything, and reading everything is exactly what the budget prevents.
The result is a quiet mismatch. Your store may stock the best answer to the shopper request and be represented in the comparison by an unrelated product, because that was the product in reach.
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
- Ask yourself whether there is a single URL on your store that returns all of one product category and nothing else. If not, an agent has no filter either.
- Check your feed for a product type or category field and see how many products have one populated.
- Check your sitemap for collection URLs.
What to change
- Set a product type or category on every product, and use a consistent vocabulary rather than free text.
- Publish collection pages so a category is browsable as a URL.
- List collection URLs in your sitemap.
- Keep collection titles descriptive rather than seasonal. New In is not a category an agent can map a shopper request onto.
What Ottom looks at
Ottom only makes this judgement when it can see the catalogue, which means when a feed is available and it holds at least three products. A store with two products has no category structure to lack, and saying otherwise would be a finding about the store being small.
Questions
Can good site search replace a category structure?
Only if it is reachable as a URL an agent can construct and returns readable results without running scripts. Many store searches meet neither condition: they post a form rather than accepting a query string, or they render results in the browser after the page has loaded. A search like that is excellent for the shoppers who use it and invisible to anything reading the page, so it does not replace a category structure or a feed.
How granular should store categories be for agents?
Granular enough that a shopper request maps onto one. If a customer would say it out loud, walking boots, waterproof jackets, cafetieres, it should probably be a category. The failure is not usually too many categories, it is one enormous one: a shop with four hundred products under Products has given an agent nothing to narrow with, so it either opens everything or gives up and asks somewhere else.