On this page:
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
Created
updated
CollectionPage Schema for Webflow Websites
CollectionPage schema tells search engines that a page is a listing or index of items. Use this for blog listing pages, CMS category pages, product catalog pages, and any page that aggregates links to individual items. It helps Google understand the page is a navigation hub, not a content destination.
When to Use
- Blog index (/blog) — Yes
- Category page (/blog/category/seo) — Yes
- Product catalog (/products) — Yes
- Author archive (/author/pavel) — Yes
- Search results — No (use SearchResultsPage)
- Individual blog post — No (use BlogPosting)
Fields
- name — Page title (shared)
- description — Page summary (shared)
- url — Page URL (shared)
- primaryImageOfPage — Hero image
- datePublished — Page creation date (shared)
- dateModified — Last update (shared)
- inLanguage — Page language (shared)
- isPartOf — Parent WebSite reference
- breadcrumb — Breadcrumb trail (shared)
Ask AI about this property
I just read https://www.karpi.studio/schema-glossary-types/collection-page about CollectionPage schema for Webflow websites. Help me apply this to my own blog/listing site:
- Which fields to use: `name`, `description`, `url`, `primaryImageOfPage`, `datePublished`, `dateModified`, `inLanguage`, `isPartOf` (parent WebSite), and `breadcrumb`
- A complete JSON-LD example using the @graph format combining CollectionPage with its `breadcrumb` and an `isPartOf` WebSite reference
- How to implement it in Webflow on listing pages — a blog index (/blog), a CMS category page, or a product catalog (/products) — not on individual posts (use BlogPosting) or search results (use SearchResultsPage)
- How to validate it with the Schema.org Validator; there is no dedicated Google rich result for CollectionPage — it helps Google understand the page is a navigation hub rather than a content destination
- The most common mistake: applying CollectionPage to an individual item page instead of a true listing/index page