Learn / Fixes
How to structure collections for agent discovery
Collections organised around how a business buys and merchandises stock rarely match how shoppers describe what they want, so a request for a kind of product resolves to a homepage rather than to a set of yours. Structuring for discovery means having a real page for the categories people actually ask for, and making sure those pages are listed, crawlable and readable without scripts.
Most catalogues are organised around how the business buys and merchandises stock. Shoppers do not ask that way, and neither do the agents acting for them, so a request for a kind of product resolves to your homepage rather than to a set of yours.
This is no category structure.
Structure for the question, not the stockroom
Your internal taxonomy can stay exactly as it is. What is missing is a real page for the categories people actually ask for, with real products in it and a description that states what belongs there.
The test is simple: take the five ways customers describe what they want, in their words, and check that each one has a page. Most stores find two or three that do not exist, and those are usually the ones with commercial value.
A collection page has to be readable
A page that only fills with products once a script runs is empty to anything reading your markup, which means the category exists and its membership does not.
- Products present in the served markup, not fetched after load.
- A description that states what the collection contains in plain terms.
- Pagination as real links rather than an infinite scroll with no crawlable URLs.
- The collection listed in your sitemap alongside your products.
Facets need URLs to exist
Filters are valuable to shoppers and usually invisible beyond them, because a filtered view lives behind a query string that nothing links to and nothing lists. If a facet matters commercially, waterproof jackets rather than jackets, give it a genuine URL and treat it as a collection.
Do this for the handful that matter rather than for every combination. A thousand generated pages with three products each is a worse outcome than the problem.
Structure is not a substitute for the feed
Good collections help an agent that arrived at your store and needs to navigate it. A feed helps an agent decide whether to consider you at all, and it is the cheaper path.
Do both, and do the feed first: how to publish a product feed for AI agents.
Questions
Do I need to restructure my whole catalogue?
No. Add pages for the ways people ask that you do not currently have, and leave your internal structure alone. The two do different jobs and there is no requirement that they match.
Is this just more landing pages?
Only if you make them thin. A collection page with real products, a description that states what belongs in it, and stable membership is a useful page. One generated for a keyword with three loosely related items is not, and reads as filler to everything looking at it.
What about filters and facets?
Useful to shoppers, usually invisible to agents, because a filtered view often lives behind a query string that is not linked, not listed and not crawlable. If a facet matters commercially, give it a real URL.