A translation glossary and style guide give every translator, editor, and AI-assisted workflow the same reference point. This practical template shows what to record, how to approve terminology, and how to review multilingual content over time so your website, campaigns, and product copy remain consistent in language, tone, and search intent.
Overview
Multilingual inconsistency rarely comes from one obvious mistake. More often, the same product feature is given two names, a call to action changes between pages, or a keyword is translated literally even though local searchers use a different phrase. These small differences make content harder to manage and can weaken the connection between a translated page, its audience, and its intended search query.
A translation glossary records approved terms and their equivalents in each target language. A translation style guide explains how those terms should be used, along with rules for tone, grammar, formatting, local references, and multilingual SEO. Use the glossary for decisions about individual words and the style guide for decisions about the wider reading experience.
Keep both documents easy to find and simple to update. A spreadsheet, shared document, or translation-management-system resource can work well if it has clear ownership, version history, and an approval status. The format matters less than the discipline of using one source of truth.
For a broader launch process, pair this system with a website translation and localization checklist. If search demand differs by market, document those findings separately through a multilingual keyword research workflow rather than treating direct translation as keyword research.
What to track
1. Build a reusable glossary spreadsheet
Start with one row per concept, not one row per appearance of a word. This prevents the glossary from becoming a list of disconnected translations. The following columns provide a practical starting structure:
| Column | What to record |
|---|---|
| Concept or source term | The word, phrase, feature name, or concept in the source language. |
| Approved translation | The preferred equivalent for each target language. |
| Part of speech | For example, noun, verb, adjective, button label, or heading. |
| Definition | The meaning in your product or brand context. |
| Usage example | A complete sentence or interface example showing the term in context. |
| Do not use | Rejected alternatives, outdated names, literal translations, or confusing synonyms. |
| Translation treatment | Translate, preserve, transliterate, or localize. |
| SEO notes | Search term, intent, spelling variation, or market-specific preference when relevant. |
| Status and owner | Draft, approved, needs review, plus the person responsible for the decision. |
| Review date | When the entry should next be checked. |
Use the do not use column carefully. It helps new contributors avoid familiar but inaccurate terms, especially when a product has renamed a feature. Add a short reason for disputed decisions, such as “too technical for consumer pages” or “conflicts with the legal term.” This preserves institutional knowledge without requiring a long explanation in every project brief.
2. Add a terminology decision table
Not every word should be translated. Decide the treatment at the concept level and record the reason.
| Treatment | Typical examples | Decision to record |
|---|---|---|
| Translate | General instructions, descriptive headings, support content | Use the approved target-language term and grammatical form. |
| Preserve | Registered product names, URLs, email addresses, code, model numbers | Keep the original form and define it if the audience may not recognize it. |
| Transliterate | A name or term that needs to be represented in another writing system | Specify the preferred spelling and whether the original should appear alongside it. |
| Localize | Currency, dates, measurements, examples, idioms, and calls to action | Adapt the expression to the market while preserving the intended meaning. |
Brand names and product names deserve their own rules. State whether capitalization, punctuation, accents, and plural forms can change. For example, a product name may remain unchanged while the surrounding sentence follows target-language grammar.
3. Create a tone-and-voice template
A style guide should turn abstract instructions such as “sound friendly” into observable choices. Include:
- Audience: Who is reading, what they already know, and what action they need to take.
- Voice: Three or four durable traits, such as clear, calm, practical, and respectful.
- Formality: Whether the brand uses formal or informal address, and when that choice changes by channel.
- Sentence guidance: Preferred length, active or passive voice, and how to handle technical explanations.
- Inclusive language: Terms to prefer, terms to avoid, and questions that require local review.
- Formatting: Rules for headings, lists, dates, numbers, quotation marks, units, and capitalization.
- Examples: A before-and-after passage showing the intended tone in the target language.
Include separate notes for website copy, product interfaces, customer support, and advertising when the tone differs. A single global rule may be too broad for every channel.
4. Track multilingual SEO decisions
Localization and SEO overlap, but they are not identical. For each important page, record the target audience, search intent, primary local query, related terms, title-tag approach, meta description guidance, heading structure, URL treatment, and internal-link anchor text. A literal translation may be grammatically correct and still fail to match how people search in that market.
Do not force keywords into sentences or translate a phrase in a way that sounds unnatural. Have a native-level reviewer assess both search relevance and readability. A multilingual readability review can help identify wording that is technically accurate but difficult for the intended audience.
Cadence and checkpoints
Use a defined workflow so terminology decisions do not depend on memory or individual preference.
- Collect: Gather recurring terms from product screens, source copy, search research, support questions, and previous translations.
- Classify: Mark each item as a general term, brand term, technical term, legal phrase, SEO term, or market-specific expression.
- Propose: Add a translation, definition, usage example, and alternatives to avoid.
- Review: Ask the appropriate subject expert, market reviewer, editor, or legal contact to assess the proposal.
- Approve: Record the final decision, owner, date, and any limits on usage.
- Apply: Update current projects, reusable templates, content briefs, and translation memories where appropriate.
- Audit: Check live pages and recently delivered content for the most important terms.
For active websites, a monthly light review is useful for new product language, campaigns, and urgent corrections. A quarterly review can cover the full glossary, page templates, search terms, and style examples. Before a major launch, complete a focused checkpoint for new features, market terminology, metadata, navigation labels, and customer-support content.
Keep a change log with four fields: date, decision, reason, and affected assets. If your team uses translation software, check whether it supports term bases, forbidden terms, contextual notes, approval states, version history, and quality checks. Tools can enforce a decision, but they cannot decide whether a phrase is culturally suitable or aligned with local search intent.
How to interpret changes
When a reviewer proposes a change, first determine what type of problem it solves. A spelling correction, a new product name, a tone adjustment, and a market-specific SEO preference should not all be handled in the same way.
| Observed change | Likely response |
|---|---|
| The same concept has multiple translations | Select one preferred term, document the exception, and search existing content for inconsistencies. |
| A translated keyword sounds unnatural | Recheck local search intent and revise the copy; do not preserve a literal phrase solely for keyword matching. |
| A product feature has been renamed | Update the glossary, interface strings, help content, metadata, and redirects or links where relevant. |
| Readers misunderstand an otherwise accurate passage | Review sentence structure, examples, terminology, and cultural assumptions rather than changing isolated words only. |
| Different channels use different levels of formality | Document the channel rule and provide examples instead of declaring one tone correct everywhere. |
Prioritize changes by risk and reach. Product names, safety instructions, legal language, navigation, conversion-focused pages, and high-traffic landing pages usually deserve faster review than low-visibility archive content. Use a translation quality assurance checklist to separate terminology issues from factual, formatting, and functional problems.
When human and machine translation are used together, keep the glossary available before drafting and during review. An AI translation tool can produce a useful first version, but it should not be treated as the authority for brand terminology, cultural nuance, or local SEO. Approved context and human review remain necessary for high-impact content.
When to revisit
Schedule a glossary and style-guide review at least quarterly for an active multilingual site, with a monthly check for newly published or frequently edited content. Revisit the documents immediately when:
- a product, feature, service, or brand name changes;
- a new market or language is added;
- keyword research reveals different local wording or search intent;
- readers, support teams, or reviewers repeatedly flag the same phrase;
- a campaign introduces new claims, slogans, or calls to action;
- the website navigation, URL structure, or content templates change;
- a translator, editor, or AI-assisted workflow joins the process;
- an audit finds inconsistent terminology across live pages.
End each review with three concrete actions: approve or reject pending terms, assign corrections to named content owners, and set the next review date. Archive superseded entries rather than deleting them, so editors can understand why a previous choice changed. For document-heavy projects, also check the requirements before translating; the guide to translating documents online without losing formatting covers practical preparation concerns.
The goal is not to prevent every variation. Good localization allows language to fit the market, channel, and audience. The goal is to make each variation deliberate, searchable, explainable, and consistent with the brand. Start with your ten most repeated terms, one page of tone rules, and a named approver. Then expand the system as real translation decisions reveal what your team needs to track.