schema.org/ThingNo rich result
Thing schema
The root schema.org type. The fallback when nothing more specific fits.
Where to use it
about references, and as a last resort.
A complete example
Valid as written, with every required property and the recommended ones that carry real information.
thing.json
{
"@context": "https://schema.org",
"@type": "Thing",
"name": "Acme Reference",
"description": "A one sentence description that restates its own subject.",
"url": "https://www.seoforsolos.com/example",
"sameAs": [
"https://www.seoforsolos.com"
]
}Properties
| Property | Status |
|---|---|
name | Required |
description | Recommended |
url | Recommended |
sameAs | Recommended |
The three mistakes this type attracts
- 01Using Thing where a specific type exists, which wastes the markup.
- 02Emitting it with only a name and no context.
- 03Using it as the top-level type of a page.
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 Thing schema type for?
The root schema.org type. The fallback when nothing more specific fits. Use it on: about references, and as a last resort.
Which Thing properties are required?
Thing requires one property: name. It also recommends 3: description, url, sameAs.
Does Thing produce a rich result?
Thing 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 Thing mistake?
The most common Thing mistake is: Using Thing where a specific type exists, which wastes the markup.