A multilingual brand glossary gives translators, editors, marketers, and AI translation tools a shared reference for important terms. This guide explains how to build one, what terminology to track, how to apply it during translation and review, and when to refresh it so website, product, and marketing content stays consistent across languages.
Overview
A brand glossary is a controlled list of terms that your organization has agreed to translate, retain, explain, or avoid. It may include product names, feature labels, industry terminology, campaign language, customer-facing phrases, and words with a specific meaning in your business.
A glossary is not a replacement for a full translation style guide. The glossary answers, “Which term should we use?” The style guide answers, “How should the content sound and be formatted?” Together, they reduce avoidable variation across web pages, app interfaces, help documentation, email campaigns, and social content.
Terminology management becomes especially useful when several people work on the same content, when an AI translator is part of the workflow, or when one brand publishes in multiple regions. Consistency does not mean translating every phrase literally. It means making deliberate decisions and recording them where future contributors can find them.
Glossary, style guide, translation memory, or prompt instructions?
| Resource | Best used for | Example |
|---|---|---|
| Brand glossary | Approved terms, meanings, translations, and forbidden alternatives | “Workspace” must use the approved target-language product term |
| Translation style guide | Voice, punctuation, formatting, inclusivity, and regional preferences | Use a direct, helpful tone and sentence case in headings |
| Translation memory | Reusing previously translated segments and approved sentence-level work | A recurring legal disclaimer or interface message |
| Prompt instructions | Giving an AI tool task-specific context and constraints | Use the glossary terms below and flag uncertain phrases |
These resources work together. A glossary records terminology decisions; a translation memory preserves approved translations in context; a style guide protects the brand voice; and prompt instructions help an AI language tool follow the current assignment.
What to track
Start with terms that create the greatest risk of inconsistency or misunderstanding. Do not try to document every word in the language. A focused glossary is easier to maintain and more likely to be used.
- Brand and product names: Record whether each name stays unchanged, is transliterated, or has an approved localized form.
- Features and interface labels: Include navigation items, buttons, account areas, plans, settings, and recurring calls to action.
- Industry terminology: Capture words that have a technical meaning in your product or market.
- Campaign and positioning language: Add recurring phrases, taglines, value propositions, and names for audience segments.
- Terms with multiple valid translations: Explain which option fits your brand and why.
- False friends and risky literal translations: Record alternatives that may sound natural but change the intended meaning.
- Regional variants: Note differences between markets where vocabulary, spelling, formality, or usage varies.
- Terms to avoid: List outdated, misleading, legally sensitive, or off-brand alternatives.
Reusable multilingual glossary template
Use one row per concept rather than one row per source-language word. This helps prevent duplicate entries when several words refer to the same product idea.
| Field | What to record |
|---|---|
| Concept ID | A stable reference such as PRODUCT-014 or UX-027 |
| Source term | The approved source-language term |
| Definition | The meaning in your product or brand context |
| Part of speech | Noun, verb, adjective, button label, or other grammatical role |
| Approved translation | The preferred translation for each target language and region |
| Forbidden alternatives | Translations, spellings, or phrases that should not be used |
| Usage example | A sentence, interface label, or headline showing the term in context |
| Grammar and format notes | Gender, plural form, capitalization, inflection, or character limits |
| Regional notes | Market-specific preferences or restrictions |
| Status | Proposed, approved, deprecated, or under review |
| Owner and review date | The person responsible for the decision and its next review |
For example, an entry for a software feature might specify that “Shared Workspace” is a proper feature name, must retain title capitalization in English, has an approved translation in Spanish, and should not be translated as a generic “common office.” The definition and usage example give translators enough context to make the correct choice.
Cadence and checkpoints
Build the glossary into the same workflow used to create and approve content. A glossary that exists in a separate file but is not consulted during production will quickly become incomplete.
Step 1: Collect candidate terms
Review product screens, website pages, support articles, campaign briefs, search terms, and previously translated content. Ask contributors to submit terms whenever they introduce a feature, rename a product area, or notice inconsistent wording.
Step 2: Resolve the source-language meaning
Before requesting translations, define what each term means in your business. Identify whether it is a proper name, a concept, an action, or a label with a character limit. Ambiguous source terms produce inconsistent target-language decisions.
Step 3: Approve target-language forms
Have a language reviewer or qualified bilingual contributor assess each proposed translation in context. For high-impact terms, review the option in a sentence, interface screen, headline, and support explanation rather than judging the isolated word alone.
Step 4: Add constraints and alternatives
Record forbidden alternatives, capitalization, grammatical gender, plural forms, regional differences, and any space or character limits. If the term must remain in the source language, state that clearly.
Step 5: Publish a usable version
Store the glossary where translators, editors, developers, and reviewers can access it. Use consistent field names, searchable entries, clear statuses, and a visible change log. If your translation platform supports terminology databases or term bases, import the approved entries using its supported format and verify the result with a small test set.
Step 6: Apply it during translation and QA
Give the glossary to human translators and include relevant entries in AI translation instructions. During review, search for forbidden alternatives and check whether approved terms are used consistently across page titles, buttons, body copy, metadata, and customer messages. A glossary should inform human judgment, not force a translation that sounds unnatural in context.
For broader document quality checks, pair terminology review with the workflow described in How to Translate Documents Accurately. Website teams can also use the multilingual SEO localization checklist to review localized page elements beyond the main text.
How to interpret changes
Track more than the number of glossary entries. The useful signals are changes that reveal risk, confusion, or growing maintenance needs.
- New product or campaign terms: A rise may indicate a launch, rebrand, or new content area that needs coordinated terminology before publication.
- Repeated reviewer corrections: Frequent corrections to the same term suggest that the entry is hard to find, poorly defined, or missing useful context.
- Regional disputes: Different markets may need separate approved terms rather than one forced universal translation.
- Deprecated entries: Old feature names should remain searchable for a period, but clearly marked as deprecated, so legacy content can be identified without reintroducing outdated language.
- AI translation deviations: If an AI translator repeatedly ignores a term, check the prompt format, terminology import, capitalization rules, and surrounding context. Do not assume that a glossary alone guarantees compliance.
- Search and conversion anomalies: A localized term may be linguistically correct but unfamiliar to the intended audience. Compare it with market research, internal search behavior, support questions, and reviewer feedback before changing it.
When a term changes, record the reason, affected languages, impacted URLs or product surfaces, and the date the new form becomes active. This makes the decision auditable and helps teams update translation memories, content management systems, prompts, and existing pages consistently.
When to revisit
Review the glossary on a regular cadence and whenever terminology changes. A practical baseline is a light monthly check and a more complete quarterly review.
Monthly check
- Review newly proposed terms and assign an owner.
- Confirm that recent launches and campaigns use approved terminology.
- Resolve repeated reviewer comments and mark obsolete entries.
- Check that translators and content contributors can access the current version.
Quarterly review
- Audit a sample of website pages, product screens, metadata, and marketing assets in each active language.
- Compare the glossary with current product names, navigation labels, and campaign language.
- Review regional variants with local-language contributors.
- Test terminology features, file imports, and AI translation instructions after major tool changes.
- Update examples, ownership, statuses, and next review dates.
Immediate review triggers
Do not wait for the calendar after a rebrand, product rename, market launch, legal terminology change, major interface update, or switch in translation tooling. Create a short terminology checkpoint before translating the related content, then complete a follow-up audit after publication.
To put this into practice, create the glossary with the template above, select the first 25 to 50 high-impact terms, assign one decision owner per language or market, and schedule the first quarterly audit. Link the approved glossary to your translation workflow, style guide, and AI translator instructions. For freelancers and small teams, the process can begin in a shared spreadsheet; for larger localization programs, the same fields can later move into a terminology-management system without changing the underlying decisions.