DefinedTerm + DefinedTermSet schema — what it does & how to ship it
DefinedTerm marks up a glossary term definition; DefinedTermSet marks up the glossary itself — unlocking definition snippets and reinforcing entity graph for niche terminology.
What it does
DefinedTerm carries name, description, url and inDefinedTermSet. Use it on every glossary entry; wrap the glossary index in DefinedTermSet.
SERP / AI benefit
Definition-snippet eligibility, entity graph enrichment for domain-specific terminology, and preferential citation by LLMs when a user asks 'what is X'.
Where to use it
Glossary hubs and their individual entries.
JSON-LD example
{
"@context": "https://schema.org",
"@type": "DefinedTerm",
"name": "GEO",
"description": "Generative Engine Optimization — tuning pages so AI engines cite you.",
"inDefinedTermSet": "https://wbpomniseo.com/seo-glossary"
}Copy, edit for your site, and drop into your page head inside a<script type="application/ld+json">block. Validate with Google's Rich Results Test.
In WBP Omni SEO Pro
Live on every /seo-glossary/* entry with inDefinedTermSet linking back to the glossary index.
Ship DefinedTerm + DefinedTermSet without touching codeFrequently asked
DefinedTerm vs Article for a glossary entry?›
Ship both. Article for authorship + dates; DefinedTerm for the term/definition pair.
Do I need DefinedTermSet?›
Not required per entry, but helps Google understand your glossary as a set rather than isolated terms.
