Structured Data
DefinedTerm
DefinedTerm is a Schema.org structured data type used to identify a specific term, its definition, and its parent glossary or dictionary on a webpage.
also called: DefinedTermSet
// definition
Far from a generic layout element or standard real-world entity, this structured data type explicitly connects a technical word to its formal definition and parent dictionary. Rather than displaying unformatted text, it encapsulates lexical descriptions so automated crawlers recognize specialized jargon. Developers implement this vocabulary within HyperText Markup Language, or HTML, to clarify complex documentation terms.
Automated search engine crawlers scan embedded code to extract term details and resolve semantic ambiguity. Linking entries directly to a parent catalog helps search engines index specialized concepts within internal knowledge graphs accurately.
{
"@context": "https://schema.org",
"@type": "DefinedTerm",
"name": "APR",
"termCode": "apr-01",
"description": "Annual Percentage Rate measuring yearly loan cost.",
"inDefinedTermSet": "https://creditunion.example.org/glossary"
}// how it works
Implementation begins when a regional credit union publishes specialized financial terms on its website to explain complex products. Web developers construct structured scripts containing the term name, unique identifier, textual definition, and parent glossary link. Developers embed this code directly into HTML pages.
Automated search engine crawlers scan the web page and detect the structured vocabulary. Crawlers extract specific details and resolve semantic ambiguity. Finally, search engines index these specialized concepts accurately, connecting them directly to internal knowledge graphs.
// common mistakes
One common mistake is substituting a general Entity schema for a lexical definition, which prevents search engines from recognizing formal glossary vocabulary. Another error is omitting the parent DefinedTermSet property, breaking the contextual relationship between an entry and its catalog.
Finally, relying solely on standard HTML presentation tags without markup limits crawler parsing. As a direct consequence, automated engines fail to resolve technical jargon, reducing search visibility for niche query terms across knowledge bases.
// related terms
As a component of Schema.org, DefinedTerm fits into the broader ecosystem of Schema markup and Structured data. Publishers implement this type via JSON-LD or Microdata alongside Organization schema, LocalBusiness schema, BreadcrumbList schema, FAQPage schema, and BlogPosting schema to describe content. Declaring these items helps search engines process specialized entities, potentially generating a Rich result.
Questions and Answers
- What is the main purpose of using DefinedTerm markup on a website?
- The primary purpose is identifying precise lexical definitions and connecting technical words to parent reference glossaries for search indexing. By explicitly marking specialized jargon, publishers help search crawlers resolve semantic ambiguity and index complex terms accurately within knowledge graphs.
- How do developers add DefinedTerm structured data to a web page?
- Developers add this markup by writing scripts in JSON-LD or Microdata and embedding them directly into HTML page code. The code contains key details including the term name, description, code, and parent catalog URL for search engine crawlers to extract.
- Why should someone avoid using a general entity schema for glossary terms?
- A general entity represents a distinct real-world object, whereas this specialized structure encapsulates a dictionary definition. Using a general entity prevents search engines from identifying formal catalog entries, breaking the contextual link between a specific term and its parent glossary.
- What happens when the parent catalog property is omitted from DefinedTerm markup?
- Omitting the parent set property breaks the contextual link between an entry and its reference set. Search engines cannot confirm which dictionary owns the terminology, reducing crawler ability to resolve domain-specific jargon and lowering search visibility for niche terms.
