Translation Glossary — Keep Terminology Consistent

Why you need a glossary

Every site has words that should never be translated. Your brand name. Your product names. Industry jargon you’ve chosen to leave in the source language. Technical terms that lose meaning when translated. If you rely on a human translator to remember the list, mistakes will happen. If you rely on AI, they will happen faster and at scale.

Lang Forge’s glossary solves this by pinning specific terms with explicit rules, and enforcing those rules everywhere — in AI translation prompts, in visual editor validation, and in WP-CLI batch jobs.

What a glossary entry looks like

Each glossary entry has:

• Termthe word or phrase in the source language
• Translation (optional) — an approved translation, if one exists
• Languageswhich languages this rule applies to (or “all”)
• Do-not-translate flagif set, the term must appear verbatim in translations
• Case-sensitive flagwhether the match is case-sensitive
• Notesfree-text context for your team

You can mark a term as “do not translate” in any specific language while allowing it to be translated in others.

How the glossary is enforced

In AI translation

Before every AI translation request, Lang Forge appends the relevant glossary entries to the prompt. The AI is instructed to preserve terms with the do-not-translate flag, to use the approved translation for terms that have one, and to flag any deviation.

In the visual editor

As you edit a translation by hand, the visual editor highlights any glossary violation — a term that should not be translated but was, or a term that should use the approved translation but doesn’t. You see the problem before you save.

In XLIFF export

When you export translatable content as XLIFF for a professional translator, the glossary is embedded in the XLIFF file’s metadata. Professional TMS software understands this format, so your agency’s translators see the same rules you set in Lang Forge.

CSV import and export

Bring your existing glossary with you

If you already have a glossary in a spreadsheet — exported from a different translation tool or maintained by your team in Google Sheets — you can import it in one click. Lang Forge accepts a simple CSV format:

term,translation,language,do_not_translate,case_sensitive,notes

Export works the other way for handoff to translators or for backup.

Use cases

• SaaS companies with product names that should stay in English across every language
• E-commerce stores with brand names that must not be translated
• Technical documentation with API names, class names, and method names
• Legal and medical content where specific terms have regulatory meaning

Ready to lock your terminology?

Get Lang Forge — from $54/year →

The glossary is included in every plan — free and paid — with unlimited entries, CSV import/export, and enforcement across manual translations, AI translations, and WP-CLI batch jobs. Glossary validation inside the visual editor is part of the Pro tier.