Skip to content
SEO4 min read

Shopify SEO: collection pages are the pages you are neglecting

Collection pages capture the highest-intent commercial searches on a Shopify store, and most are shipped with a bare grid and no copy. Here is how to fix them.

Shopyra TeamProduct & Engineering
Share

Most Shopify SEO effort goes into product pages and blog posts. Meanwhile the collection page — the one that should rank for “womens merino base layers”, the highest-commercial-intent search in that category — ships as a title, a grid, and nothing else.

This is backwards. Collection pages are how category searches get satisfied, and category searches are where the money is.

Why collections outrank products for category terms

Search for a category term and look at what ranks. It is almost never a single product page. It is category pages, because they match the intent: the searcher wants to compare options, not buy a specific SKU.

A product page competing for “merino base layers” is competing with one item against pages offering forty. It loses. The collection page is the right page for that query, and on most Shopify stores it is the least developed page on the site.

What a collection page needs

An introduction that is genuinely useful

Not 300 words of keyword-stuffed filler beneath the grid where nobody reads it. Two or three short paragraphs above or beside the grid that help someone choose:

  • What is in this category and how the options differ
  • What to consider when choosing (weight, fit, use case)
  • A pointer to the obvious default for someone who does not want to think

This copy does double duty. It gives search engines something to understand the page by, and it helps the shopper who is genuinely undecided — who is the person the page exists for.

Shopify lets you put this in the collection description field. If your theme renders that description in a tiny box under the header, edit the section to give it room.

A title and meta description written for the query

The default is {{ collection.title }} – {{ shop.name }}. Do better:

{%- if collection.metafields.seo.title -%}
  {{ collection.metafields.seo.title }}
{%- else -%}
  {{ collection.title }} | {{ shop.name }}
{%- endif -%}

A metafield gives you per-collection control without touching code again. Write titles that include the qualifier people actually search — “Merino Base Layers for Women | Free UK Delivery” beats “Base Layers”.

Faceted navigation that does not create a crawl swamp

Shopify’s filter URLs (?filter.v.option.size=M) can generate thousands of near-duplicate URLs. Google will crawl them, find near-identical content, and spend your crawl budget on it.

Two things to do:

  1. Make sure filtered views carry a canonical pointing at the unfiltered collection.
  2. Disallow the filter parameters in robots.txt if you are not deliberately targeting the filtered combinations.

If a specific filtered view does deserve to rank — “black merino base layers” is a real search — do not rely on the parameter URL. Create a real collection for it with its own title, description and canonical.

Structured data

Collection pages support CollectionPage and ItemList markup. This is not a ranking factor on its own, but it helps search engines understand the page as a list of products rather than an undifferentiated blob of text.

{
  "@context": "https://schema.org",
  "@type": "CollectionPage",
  "name": "Women's Merino Base Layers",
  "url": "https://example.com/collections/womens-merino-base-layers",
  "mainEntity": {
    "@type": "ItemList",
    "numberOfItems": 24,
    "itemListElement": [
      { "@type": "ListItem", "position": 1, "url": "https://example.com/products/…" }
    ]
  }
}

Related collections, a link up to the parent category, and links down to sub-collections. Most Shopify stores have a flat collection structure with no internal linking between collections at all, which means every collection is an island reachable only from the nav.

Pagination handled properly

If your collection paginates, each page needs a self-referencing canonical (not one pointing at page 1 — that has been wrong since Google dropped rel=prev/next support). Page 2 is a different page with different products; treat it as one.

Infinite scroll needs paginated URLs behind it or the products beyond the first screen are invisible to crawlers.

Here is the part most stores skip. The collection pages that outperform are usually the ones with a genuine buying guide attached — not a blog post linking to the collection, but content on the collection page itself.

For a base layer collection: a short section on the weight ranges and what conditions each suits. For a coffee collection: the roast levels and what they taste like. This is the content that gets linked to, and the links land on the page you want to rank rather than on a blog post two clicks away.

A realistic order of operations

You probably have more collections than time. Prioritise:

  1. Find your top 10 collections by revenue. Shopify Analytics → Sales by collection.
  2. Search their primary term and see what ranks. If it is competitors’ collection pages, you have a real opportunity.
  3. Write the intro copy for those 10. Two paragraphs each. One afternoon.
  4. Fix titles and meta descriptions on the same 10.
  5. Add structured data site-wide. It is one theme edit.
  6. Sort out filter canonicals and robots rules. Also one edit, and it protects everything else you do.

Then leave it for eight weeks. Collection page improvements do not show up next Tuesday; they show up when the page gets recrawled and re-evaluated, which for a mid-sized store is measured in weeks.

What not to bother with

  • Keyword density. Not a thing. Write for the person choosing.
  • Duplicating the intro copy across collections with the term swapped. Search engines are good at noticing this, and it makes your store worse for humans.
  • Hidden text below the fold. If you are hiding it because it is bad for shoppers, it is not helping.

Collection pages are unglamorous work. They are also, on most Shopify stores, the largest pile of unclaimed organic traffic available.

Read next

All posts

Get started free

Put this into practice

Our apps are built on exactly the principles in these posts — small, fast, theme-native, and honest about what they do.

  • Free to install
  • OS 2.0 app blocks
  • No code required