Quick answer: Collection pages usually have more search volume than any individual product, because people search categories ("womens walking boots") far more than SKUs. Shopify's default collection page is a grid with no copy, which is why they rarely rank. Adding a real intro, a sensible H1 and internal links is most of the work.

Product pages get all the attention and collection pages get the traffic. A store selling forty kinds of walking boot will get more search demand for the category term than for all forty products combined, and the page that should capture it is typically a bare product grid.

Why the default page does not rank

Shopify renders a collection as a title and a grid. There is no body copy unless someone writes it, and the collection description field is empty on most stores.

That leaves Google with a page whose only unique text is the product names — which appear on the product pages too. There is nothing on it to rank.

What to add, in order of impact

An intro that answers the category question. Two or three paragraphs above or below the grid covering what to consider when choosing, who each option suits, and the distinction shoppers get wrong. This is also the text AI engines quote when asked to recommend.

An H1 that matches the search term. Shopify uses the collection title as the H1. "Boots" is a catalogue label; "Women's Walking Boots" is a search term. Rename the collection or override the heading.

Internal links to the products that matter. The grid links to everything equally. A short "most popular" or "best for wet weather" paragraph with three or four inline links tells Google which products the category is really about.

A meta description written for the click. The default is empty, so Google composes one from the grid — usually a list of product names, which reads as noise.

The filtered-URL problem

Tag filters generate a URL per combination, each self-canonical, each nearly identical. On a store with several tag dimensions this is hundreds of thin pages competing with the parent.

The decision is per-filter: if the filtered view matches a real search phrase, give it a unique heading and intro and let it stand as its own page. If it does not, canonicalise it to the parent. Doing neither is what produces the "Duplicate, Google chose different canonical" reports in Search Console — see Shopify canonical tags.

Situation Correct Action Result of Doing Nothing
Filtered view matches a real search phrase Give it a unique heading and intro; let it stand as its own page Google reports "Duplicate, Google chose different canonical" in Search Console
Filtered view does not match a real search phrase Canonicalise it to the parent Hundreds of thin pages compete with the parent collection page

Sequencing it

Take the five collections with the most products or the most revenue. Write intros for those. Leave the rest until the first five show movement.

Writing forty collection intros before checking whether any of them rank is the usual way this project dies.

Related