schema.org — ItemList / ListItem / Product / Offer types exist precisely to mark up individual records and lists as machine-readable structured data
Summary
Claim: The schema.org Product, ItemList, ListItem, and Offer types exist precisely to mark up individual records and lists of records as machine-readable structured data. ItemList "represents an ordered or unordered list of items," and each ListItem can carry its own URL and nested Product/Offer data.
Source: schema.org/ItemList, schema.org/Product, schema.org/ListItem (development version dated "Google — May 2026").
Confidence: Verified — primary standards source.
Why this matters for Candid: The vocabulary for "catalogue of records, each individually addressable" is already standardised. We are not asking clients to invent structure — we are pointing them at the standard the search engines themselves wrote. Cross-link schema.org — founded jointly by Bing, Google, and Yahoo! in 2011; Yandex joined Nov 2011 for the standards-body lineage.
Related entries
Related
Referenced by (6)
- reference Research brief: the searchable, structured catalogue as a working tool — when records-not-prose pays off (June 2026) relates-to
- reference schema.org — founded jointly by Bing, Google, and Yahoo! in 2011; Yandex joined Nov 2011 relates-to
- reference Google Search Central — structured data labels each individual element so users can search by ingredient, calorie count, cook time relates-to
- reference Google Search Central — product rich results require "a distinct URL" per product (or per variant); confirms one findable page per record relates-to
- reference Bing — supports JSON-LD, schema.org, Microdata, Microformats, Open Graph, RDFa via the Markup Validator (August 2018) relates-to
- rule R3 — One indexable page per record (distinct URL per item / variant) — per Google's merchant-listing guidance depends-on