Back to blog

The Collection Page Is the Page AI Assistants Want to Recommend

Oct 18, 2026

A rounded shop window lit by a spotlight from above, with a vase, a jug and two small objects arranged on its shelf, surrounded by smaller empty windows in shadow.

Ask an AI assistant about one exact product and it wants a product page. But most shopping questions aren't that narrow: “good gifts for a new runner under $100”, “what do I need for my first camping trip”. For those, the most useful page to point at is one that has already gathered the options and explained them. That page is a collection.

Most collection pages are a title and a grid. For a person browsing, that's fine. For an assistant, it is a list of links with no reason attached.

What a recommendable collection page has

A single page card with three short text bars at the top and a grid of nine tiles below it, each tile holding a simple shape.
A few lines of real description above the grid is what turns a list of links into an answer.
  • A name that says who it is for, not only what is in it.
  • A real description: a few short lines on who it is for, what ties the products together and how to choose between them.
  • A search title and meta description written for the question, not the category.
  • Products that truly belong. A tight 20 beats a loose 200.
  • Structured data that says “this page is a collection of these products”.

The markup: CollectionPage and ItemList

One large circle at the top connected by curved lines to a row of five smaller circles beneath it, over a faint grid.
CollectionPage says what the page is. ItemList says what is on it, in order.

Structured data usually comes up for product pages, but schema.org has types for list pages too. CollectionPage says what the page is, and an ItemList with one ListItem per product says what is on it and in what order. A trimmed example:

{
  "@context": "https://schema.org",
  "@type": "CollectionPage",
  "name": "Rainy Day Commuter",
  "description": "Waterproof, reflective gear for riding to work in the rain.",
  "url": "https://example.com/collections/rainy-day-commuter",
  "mainEntity": {
    "@type": "ItemList",
    "numberOfItems": 2,
    "itemListElement": [
      { "@type": "ListItem", "position": 1, "url": "https://example.com/products/commuter-shell" },
      { "@type": "ListItem", "position": 2, "url": "https://example.com/products/reflective-pannier" }
    ]
  }
}

Plenty of themes add Product markup to product pages and nothing at all to collections. To check yours, open a collection page, view its source and search for “application/ld+json”.

Writing the description: a three-line recipe

  1. Who it is for, and the situation they are in.
  2. What ties these products together: the one shared feature that matters.
  3. How to choose: one sentence of honest guidance.

For anyone who bikes to work and refuses to arrive soaked. Everything here is waterproof, reflective and packs small enough for a pannier. Short ride? Start with the shell. Longer than 30 minutes? Add the overtrousers.

Where Themes fits

An open arched doorway glowing white, with small swirls of light streaming in from all around it.
Every approved theme can become a collection, on your schedule.

In CortexGuard's new Themes page, every approved theme can become a collection. CortexGuard improves the description and search fields of the collection that already covers the theme best, or creates a new one that stays a draft until you publish it. The storefront embed then marks theme collections up as a CollectionPage with an ItemList, and you can switch that off any time under Settings, Structured data.

Not ready for Themes? Everything above works by hand, one collection at a time. Start with your top three. And to see what assistants read on your store today, run a free scan at cortexcommerce.ai/scan.