DefinedTermSet schema

Where to use it

Glossary index pages.

A complete example

Valid as written, with every required property and the recommended ones that carry real information.

{
  "@context": "https://schema.org",
  "@type": "DefinedTermSet",
  "name": "Acme Reference",
  "description": "A one sentence description that restates its own subject.",
  "hasDefinedTerm": [
    {
      "@type": "DefinedTerm",
      "@id": "https://www.seoforsolos.com/glossary/canonical-url#term",
      "name": "Canonical URL",
      "description": "The address a site declares to be authoritative for a page."
    }
  ],
  "url": "https://www.seoforsolos.com/example"
}

Properties

The three mistakes this type attracts

1. 01Listing only some terms, so the set contradicts the page.
2. 02Duplicating each term as both a nested node and a separate top-level node with the same @id.
3. 03Omitting the set entirely and emitting 80 unconnected DefinedTerms.

Related types

• QAPage
• Question
• Answer
• SpeakableSpecification
• Product
• Offer

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