Collection Page Schema: A Simple Guide for E-Commerce SEO
If you run an online store, your category pages — also called collection pages — are often your highest-traffic landing pages. Yet most e-commerce sites leave a major SEO opportunity untouched on these pages: collection page schema.
Structured data helps search engines understand what your pages contain. When applied correctly to collection pages, it can improve your visibility in Google Search, unlock rich results, and give you an edge over competitors who haven't bothered. This guide covers everything you need to know in plain English.
What Is Collection Page Schema?
A collection page groups related products together — think "Men's Sneakers" or "Kitchen Appliances." Collection page schema is structured data, written in JSON-LD format, that you add to these pages to tell Google exactly what the page is and what products it contains.
It uses the CollectionPage type from Schema.org, which is a subtype of WebPage. Inside it, you nest an ItemList that references each product individually. This gives Google a machine-readable map of your catalog — something it simply cannot get from reading your HTML alone.
This is different from product schema, which belongs on individual product detail pages. Both are important, but they serve different purposes.
Key Properties to Include
When building your collection page schema, focus on these core properties:
- @type — Set to CollectionPage
- name — The collection's title, e.g., "Women's Running Shoes"
- url — The full, absolute URL of the page
- description — A brief summary of what the collection contains
- breadcrumb — A BreadcrumbList showing the page's place in your site hierarchy (use our breadcrumb schema generator to build this quickly)
- mainEntity — An ItemList containing each product, with name, url, offers (price + availability), and optionally aggregateRating
The more complete your data, the higher your chances of qualifying for rich results in Google Search.
How to Implement It
Google recommends JSON-LD, and it's the easiest format to work with. You add a <script type="application/ld+json"> block inside the <head> of your collection page — no changes to your HTML structure required.
On Shopify: Add the schema via your collection.liquid template using a Liquid loop over collection.products. This makes it dynamic — the schema updates automatically when products change. Our Shopify schema markup guide walks through the exact steps.
On WordPress/WooCommerce: Add it via your category template or use a plugin. See our WordPress schema markup guide for details.
After adding schema, always run it through the Schema Markup Validator to catch any errors before Google does.
Common Mistakes & Final Thoughts
Before you go live, watch out for these common errors:
- Using relative URLs — All URLs in your schema must be absolute (e.g., https://yourstore.com/collections/shoes, not /collections/shoes)
- Outdated availability data — If your schema says InStock but the product is sold out, Google will flag the mismatch
- Wrong schema type — Using WebPage instead of CollectionPage means you miss out on category-specific rich result eligibility
- No validation after theme updates — Platform updates can silently break your schema; always re-test after changes
Collection page schema is one of the simplest wins in e-commerce SEO, yet most stores skip it entirely. If you want to understand the full landscape of structured data options available to you, our types of schema markup guide is a great next step. Start with your top-traffic collection pages, validate your implementation, and let the structured data do the work.