CollectionPage schema

Where to use it

Blog index, category pages, glossary index.

A complete example

Valid as written, with every required property and the recommended ones that carry real information.

{
  "@context": "https://schema.org",
  "@type": "CollectionPage",
  "url": "https://www.seoforsolos.com/example",
  "name": "Acme Reference",
  "description": "A one sentence description that restates its own subject.",
  "isPartOf": {
    "@id": "https://www.seoforsolos.com/#website"
  },
  "mainEntity": {
    "@type": "Person",
    "name": "A Real Person",
    "url": "https://www.seoforsolos.com/about"
  },
  "breadcrumb": {
    "@id": "https://www.seoforsolos.com/example#breadcrumb"
  }
}

Properties

The three mistakes this type attracts

1. 01Using CollectionPage for a page with substantial original content of its own.
2. 02Omitting mainEntity, which leaves the collection empty.
3. 03Duplicating the ItemList both inline and as a separate node.

Related types

• SiteNavigationElement
• Article
• BlogPosting
• TechArticle
• FAQPage
• HowTo

Where this appears in the playbook

• Structured data: what each type is for and which ones earned their place.
• The schema graph: composing types into one graph with stable identifiers.
• One JSON-LD script per page, holding one @graph
• Stable @id anchors that cross-reference rather than duplicate
• Optional fields are omitted, never emitted as empty strings