CollectionPage + ItemList Schema

By Amit Patel

CollectionPage marks a page as a curated collection — a hub, category, or list — and ItemList enumerates the entries on it in order, giving Google a structured view of what the page pulls together. Unlike the foundational entity types, these are ones you often can add yourself, because most SEO plugins do not generate them for custom hub pages. They power list understanding and, in some cases, carousels.

What These Types Do

CollectionPage says “this page is a collection”; ItemList says “here are its members, in this order.” Together they help Google understand hub and category pages as structured lists rather than generic pages.

This is the exact markup the blog pillars on this site use — each pillar is a CollectionPage whose mainEntity is an ItemList of its child articles. It is one of the types this cluster’s own guidance says you may safely add, alongside FAQ, because it does not conflict with the platform-owned Article and Organization entities.

How CollectionPage and ItemList Nest

The clean pattern is a CollectionPage with a mainEntity that is an ItemList, whose itemListElement is an array of ListItems — each with a position, url, and name, exactly like a BreadcrumbList but describing content rather than navigation.

Positions start at 1 and should reflect the intended reading or ranking order. You can point each ListItem’s url at the member page. The structure mirrors BreadcrumbList; the difference is semantic — a collection of content versus a navigation trail.

The Carousel Connection

For certain content types — recipes, courses, movies, restaurants — an ItemList of eligible items can make a page eligible for a host carousel rich result, where Google shows a swipeable set from your site.

The carousel only applies to specific supported types and requires each item to also carry its own valid markup; a generic list of blog links will not produce a carousel. Check Google’s list-format documentation before expecting one, and validate with the Rich Results Test.

When to Add It

Add CollectionPage + ItemList to genuine hub, category, and curated-list pages where your platform does not already emit it — it clarifies structure and is one of the safe, additive types.

Do not force it onto ordinary article pages, and do not duplicate it if a plugin already outputs it for archives. It pairs naturally with strong internal linking and hub architecture from the Content Strategy pillar.

Example Markup

A CollectionPage wrapping an ItemList (shown as code):

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "CollectionPage",
  "name": "Schema Markup References",
  "mainEntity": {
    "@type": "ItemList",
    "itemListElement": [
      { "@type": "ListItem", "position": 1, "url": "https://example.com/a/", "name": "Guide A" },
      { "@type": "ListItem", "position": 2, "url": "https://example.com/b/", "name": "Guide B" }
    ]
  }
}
</script>

See JSON-LD vs Microdata for the format.

Frequently Asked Questions

The Bottom Line

CollectionPage and ItemList are the structured-data types for pages that gather things together — hubs, categories, curated lists. They are safe to add where your platform doesn’t, they clarify structure, and for a few content types they unlock carousels. Use them on real collections and keep the positions honest, following the ownership guidance across the schema cluster.