ItemList schema

Where to use it

Hub pages, category pages, index pages.

A complete example

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

{
  "@context": "https://schema.org",
  "@type": "ItemList",
  "@id": "https://www.seoforsolos.com/#itemlist",
  "itemListElement": [
    {
      "@type": "ListItem",
      "position": 1,
      "name": "First",
      "item": "https://www.seoforsolos.com/first"
    },
    {
      "@type": "ListItem",
      "position": 2,
      "name": "Second"
    }
  ],
  "numberOfItems": 2,
  "itemListOrder": "https://schema.org/ItemListOrderAscending",
  "name": "Acme Reference"
}

Generate a ItemList node with your own values in the schema generator, and lint what your page actually ships with the schema validator.

Properties

The three mistakes this type attracts

1. 01numberOfItems disagreeing with the number of elements actually present.
2. 02Using ItemList for navigation chrome rather than for the page's real content.
3. 03Omitting position on each ListItem in an ordered list.

Related types

• ListItem
• BreadcrumbList
• CollectionPage
• WebSite
• WebPage
• SiteNavigationElement

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
• Does schema markup work? What 42 types on one site actually did: which of these types measurably did anything in production.