schema.org/ListItemNo rich result
ListItem schema
One element of an ItemList or BreadcrumbList.
Where to use it
Nested inside a list type.
A complete example
Valid as written, with every required property and the recommended ones that carry real information.
list-item.json
{
"@context": "https://schema.org",
"@type": "ListItem",
"position": 1,
"name": "Acme Reference",
"item": "https://www.seoforsolos.com/example",
"url": "https://www.seoforsolos.com/example"
}Properties
| Property | Status |
|---|---|
position | Required |
name | Recommended |
item | Recommended |
url | Recommended |
The three mistakes this type attracts
- 01position starting at 0.
- 02Both item and url set with different values.
- 03Omitting name, leaving the entry unlabelled.
Related types
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
Questions
What is the ListItem schema type for?
One element of an ItemList or BreadcrumbList. Use it on: nested inside a list type.
Which ListItem properties are required?
ListItem requires one property: position. It also recommends 3: name, item, url.
Does ListItem produce a rich result?
ListItem does not produce a Google rich result. It is still worth shipping, because its value is entity resolution and answer extraction rather than search result presentation.
What is the most common ListItem mistake?
The most common ListItem mistake is: position starting at 0.