Glossary Page Design

A SaaS glossary is a collection of definition pages that target "what is [term]" search queries. Each term gets its own URL, its own page, and its own shot at ranking. Done well, glossary pages capture top-of-funnel traffic from buyers learning the category. Done poorly, they're thin content that Google ignores.

The principle: a glossary page should teach, not just define. A dictionary definition is 20 words. A useful glossary entry is 400-800 words that helps the reader understand the concept, why it matters, and how it connects to their work. Depth is the differentiator.

Architecture

Structure

/glossary/                    → Hub page listing all terms
/glossary/mql/               → Individual term page
/glossary/lead-scoring/      → Individual term page
/glossary/pipeline-coverage/ → Individual term page

Architecture rules

• Hub page + individual pages. The hub (/glossary/) lists all terms with short descriptions and links. Each term gets its own URL with full content
• Alphabetical AND categorical navigation on the hub. Users browse alphabetically. Google needs categorical grouping for topical relevance. Provide both
• 50-200 terms per glossary. Under 50 is too thin to build topical authority. Over 200 and maintenance becomes difficult. Start with 50, add 10 per month
• Each term on its own URL. Don't put all definitions on one page. Individual URLs target individual keywords and are indexable separately

Writing Glossary Entries

Entry structure

H1: What is [Term]?

Definition (2-3 sentences):
  Clear, jargon-free definition accessible to someone
  new to the concept.

Why it matters (2-3 sentences):
  Why this concept is important for B2B SaaS teams.
  Connect to business outcomes.

How it works (3-5 bullet points or short paragraphs):
  Practical explanation. How does this concept apply
  in practice?

Example:
  One concrete example showing the concept in action.
  Use real-world B2B SaaS context.

Related concepts:
  Links to 3-5 related glossary terms.

CTA (optional):
  Soft link to relevant product page or resource.
  "Learn how [product] handles [concept]"

Entry writing rules

• 400-800 words per entry. Under 400 is thin content. Over 800 and you're writing a blog post, not a glossary entry. Hit the sweet spot
• Lead with a plain-language definition. No jargon in the definition of the thing you're defining. "MQL is a Marketing Qualified Lead. It's a lead that meets specific criteria indicating they're likely to become a customer" beats "An MQL is a demand-gen lifecycle stage in the revenue waterfall"
• Include a concrete example. "For example, a SaaS company might define an MQL as a lead who matches their ICP (50-500 employees, B2B, has marketing team) AND has visited the pricing page twice in 7 days"
• Link to 3-5 related terms. Every glossary entry should link to related terms within the glossary. This creates an internal linking web that boosts all pages
• No fluff. "In today's fast-paced business environment, understanding MQL is crucial for success." Delete. Start with the definition. Get to the point

Example entry

## What is Pipeline Coverage?

Pipeline coverage is the ratio of active sales pipeline
to revenue target. If your quarterly target is $500K and
you have $2M in pipeline, your coverage ratio is 4x.

## Why It Matters

Pipeline coverage is the earliest warning signal for
revenue misses. By the time you miss revenue, it's too
late to fix. Thin pipeline coverage 8 weeks before
quarter-end means you're likely to miss target.

## How It Works

- Calculate: Active pipeline / Revenue target = Coverage ratio
- Standard target: 3-5x for most B2B SaaS teams
- Adjust by win rate: lower win rate = higher coverage needed
- Measure weekly: coverage should decrease naturally
  as the quarter progresses and deals close or fall out
- Use weighted coverage for accuracy: multiply each deal
  by its stage win rate

## Example

A Series B SaaS company targets $600K in quarterly
revenue. They start Q2 with $2.4M in active pipeline
(4x coverage). By mid-quarter, pipeline has dropped to
$1.5M (2.5x). This signals risk: they need to accelerate
deal creation or accept a likely miss.

## Related Terms

- [Pipeline Forecasting](/glossary/pipeline-forecasting/)
- [Win Rate](/glossary/win-rate/)
- [Sales Velocity](/glossary/sales-velocity/)
- [Weighted Pipeline](/glossary/weighted-pipeline/)

SEO Optimization

Keyword targeting

SEO rules

• Target "what is [term]" queries. These are the primary keywords. "What is MQL" (8K/mo), "what is pipeline coverage" (500/mo), "what is lead scoring" (3K/mo)
• Use DefinedTerm schema markup. This tells Google explicitly that this page defines a term. It can trigger dictionary-style rich snippets
• Front-load the definition. Google often pulls the featured snippet from the first 2 sentences. Make the definition clear and complete in the opening
• Internal link from blog posts. Whenever a blog post mentions a glossary term, link to the glossary entry. This builds authority and helps users

Hub Page Design

Hub page elements

Term Selection

How to choose terms

Selection rules

• Only define terms relevant to your category. A CRM company shouldn't define "machine learning." Stay in your lane. Topical relevance matters more than term volume
• Prioritize by search volume. "What is CRM" (200K/mo) ranks higher in priority than "what is BANT" (5K/mo). Start with the highest-volume terms
• Include terms your product uses. If your product has features called "Signals" or "Sequences," define those terms. Users search for them
• Don't duplicate Wikipedia. If the term is generic enough that Wikipedia owns the featured snippet and always will ("what is marketing"), skip it. Focus on B2B SaaS-specific terms where you can compete

Measurement

Pre-Publish Checklist

• [ ] Hub page created with alphabetical and categorical navigation
• [ ] Each entry is 400-800 words with definition, why it matters, how it works, example
• [ ] Each entry links to 3-5 related glossary terms
• [ ] H1 is "What is [Term]?" format
• [ ] Meta title follows "[What is Term]? Definition + Examples" pattern
• [ ] Plain-language definition in the first 2 sentences (featured snippet target)
• [ ] DefinedTerm schema markup implemented
• [ ] No jargon in definitions (defines terms, doesn't use undefined terms)
• [ ] Blog posts link to relevant glossary entries
• [ ] Terms selected based on search volume and category relevance
• [ ] "Last updated" date visible on each entry

Anti-Pattern Check

• 50-word definitions with no depth. "MQL: A Marketing Qualified Lead is a lead that meets marketing's criteria." That's a dictionary entry, not a glossary page. Google won't rank it. Add 400-800 words of context, examples, and related concepts
• All terms on one page. A single /glossary/ page with 100 terms and anchor links. Each term can't rank individually. Each term needs its own URL
• Defining terms outside your category. You're a CRM company defining "blockchain," "machine learning," and "agile methodology." These dilute your topical authority. Define terms in your domain only
• No internal linking between entries. 50 glossary pages exist in isolation. None link to each other. You're missing the internal linking benefit that makes glossaries SEO-powerful. Every entry links to 3-5 related terms
• Glossary published and never updated. Terms from 2023 reference outdated concepts and tools. Stale glossaries lose rankings. Review and update quarterly
• No link from blog to glossary. Your blog mentions "pipeline coverage" 15 times across 10 articles. None link to /glossary/pipeline-coverage/. Every mention is a missed internal linking opportunity
• Marketing copy in definitions. "MQL is a powerful concept that unlocks growth potential for forward-thinking teams." Nobody searched for that. Define clearly, explain practically, skip the marketing