glossary-definition-hublisted

# Glossary and Definition Hubs Definitional queries are the cheapest search traffic in most categories and the most reliably quoted by AI assistants, because a definition is exactly the shape of content an extraction system is looking for: short, self-contained, factual, unambiguous. They're also strategically useful beyond their own traffic. A glossary gives every other page on the site something authoritative to link to with clean anchor text, which is how a topic cluster actually gets bound together. The failure mode is obvious and common: 200 auto-generated definition pages of 80 words each, which is thin content at scale and gets treated as such. ## When a glossary is worth building Build it when at least two are true: - **The category has genuine jargon** customers must understand to buy. - **The site already has a topical map** these terms support. A glossary floating in isolation is decoration. - **You can write each entry with real authority**, including the parts other definitions get wrong. - **There are 15 to 60 terms that matter.** Fewer isn't a hub. More is usually padding. Don't build it when the terms are generic and already definitively covered elsewhere. A SaaS company doesn't need a definition page for "API" and won't rank for it. ## Structure ``` /glossary/ ← the hub, browsable and useful in itself /glossary/term-name ← one page per term ``` The hub page is a real page, not a link dump: - All terms listed