Collection page SEO: templates that rank

Short answer

Default Shopify collection pages ship as bare product grids with no copy and no schema. To rank them you need three things: 80 words of unique intro copy above the grid, 300-500 words below, and ItemList schema. Do that on your top 30 collections first - it usually lifts collection-page sessions 40-90% inside 90 days.

Why collections don't rank by default

Google treats a page with 12 product cards, an H1 and no other content as thin. It ranks Amazon, John Lewis or ASOS instead - all of which have thousands of internal links, review-rich cards, and category copy Google can actually parse. Closing the gap doesn't require matching Amazon; it requires giving Google something to rank.

The collection page template

1. H1: match search intent, not just internal taxonomy ("Men's Black Running Shoes - UK").
2. Intro copy (80 words above grid): what's in the collection, who it's for, one differentiator.
3. Product grid: default Shopify layout is fine.
4. Body copy (300-500 words below grid): buying guide, materials context, size/fit notes, care.
5. FAQ block (3-5 questions): answers the top informational queries in the SERP.
6. Internal links: to adjacent collections, parent category, top 3 guide posts.

Copy placement matters

Some teams push all collection copy below the grid to preserve the merch view. This is a mistake. Google trusts above-the-fold content more heavily. The split is 80 words above (short, tight, keyword-primary) and 300-500 words below (deeper, useful, long-tail).

ItemList schema

Add to your collection template:

{
  "@context": "https://schema.org",
  "@type": "ItemList",
  "itemListElement": [
    {% for product in collection.products limit: 24 %}
    {
      "@type": "ListItem",
      "position": {{ forloop.index }},
      "url": "{{ shop.url }}{{ product.url }}",
      "name": "{{ product.title }}"
    }{% unless forloop.last %},{% endunless %}
    {% endfor %}
  ]
}

Faceted navigation strategy

Which filters should be indexable? Rule of thumb: if a filter combination has real search demand and would earn a distinct H1, index it as a dedicated collection. If it's just a UX filter with no demand, noindex it.

• Index: "Men's Running Shoes", "Men's Black Running Shoes" (both real queries).
• Noindex: "Men's Running Shoes sorted by newest".
• Block via robots: any filter combination with no demand and infinite permutations.

Internal linking from collections

Collections should link to parent categories, sibling collections and 2-3 related guide posts. This builds topical clusters Google can trust. A "Men's Black Running Shoes" collection should link to "Men's Running Shoes" (parent), "Women's Black Running Shoes" (sibling), and "How to choose running shoes" (guide).

Common mistakes

• Creating one collection per keyword permutation - creates duplicate content between near-identical URLs.
• Copy 100% below the fold - Google discounts what it doesn't see in the first viewport.
• No ItemList schema - misses a free rich-result opportunity.
• No FAQ block - misses the featured-snippet opportunity for buying queries.