How to Add a Glossary and Definition Pages to Your Site

Your site has no linked glossary or 'what is' pages, so search engines and AI assistants have no clear page of yours to cite when someone asks what a term in your industry means. By the end of this guide you will have published a glossary hub and individual definition pages with recognizable URLs (such as /glossary/ or /what-is-churn-rate/), linked them from your site's navigation or footer, and marked them up with structured data.

By Updated ⏱ 2-4 hours for a hub plus 10 terms🎯 Beginner● Low impactContent
Illustration: Glossary and definitions fix guide
CONTENT · FIX GUIDE Glossary and definitions IMPACTEFFORT TIME2-4 hours for a hub plus 10 terms LEVELBeginner

Why it matters

Definition queries ('what is X', 'X meaning') are some of the most common searches, and they are the questions AI Overviews, ChatGPT and Perplexity answer by quoting a short, self-contained definition from a source page. A dedicated page with a concise definition at the top is much easier to extract and cite than a term buried in a blog post. Glossary pages also give you natural internal links to product and service pages.

The impact is modest per term but compounds as you add more, and a linked glossary signals topical depth in your niche.

✕BeforeNo link anywhere on the homepagepoints to a URL containing 'glossary','definition' or 'what-is'; terms are✓AfterThe footer links tohttps://example.com/glossary/, whichlists and links to pages like

What you need

Editor access to your CMS or site codebase
A list of 10-20 industry terms (from Google Search Console, sales calls or support tickets)
Access to edit your main navigation or footer menu
Google Search Console access (optional, for indexing)

Step-by-step fix

1

Pick the terms you want to own

Start with terms your customers already search for. In Google Search Console go to Performance > Search results, click + New > Query, choose Custom (regex) and filter with the regex below to see definition-style queries you already get impressions for. Add terms your sales and support teams explain repeatedly.

Aim for 10-20 terms to launch, prioritizing ones tied to your product.

text
(?i)^(what is|what are|what does|define|definition of|meaning of)\b|\bmeaning$
Pro tip: Skip generic terms dominated by dictionaries and Wikipedia; target terms specific to your niche where you can add real expertise.
2

Choose a URL structure with a clear slug

Use URLs that make the purpose obvious. Two patterns work well:

  • A hub at /glossary/ with child pages like /glossary/churn-rate/
  • Standalone pages like /what-is-churn-rate/ for high-value terms

Use the word 'glossary', 'definitions' or 'what-is' in the slug rather than vaguer names like /terms/ or /dictionary/, which are often confused with legal pages and are less recognizable to crawlers and audits.

text
https://example.com/glossary/
https://example.com/glossary/churn-rate/
https://example.com/glossary/net-revenue-retention/
https://example.com/what-is-customer-lifetime-value/
Pro tip: Pick one pattern and stick to it; mixing both for the same term creates duplicate content.
3

Write each definition page answer-first

g. '). Follow with how it is calculated or used, a worked example, common confusions, and links to related terms and your relevant product page.

Use the term in the H1 and title tag. Keep each page focused on one term.

html
<h1>What Is Churn Rate?</h1>
<p><strong>Churn rate</strong> is the percentage of customers who stop using a product during a given period. For example, if Example Co starts the month with 1,000 subscribers and 30 cancel, its monthly churn rate is 3%.</p>
<h2>How to calculate churn rate</h2>
<p>Churn rate = customers lost during the period ÷ customers at the start of the period × 100.</p>
<h2>Related terms</h2>
<ul>
  <li><a href="/glossary/net-revenue-retention/">Net revenue retention</a></li>
  <li><a href="/glossary/customer-lifetime-value/">Customer lifetime value</a></li>
</ul>
Pro tip: Add an author name and 'last updated' date; AI tools and reviewers favor definitions with visible accountability.
4

Add DefinedTerm structured data

Mark up each term with schema.org DefinedTerm and connect it to a DefinedTermSet representing your glossary. Google does not show a rich result for this type, but it gives machines an unambiguous term-and-definition pair. Place the JSON-LD in the page's head or body.

html
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "DefinedTerm",
  "name": "Churn rate",
  "description": "Churn rate is the percentage of customers who stop using a product during a given period.",
  "url": "https://example.com/glossary/churn-rate/",
  "inDefinedTermSet": {
    "@type": "DefinedTermSet",
    "name": "Example Co SaaS Glossary",
    "url": "https://example.com/glossary/"
  }
}
</script>
Pro tip: Keep the description in the schema identical to the visible opening definition.
5

Build the glossary hub page

Create /glossary/ as an index listing every term alphabetically, each with a one-sentence summary and a link to its page. Add A-Z jump links if you have more than about 30 terms. Give the hub its own title and intro paragraph so it is not a thin list of links.

html
<h1>Example Co Glossary</h1>
<nav aria-label="Glossary letters"><a href="#c">C</a> <a href="#n">N</a></nav>
<h2 id="c">C</h2>
<dl>
  <dt><a href="/glossary/churn-rate/">Churn rate</a></dt>
  <dd>The share of customers who cancel in a given period.</dd>
  <dt><a href="/glossary/customer-lifetime-value/">Customer lifetime value</a></dt>
  <dd>The total revenue you expect from one customer.</dd>
