Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Content Marketing › Content Production

Building a Glossary for Your Audience

How to build a glossary readers and search engines can use: choosing terms from real questions, writing definitions, linking to guides and avoiding thin pages.
Tutorialintermediate10 min readUpdated

What a glossary is for

A glossary does three jobs. It helps a reader who has met an unfamiliar word in one of your pages, an email or a form and needs to know what it means before going on. It gives the whole site one agreed meaning for each term, so that writers do not define the same word differently on different pages. And it gives search a clear page for definitional queries, many of which are Long-Tail Keyword queries phrased in the reader's own words.

The first job matters most. A glossary built for search alone tends to collect every term in the field, with definitions written to a word count, and ends up helping nobody. Google's guidance on helpful content, which the content governance guide uses as the standard for every page, asks whether content is made for people and provides original information. A definition written for your readers, with an example from your own products or customers and the confusion you actually see, passes that test in a way a rewritten dictionary entry does not.

A glossary is also a hub. In a topic cluster, the hub page carries the subject's definitions and links to the supporting pages; a glossary does the same across clusters, sending a reader from a term to the guide that teaches what to do with it. This site's own glossary works that way: each entry gives a short definition and links to the guide that covers the subject in depth.

One page or a page per term

The most consequential decision is how many pages the glossary has. There are two shapes, and most good glossaries use both.

ShapeWhat it looks likeSuitsThe risk
One glossary pageAll terms on one page, alphabetical or grouped, each with an anchor that other pages link toMost terms: those a sentence or two defines wellA long page that is hard to scan without grouping and search
A page per termA short page for one term, with the definition, a worked example, comparisons and linksThe few terms readers need more than a sentence forMany near-identical pages that add nothing, the pattern spam policies describe
BothEvery term on the glossary page, with the few that need more linking to their own pageMost sitesKeeping the short entry and the full page in agreement

The test for a page of its own comes from two places. The guide to Google's spam policies describes scaled content abuse: many pages generated primarily to manipulate rankings rather than to help users, typically unoriginal and of little value, however they are produced. A page per term, each holding a sentence and a template, is the shape that description fits. And the programmatic SEO guide sets the test every page in a set of similar pages must pass: a distinct need, where a reader looking for this term wants something different from one looking for its neighbour, and different substance, where the page shows something its siblings do not.

So a term earns its own page when a reader needs more than a sentence, such as a worked example, a calculation, a comparison with a term it is confused with, or the mistakes people make with it, and when that page would say something no other entry says. Everything else is an entry on the main page.

Before you start

  • A question bank. The audience research guide builds one from interviews, support logs, search data and communities. The terms readers ask about are in it.
  • Support logs and site search. Export recent support tickets and chat transcripts, and the site search log. The help-centre SEO guide explains why support content is written in customers' words; the same logs show which words confuse them.
  • The list of guides. Know which guide on the site teaches each task, so every entry can point to one.
  • A reviewer. Someone who uses the terms every day: a product specialist, a production manager, a support lead.
  • The house style guide. Spellings, capitalisation and product names for the entries should follow it.
  • A content owner. Someone who will own the glossary after launch, named in the governance roles.

The steps

The first two steps decide what goes in and how many pages there are; the next four write and link the entries; the last three check, publish and maintain them.

  1. List the terms readers stumble over

    Go through the question bank, support logs and site search log, and pull out every term readers ask about, misuse or search for. Note where each one came from and the reader's own wording, because a reader who types "what does bleed mean" and one who writes "why is my picture cut off at the edge" are asking about the same term in different words. Add terms your own pages use without explaining, which writers and editors can flag. Leave out terms nobody has asked about, however central they seem to the field: the glossary is for your readers' vocabulary, not a complete dictionary of the industry. Group the list by subject so that related terms are written together.

  2. Decide which terms earn their own page

    Mark each term as an entry or a page using the test above. A term earns a page when readers need more than a sentence or two and the page would hold something distinct: a worked example, a comparison with the term it is confused with, a calculation, or the mistakes people make. Check whether a guide already covers the term in depth. If it does, the term gets a glossary entry that links to that guide, not a page that repeats it. The keyword cannibalisation guide explains why: the guide that teaches a task owns the "how to" query, and the term entry owns the definition and points to it, so the two serve different Search Intent and do not compete. Expect most terms to stay entries.

  3. Write a definition pattern

    Decide the structure every entry follows, so that readers know where to look and writers know what to write. A pattern that works for most glossaries is: the term, with any common abbreviation or variant spelling; a one-sentence definition; an example, from your products or your readers' situations; the common confusion, where there is one; related terms; and the guide to read next. Pages for individual terms add a worked example, the comparison or the mistakes, and nothing else that the main guide already covers. Write the pattern down with one finished entry as a model, and add it to the house style guide so every writer follows it.

  4. Write the one-sentence definition first

    Start every entry with a single sentence that a reader could understand without reading anything else on the page. Say what the thing is in plain words, then what it is for. Avoid defining a term with other terms the reader may not know; where you must, link them. Avoid circular definitions, which use the word to define itself, and definitions copied from a dictionary, which describe the word in general rather than how your readers meet it. The writing for the web guide explains why the first sentence carries most of the weight: people scan before they read, and many readers will stop after it.

  5. Add the example and the common confusion

    Follow the definition with an example drawn from your own products, customers or readers' situations, because a definition is understood through an example far more easily than through more definition. Then add the confusion you actually see in the support logs and questions: the term it is mixed up with, the mistake readers make, or the everyday meaning that differs from the technical one. This is where an entry becomes original rather than generic, because the confusion is specific to your readers and nobody else's glossary records it. Keep both short in the main glossary; a page for an individual term can develop them further.

  6. Link each entry to the guide that teaches it, and back

    Every entry ends with a link to the guide that teaches what to do with the term, and every guide that uses the term links to its entry the first time it appears. Use descriptive anchor text, as the internal linking guide explains Google's link guidance recommends: the guide's subject for links out of the glossary, and the term itself for links in. Link entries to related entries where the comparison helps. These Internal Link paths are what make the glossary useful in both directions: a reader on a guide can check a word without losing their place, and a reader who arrived on a definition can go on to the task.

  7. Have someone who uses the terms daily review every entry

    Send each batch of entries to the reviewer before publication. Ask three questions of every entry: is the definition correct as the term is used in practice here; does the example reflect real work; and is the confusion one the reviewer recognises? Experts often find that a definition is technically right but describes the term as a textbook does rather than as customers meet it. Record who reviewed each entry and when, because a reviewed definition is one the rest of the site can rely on, and governance needs to know whose judgement it rests on.

  8. Publish in batches and watch what search does with them

    Publish the glossary page with its first group of entries, and any term pages that are ready, rather than everything at once. Then watch the search performance report for the glossary and the term pages: which queries they appear for, whether those queries are definitional, and whether a term page is appearing for queries a guide should own, which is the sign of competition the cannibalisation guide describes. Watch site search and support logs too, for whether the confusions you wrote about become less common. Adjust the next batch: terms readers look for that you missed, term pages that should fold back into the main glossary, and entries whose definitions readers still misunderstand.

  9. Give every entry an owner and a review date

    Add the glossary and every term page to the content inventory with an owner and a review date, as the governance guide requires of every page. Definitions age when products change, when the field adopts new usage, or when a guide an entry links to is retired. Tie entries to the guides they link to, so that a change to a guide prompts a check of its entries. When a definition changes in substance, update every page that quotes it, and record the change.

