SEO · CONTENT · AEO · 11 FEBRUARY 2025 · 8 MIN READ
Collection pages are your best SEO asset
Product pages chase terms nobody searches. Collections match how people actually look for things — and most stores ship them as a bare grid.
Optimise collection pages the way you would optimise a landing page: one clear h1, a short opening paragraph that answers what the collection is and who it suits, a sane faceted-navigation setup, and internal links out to the narrower collections below it. Collections match the way people search — a category plus a qualifier, "waterproof walking boots", not a product name — and unlike a product page, a collection survives the product going out of stock. Most Shopify stores ship them as a title, a grid and nothing else, which is why the ones with 200 words of real copy outrank them.
IN SHORT
- Search demand sits at the category level: people search "linen shirts men" far more than they search any single shirt.
- A collection page is stable. A product page dies with the product, taking its rankings and links with it.
- The minimum viable collection page is an h1, an intro that answers a question, the grid, and links to narrower collections.
- Faceted navigation is the single biggest crawl problem on a Shopify store, and the fix is choosing which facets get indexable URLs.
- A collection with fewer than about five products is usually a thin page — merge it rather than publish it.
Why the category page wins the search
Type what a customer types. Almost nobody searches for a product name unless they already know the brand — and if they already know the brand, you have them. The volume sits one level up, at the category plus a qualifier: "waterproof walking boots", "gifts for new parents", "linen shirts men". Those are collection pages, not product pages.
The second reason is durability. A product page has a lifespan. It sells out, the supplier changes, the line is discontinued, and the page either 404s or redirects — and whatever authority it had accumulated is now a redirect chain. A collection page for the same category outlives every product in it. Links earned to it keep working. That makes the collection the right place to spend effort you only want to spend once.
The third is that a collection can hold content a product page structurally cannot. A product page is a spec sheet with a buy button; adding 400 words of buying guidance to it fights the conversion job it is doing. A collection page has room above and below the grid for exactly that guidance, and the guidance is what answer engines lift.
What a collection page needs, in order
Most Shopify themes give you a title and a grid. That is the starting point, not the page.
- One h1 that matches the search, not the internal taxonomy. "Walking boots" beats "SS25 Footwear — Outdoor".
- An opening paragraph of two or three sentences that answers what this collection is and who it is for. This is the paragraph that gets quoted.
- The grid, with enough products to justify the page existing.
- A short buying-guidance block below the grid — how to choose, what the differences mean, what to avoid.
- Links out to the narrower collections beneath this one, in prose or as cards, not only in the sidebar facets.
- Two or three FAQs with schema, answering the questions the sales team actually gets.
The copy goes above the grid, and it should be short
There is a habit, inherited from a decade of SEO advice, of dumping 800 words underneath the product grid where no human will ever read them. It is not 2014. That block is ignored by shoppers and discounted by search engines, and it makes the page slower.
Put two or three sentences above the grid, where they are read, and the longer guidance below it. The test for the opening paragraph: if a search engine quoted it on its own, with no page around it, would it answer the question? That is the same test the rest of this site applies to a service page, and it is the whole of what people now call answer engine optimisation.
Write it once, properly, for the twenty collections that carry your traffic. Do not write it badly for two hundred.
Faceted navigation is where the crawl budget goes to die
Shopify generates a URL for almost every filter combination a shopper can click. Colour, size, price band, availability, sort order — multiply them together and a store with forty products can produce tens of thousands of crawlable URLs, nearly all of them near-duplicates of each other.
The decision to make is which facets deserve to be real, indexable pages, and the answer is: the ones with search demand behind them. "Black walking boots" is a search. "Walking boots sorted by price descending, in stock, size 9" is not. The first deserves its own collection with its own copy; the rest should be reachable but not indexable.
This is one of those jobs where the right answer is boring and specific to your catalogue, which is why it is worth doing once with someone looking at your actual Search Console data rather than applying a generic rule.
When not to make a collection
The instinct once this clicks is to create a collection for every permutation, because each one is a page and pages are traffic. They are not. A collection with three products in it is a thin page, and a hundred of them is a pattern search engines recognise and discount across the whole site.
The rule of thumb we use: if a collection has fewer than about five products, or if its copy would be a rewording of its parent, it should not exist as an indexable page. Merge it upward. You can still offer it as a filter.
The same applies to seasonal collections. "Summer 2024" earns its keep for one summer and then becomes a page that says nothing, linked from nowhere. Either refresh it annually under a stable URL — /collections/summer — or let it go.
Questions this raises
How do you optimise Shopify collection pages for search?
Give each collection a single h1 that matches the phrase people search, two or three sentences above the grid that answer what the collection is and who it suits, longer buying guidance below the grid, internal links to the narrower collections under it, and two or three FAQs marked up with FAQPage schema. Then decide which filter combinations deserve indexable URLs of their own.
Should collection copy go above or below the products?
Both, split by length. Two or three sentences above the grid, where shoppers and answer engines actually read them, and the longer guidance below. A single 800-word block under the grid is the old pattern and it does nothing for either audience.
How many products should a collection have?
Enough that the page is worth landing on — around five is the point below which it usually reads as thin. Fewer than that and the collection is better merged into its parent and offered as a filter instead of a page.
Do filtered collection URLs get indexed?
They can, and that is the problem. Filter combinations multiply into thousands of near-duplicate URLs. Pick the handful of facets with real search demand behind them, give those proper collections with their own copy, and keep the rest crawlable but out of the index.
Are collection pages more important than product pages?
For search, usually yes. Category-level phrases carry most of the demand, and a collection outlives the products inside it, so the work you put into one keeps paying after the catalogue turns over. Product pages matter enormously for conversion once someone arrives.
NEXT STEP
Free store audit
A senior Shopify engineer reviews your storefront, theme performance and checkout, then sends a prioritised list of fixes.