</dl>
6

Link the glossary from your site template

Add a plain HTML link to /glossary/ in your footer (under Resources) or main navigation so it appears on every page, including the homepage. Also link to individual definition pages from blog posts and product pages the first time a term appears. Use a real <a href> element, not a JavaScript click handler or a button.

html
<footer>
  <h3>Resources</h3>
  <ul>
    <li><a href="/blog/">Blog</a></li>
    <li><a href="/glossary/">Glossary</a></li>
  </ul>
</footer>
Pro tip: Link each term only once per article to avoid cluttering the text.
7

Verify the links and request indexing

Open your homepage, press Ctrl+U (Cmd+Option+U on Mac) to view the source, and search for 'glossary' or 'what-is' to confirm the link is in the server-delivered HTML. Make sure the new URLs are in your XML sitemap and not set to noindex. In Google Search Console, use URL Inspection on the hub and click Request indexing, then re-run the audit.

text
curl -s https://example.com/ | grep -Eio 'href="[^"]*(glossary|definitions?|what-is)[^"]*"'
Pro tip: If curl returns nothing but you see the link in the browser, your menu is rendered client-side; move the link into static HTML.

Platform-specific notes

WordPress

Create the hub under Pages > Add New Page and set the slug to 'glossary' in the Page settings panel (Settings > Permalinks should use 'Post name'). For many terms, set child pages with Page Attributes > Parent = Glossary, or register a 'glossary' custom post type. Add the footer link under Appearance > Menus (classic themes) or Appearance > Editor > Patterns/Footer (block themes). Yoast and Rank Math do not output DefinedTerm, so add the JSON-LD with a Custom HTML block.

Shopify

Create pages under Online Store > Pages; Shopify forces the /pages/ prefix, so set the handle to 'glossary' or 'what-is-churn-rate' (giving /pages/glossary). Add the link via Online Store > Navigation > Footer menu. For many terms, use a blog named 'Glossary' (Online Store > Blog posts > Manage blogs), which produces /blogs/glossary/term-name URLs.

Wix

Add pages from the Pages & Menu panel, then open each page's Settings > SEO basics and set the URL slug to 'glossary' or 'what-is-term'. For a large glossary, create a CMS collection with a dynamic page whose URL prefix is /glossary/. Add JSON-LD under Page Settings > SEO > Advanced SEO > Structured data markup.

Webflow

Create a CMS Collection named 'Glossary Terms' with the collection URL set to 'glossary', plus fields for Definition and Body. Build the hub as a static page at /glossary using a Collection List. Insert DefinedTerm JSON-LD in the Collection template's Page Settings > Custom Code, using CMS field bindings for name and description.

Next.js

With the App Router, create app/glossary/page.tsx for the hub and app/glossary/[slug]/page.tsx for terms, using generateStaticParams to prerender them and generateMetadata for titles. Use the next/link Link component in your footer so the href is in the server-rendered HTML, and render the JSON-LD with a script tag of type application/ld+json.

Check that it worked

✅ How to verify

  • View the homepage source (or run the curl command from step 7) and confirm at least one href contains 'glossary', 'definition' or 'what-is'.
  • Re-run the audit and confirm the check reports glossary/definition content found.
  • Paste a term URL into validator.schema.org and confirm the DefinedTerm and DefinedTermSet parse without errors.
  • In Google Search Console, use URL Inspection on /glossary/ and a term page to confirm they are indexable and, after a few days, indexed.

⚠️ Common mistakes

  • Publishing the glossary but not linking it anywhere crawlable, so it is an orphan page that search engines and audits never find.
  • Naming the section /terms/, /dictionary/ or /resources/wiki/ instead of using 'glossary' or 'what-is' in the URL, which makes its purpose less clear.
  • Writing one-line definitions copied from Wikipedia; thin or duplicated pages rarely rank or get cited by AI tools.
  • Rendering the footer or menu link only through JavaScript, so the link is missing from the HTML crawlers first receive.

Is this still an issue on your site? Run a free audit — ZORO checks this and 294 other SEO, AI-visibility, accessibility and security signals, with fixes for your platform.

Check my site free

FAQ

Should glossary terms be on one page or separate pages?

Use both: a hub page at /glossary/ that lists every term, plus separate pages for terms with real search demand. A single long page can only rank well for a few terms, while individual pages can each target their own 'what is' query.

How long should a glossary definition page be?

Lead with a 40-60 word standalone definition, then add enough depth to be useful, typically 300-800 words covering how it works, an example and related terms. Length should follow the term's complexity, not a word count target.

Does DefinedTerm schema give a rich result in Google?

No. Google does not currently show a rich result for DefinedTerm, but the markup still makes the term and its definition explicit to search engines and AI systems that parse structured data.

Will a glossary help my site appear in AI Overviews and ChatGPT answers?

It improves your chances. AI answers for definition questions often quote a concise definition from a page dedicated to that term, so a clear answer-first paragraph on an indexable, well-linked page is the format most likely to be cited.