Content tags vs labels

Ref: C16 · Track: Knowledge Base Admin · Time to complete: ~3 min

Why this matters

Zendesk uses two tagging concepts on articles — labels and content tags — and they do different things. Confusing them will lead to broken reports or irrelevant article suggestions. This article separates them.

Labels

Labels are free-text metadata on an article, visible to admins (and optionally to customers as a filter). They're the informal tagging system.

Common uses: - Internal organisation ("billing", "Q2-review", "legal-approved"). - Search relevance — labels are included in the help center search index. - Reporting — filter "articles labelled billing" in book view or Explore. - Scope for verification rules (C08) and bulk actions (C11).

You can apply multiple labels to one article.

Creating / applying

1. Open the article.
2. In the right sidebar, Labels field.
3. Start typing — existing labels autocomplete, or type a new one and press enter.
4. Save.

No separate "create a label" step — labels come into existence when you apply them.

Content tags

Content tags are a newer, more structured concept. They're a controlled vocabulary defined by admins in advance. Think of them as allowed categories for content-based features:

• AI/Answer Bot training: content tags can be used to scope which articles the bot draws from per intent.
• Generative answers & search: tagged articles can be matched more precisely to question intent.
• Content quality reporting: more consistent than labels because values are controlled.

You can't just type a new content tag from an article — they're created in admin first, then applied.

Creating a content tag

In Guide admin → Content tags: 1. Click Add content tag. 2. Name and describe it. 3. Save.

Applying a content tag to an article

1. Open the article.
2. In the right sidebar, Content tags field.
3. Pick from the available list.
4. Save.

The difference in one line

Labels = free-text, informal, great for flexibility and quick filters. Content tags = controlled vocabulary, formal, great for AI features and structured reporting.

They co-exist. Most orgs use both.

When to use which

Reach for labels when

• You want to tag something fast without asking admin.
• You're filtering the book view for a project ("Q2-refresh").
• You want a customer-facing filter ("tutorial", "how-to").

Reach for content tags when

• You're shaping AI/bot answers.
• You want consistent reporting across articles.
• You're building a long-term taxonomy that you want enforced.

Gotchas

• Label sprawl. Because anyone can invent a label, you end up with billing, Billing, BILLING, bill, invoicing. Review labels quarterly; consolidate.
• Content tags are limited in scope. Not every Guide feature uses them yet; check which of your tools do.
• Case sensitivity. Labels are usually case-insensitive, but it's worth establishing a convention (lowercase-kebab, etc.).
• Customer-visibility of labels. Depending on theme, labels may appear as filterable keywords to end users. If you use labels for internal notes, decide whether that's okay.
• Labels don't support spaces neatly. Zendesk accepts spaces but many themes display them underscored. Prefer kebab-case (payment-failed).

Example taxonomy for a mid-size SaaS

Content tags (controlled): - product/core - product/addon-abc - audience/customer - audience/partner - purpose/how-to - purpose/policy - purpose/troubleshooting

Labels (free): - Internal project tags like Q2-review, legal-approved-2026, beta-v3.

This way the bot and reporting use content tags, and your team uses labels for ephemeral project work.

Quick check — have you got this?

• You want to tag 12 articles for a Q2 content review project. Labels or content tags?
• You want AI answers to draw from "policy" articles only when the question is about policy. Labels or content tags?
• Can you use both on the same article?

Related articles

• C05 — The book — managing all your content
• C08 — Article verification — keeping content current
• C18 — Knowledge Capture inside a ticket