Decision Content Optimisation

Should I build a glossary?

When your field is jargon-heavy and you are weighing a glossary or definitions hub.

ID
SS-DE-046
Confidence
Established · 79
Evidence
Established
Updated
2026-07-08

The question

When your field is jargon-heavy and you are weighing a glossary or definitions hub.

Your industry has specialised terminology and you are deciding whether to publish a glossary or definitions section.

Why it matters

A well-built glossary captures definition-stage queries and strengthens entity and topical signals for AI, but a thin auto-generated one creates dozens of low-value pages that dilute quality.

How to decide

IfIf your audience searches for what-is and definition queries in your field
ThenYes - build substantive definition pages that answer and interlink to related topics.
IfIf you want to reinforce entity and topical authority for AI understanding
ThenYes - clear definitions help engines map your expertise and cite you.
IfIf you would only auto-generate one-line stubs at scale
ThenNo - thin definition pages add clutter, not authority.
IfIf the terms are already covered well within existing content
ThenNo - deepen and interlink existing pages before creating a separate hub.

Default answer

Recommended next steps

    Apply the method Knowledge Coverage Model Framework See the wider capability Content Opportunity Prioritisation Capability