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": 12,
  "itemListOrder": "A real itemListOrder value",
  "name": "Acme Reference"
}

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

• WebSite
• WebPage
• BreadcrumbList
• CollectionPage
• SiteNavigationElement
• Article

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