← Back to all guides

Classification: Optional · Last updated: April 2026

CollectionPage Schema for Shopify: The Complete Guide

CollectionPage schema markup identifies a page as containing a curated collection of items. For Shopify stores, this applies to your collection pages — the category pages that group products by type, season, theme, or any other criteria you define.

What Is CollectionPage Schema?

CollectionPage (schema.org/CollectionPage) is a subtype of WebPage that specifically indicates a page containing a curated collection of items. It tells Google that this page isn't a standalone content page or a product page — it's an index of related items.

CollectionPage is part of the schema.org vocabulary but Google does not currently offer a specific rich result type for CollectionPage. This means implementing it won't unlock a visual search enhancement the way Product or FAQ schema does. However, it provides supplementary structural data that helps Google understand your site's content architecture.

Why CollectionPage Is Optional

Schema Clinic classifies CollectionPage as Optional because:

• Google does not offer a specific rich result for CollectionPage markup
• Google can already identify collection/category pages through URL patterns, internal linking, and page content
• The SEO benefit is supplementary — it reinforces what Google likely already understands about your collection pages
• Missing CollectionPage schema does not result in any visible loss in search results

That said, CollectionPage schema is not harmful and can improve Google's understanding of your site structure, particularly for stores with complex or non-standard collection hierarchies.

Properties

CollectionPage inherits all properties from WebPage. The most relevant properties for Shopify stores include:

• @type — "CollectionPage"
• name — The collection name (e.g., "Summer Collection", "Women's Dresses")
• description — The collection description as entered in your Shopify admin
• url — The canonical URL of the collection page
• mainEntity — Can reference an ItemList of the products in the collection
• isPartOf — Reference to your WebSite entity via @id
• breadcrumb — Reference to a BreadcrumbList for the collection page

JSON-LD Example for Shopify

{
  "@context": "https://schema.org",
  "@type": "CollectionPage",
  "@id": "https://yourstore.com/collections/summer-2026/#collection",
  "name": "Summer 2026 Collection",
  "description": "Our curated selection of lightweight summer essentials.",
  "url": "https://yourstore.com/collections/summer-2026",
  "isPartOf": {
    "@id": "https://yourstore.com/#website"
  }
}

CollectionPage vs ItemList

CollectionPage and ItemList are often confused but serve different purposes:

• CollectionPage — Describes the page itself as a collection/category page. It's a page-level annotation
• ItemList — Describes a list of specific items on the page. It's a content-level annotation that can exist within a CollectionPage

You can use both together: CollectionPage identifies the page type, and ItemList (as the mainEntity) describes the items it contains. However, ItemList only triggers rich results for specific content types (courses, movies, recipes, restaurants) — not products.

When to Implement CollectionPage

Consider adding CollectionPage schema if:

• You have a well-organised collection structure that mirrors your business categories
• Your collection pages have unique, descriptive content (not just product grids)
• You want to reinforce the hierarchical relationship between your homepage, collections, and products
• You're already implementing other schema types and want comprehensive coverage

How Schema Clinic Handles CollectionPage

Schema Clinic detects CollectionPage schema on collection URLs but does not flag its absence as an error or recommendation, since it's classified as Optional. If present, the audit validates property correctness and checks for conflicts with other schema on the same page.

← Back to all guides