schema.org/DefinedTermNo rich result
DefinedTerm schema
A term with a definition, belonging to a defined set.
Where to use it
Glossary entry pages.
A complete example
Valid as written, with every required property and the recommended ones that carry real information.
defined-term.json
{
"@context": "https://schema.org",
"@type": "DefinedTerm",
"name": "Acme Reference",
"description": "A one sentence description that restates its own subject.",
"termCode": "canonical-url",
"inDefinedTermSet": {
"@id": "https://www.seoforsolos.com/glossary#termset"
},
"url": "https://www.seoforsolos.com/example"
}Properties
| Property | Status |
|---|---|
name | Required |
description | Recommended |
termCode | Recommended |
inDefinedTermSet | Recommended |
url | Recommended |
The three mistakes this type attracts
- 01Emitting terms with no inDefinedTermSet, producing unconnected definitions.
- 02termCode that changes between builds.
- 03Using it for a general concept page rather than a defined term.
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 DefinedTerm schema type for?
A term with a definition, belonging to a defined set. Use it on: glossary entry pages.
Which DefinedTerm properties are required?
DefinedTerm requires one property: name. It also recommends 4: description, termCode, inDefinedTermSet, url.
Does DefinedTerm produce a rich result?
DefinedTerm 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 DefinedTerm mistake?
The most common DefinedTerm mistake is: Emitting terms with no inDefinedTermSet, producing unconnected definitions.