schema.org/TableNo rich result
Table schema
A tabular data structure that is the page's primary content, as opposed to a layout table.
Where to use it
Pages whose primary content is a table.
A complete example
Valid as written, with every required property and the recommended ones that carry real information.
table.json
{
"@context": "https://schema.org",
"@type": "Table",
"about": {
"@type": "Thing",
"name": "Structured data"
},
"name": "Acme Reference"
}Properties
| Property | Status |
|---|---|
about | Required |
name | Recommended |
The three mistakes this type attracts
- 01Marking up layout tables.
- 02Using it instead of Dataset for published data.
- 03Omitting about, which leaves the table's subject unstated.
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 Table schema type for?
A tabular data structure that is the page's primary content, as opposed to a layout table. Use it on: pages whose primary content is a table.
Which Table properties are required?
Table requires one property: about. It also recommends 1: name.
Does Table produce a rich result?
Table 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 Table mistake?
The most common Table mistake is: Marking up layout tables.