A print studio's glossary (illustrative)

Illustrative example — not a real result

Inkthistle Print Co. builds a glossary from its order forms

Inkthistle Print Co., an invented print studio that takes orders online, finds that customers keep getting the same things wrong on its order forms. Its content lead reads 3 months of support emails and order notes and lists 47 terms customers asked about or misused; 31 survive after removing terms nobody asked about twice. Four terms cause most of the problems: bleed (designs supplied without the studio's 3 mm bleed, so pictures are trimmed at the edge), proof (customers approving a proof without checking it, then disputing the print), paper weight (customers choosing by number without knowing what it feels like) and spot colour (confused with the colours on screen). Those 4 get their own pages, each with a worked example, photographs of right and wrong files, and the confusion customers actually have. The other 27 are entries on one glossary page with an anchor each, using the pattern: one-sentence definition, example, common confusion, related terms, and a link to the ordering guide that uses the term. The ordering guides link back to each term the first time it appears. The production manager reviews every definition and rewrites 6, including paper weight, which the first draft defined as the thickness of the paper. The glossary goes live in 2 batches a month apart. In the 3 months after launch, support emails about trimmed pictures fall from 58 to 21, and one term page, proof, starts appearing for "how to approve a print proof", a query the ordering guide should own; the content lead shortens the term page and points it at the guide.

Common mistakes

  • Building from a dictionary instead of from readers. Terms nobody asked about crowd out the ones readers need.
  • A page for every term. Pages that hold a sentence and a template are the shape the scaled content abuse policy describes; keep most terms on one page with anchors.
  • Definitions that need a definition. A first sentence full of other jargon sends the reader somewhere else.
  • Copying general definitions. A dictionary-style entry says nothing about how your readers meet the term; the example and the confusion are what make it yours.
  • Term pages that grow into guides. A definition page that teaches the task competes with the guide that owns it.
  • Links in one direction only. Entries that never link to guides, or guides that never link to entries, leave readers stuck on one side.
  • No expert review. A definition that is right in a textbook and wrong in practice misleads the people who rely on it most.
  • Publishing everything at once and never looking again. Batches show what search and readers do with the first entries before the rest are written.
  • No owner. Definitions drift out of date as products and usage change, and nobody notices.

Frequently asked questions

Should every glossary term have its own page?

No. Give a term its own page only when a reader needs more than a sentence or two, such as a worked example, a comparison or the common mistakes, and when that page says something its sibling entries do not, which is the test the programmatic SEO guide sets for any set of similar pages. Keep the rest as entries on one glossary page with an anchor each. Google's spam policies describe scaled content abuse as many pages generated primarily to manipulate rankings rather than help users, however they are produced, and a page per term with a sentence on each is the shape that description fits.

Will a glossary entry compete with my guides in search?

Not if each page has its own job. The guide that teaches a task owns the 'how to' query; the glossary entry owns the definition and links to the guide. The keyword cannibalisation guide notes that pages sharing words but serving different intents are not competing, because the results page wants different formats for the two queries. Problems start when a glossary page grows into a second guide, or a guide is retitled as a definition; keep the definition short and point onwards.

Glossary or blog post: which should explain a term?

Usually the glossary, with a link to the post. A definition is reference material that readers come back to and that other pages link to, so it belongs in a stable place with one address. A blog post is the right home when the term needs a story, an opinion or an argument, such as why a common usage is wrong, and the glossary entry can then link to the post for readers who want more. What to avoid is the same definition written several times in several posts, each slightly different.

Terms used on this page

Frameworks

Also related

Sources

  1. Spam policies for Google web search — Google Search Central
  2. Creating helpful, reliable, people-first content — Google Search Central
  3. Link best practices for Google — Google Search Central

Related