A category page earns its place in AI answers by doing the job only a category page can do: showing a buyer the whole range for one need, in a structure a machine can walk, with a short introduction that says who the range is for and how to choose within it. A category page that is only a product grid with no words, no links, and no structure is invisible to an AI system, because there is nothing on it to quote and no path through it to follow.
Category pages usually target the broadest buying queries your store can win, such as running shoes for road running, so they deserve the same care as a product page. The work is structure first, copy second, and crawl control third.
Build the hierarchy a machine can follow
Google's ecommerce guidance describes the site structure as a chain: link from menus to category pages, from category pages to sub-category pages, and from sub-category pages to all product pages. That chain is how a crawler finds your products, and it is how a model learns which pages matter. The more internal links a page has within a site, the more important it looks relative to your other pages, so link your best-selling categories and products more often, including from the homepage.
Use plain HTML links for the chain. A link is an anchor element with an href, and navigation built only with JavaScript click events may not be followed. Check that every product you want indexed is reachable by following links from a category page, because Googlebot does not type queries into your search box to discover products.
Add breadcrumbs on category and product pages, showing the path from the homepage to the current page, such as Home, then Running Shoes, then Road Running Shoes. Add BreadcrumbList markup that mirrors the visible trail, with each item carrying a position, a name, and a URL. The markup tells a machine where the page sits in the site, and it must match the trail a visitor sees.
Give each category page one clear purpose. A category that mixes road running shoes, trail shoes, and casual sneakers in one grid serves no single buyer, and a model cannot describe what the page is for. Split the range where buyers split it, and link the sub-categories from the parent page.
Write an introduction that helps a buyer choose
A category page needs words of its own, not just a product list. Write a short introduction at the top of the page, above the product grid, that answers three questions: who this range is for, what varies within it, and how to choose.
A good introduction for a road running shoe category reads like this: "Road running shoes for daily training on pavement. Cushioned shoes suit long easy runs, responsive shoes suit tempo days, and lightweight shoes suit race day. Start with your weekly distance and your foot strike, then filter by cushion level." That is a passage an AI system can quote, because it answers a real question in words that stand on their own.
Keep the introduction short and specific. A paragraph or two is enough. Name the differences that matter in this category: cushion, drop, weight, width, or surface. Do not repeat the same introduction across categories with the category name swapped in. Each category has its own differences, and a copied introduction tells a system the page has nothing of its own to say.
Put the facts a buyer compares in the product list itself: price, key attributes, and availability, in plain text. Do not hide the price behind a hover or a script. A category page that shows products without prices gives a model nothing to compare.
Control filters so they do not drown the crawl
Filters are the biggest technical risk on a category page. Every combination of size, color, price, and brand can create its own URL, and a category with a large catalog can generate thousands of near-duplicate URLs that waste crawling on pages no buyer needs. Google calls faceted navigation one of the most common sources of overcrawl issues, and its guidance offers two paths.
If a filtered view does not need to appear in search, keep it out of the crawl. Block the filter parameters in robots.txt while leaving the product pages and the unfiltered category page crawlable, or put the filters after a hash in the URL, which Google generally does not crawl. Either way, the filter still works for the shopper, and the crawler spends its time on pages that matter.
If a filtered view should appear in search, treat it as a real page. Give it a clean URL, a unique introduction, and internal links that expose it, and return a 404 for combinations with no results instead of redirecting them. Only a small number of filter combinations deserve this treatment: the ones buyers actually search for, such as a size or a use case with real demand. The rest stay out of the crawl.
Keep the canonical tag on each filtered URL pointed at the representative version, and do not use the first page of a paginated sequence as the canonical for the whole sequence. Give each page of the sequence its own URL and its own canonical, and link the pages in sequence with plain HTML links so a crawler can walk through them.
Mark up the page for what it is
Do not put Product markup on a category page. Google's merchant listing guidance recommends focusing Product markup on product pages instead of pages that list products or a category of products, because merchant listing experiences support pages that focus on a single product. A category page with Product markup for every item in the grid is markup that does not match what the page is.
What a category page can carry is BreadcrumbList markup for its place in the hierarchy, and Organization markup belongs on the homepage or the About page, not repeated here. For the markup on product pages themselves, see our product schema guide.
Keep the page fast and readable. A category page with a large product grid, heavy images, and scripts that delay the content is a page a crawler may not finish reading. Serve the introduction, the product links, and the prices in the HTML the server sends, and let the images and the filters load around them.
The fundamentals
These mechanics are shared across every engine and covered in full in their own guides:
- •The llms.txt format and a complete sample, see our guide to writing a good llms.txt file
- •The markup this engine reads, see our product schema guide
- •The complete crawler rule reference, see our robots.txt guide for AI search
Say you run a running shoe store
Say you sell running shoes, and your road running category page is a grid of forty shoes with no introduction, filters that generate a new URL for every combination of size and color, and Product markup pasted across the whole grid. A buyer asks an assistant for road running shoes for daily training. The assistant retrieves your page, but there is no passage that says who the range is for or how to choose within it, and the crawler that fetched the page spent its time on hundreds of filter URLs instead of the products. You rewrite the page: a short introduction naming the buyer and the differences that matter, sub-category links for cushioned, responsive, and lightweight shoes, plain HTML links to every product, the filter parameters blocked from crawling, and the Product markup removed from the category page and kept on the product pages where it belongs. Nothing else on the site changes. The next crawl finds a page with a clear purpose, a readable introduction, and a clean path to every product in the range.
What this guide does not cover
This guide covers the category page itself. It does not cover product pages, which are our product schema guide and our guide to writing product descriptions, and it does not cover the transaction layer that turns a recommendation into a sale. A category page that is structured, introduced, and crawlable is a page a system can use. It does not promise a citation.
Check your own brand now
Run the free scan. It takes seconds, no signup, and shows whether AI crawlers can read your category pages today: aizii.ai/aeo-scan
Run the free scanSources
- Google Search Central, SEO best practices for ecommerce sites (specific): https://developers.google.com/search/docs/specialty/ecommerce
- Google Search Central, Merchant listing structured data (specific): https://developers.google.com/search/docs/appearance/structured-data/merchant-listing
- Google Search Central, Optimizing your website for generative AI features on Google Search (specific): https://developers.google.com/search/docs/fundamentals/ai-optimization-guide
- Google Search Central, Product structured data (specific): https://developers.google.com/search/docs/appearance/structured-data/product
- Schema.org, BreadcrumbList type (specific): https://schema.org/BreadcrumbList
- Schema.org, ItemList type (general standard): https://schema.org/ItemList
Note: links marked specific point to the page that supports the claim in this guide. Links marked general docs point to the vendor's general docs section for that topic, not to a page that proves every step. Check the vendor docs for the current path before relying on a menu name or click path in this guide.
