A Translation Glossary for Your Website: Which Terms Belong to Which Language Direction?

A translation glossary should express approved terminology for a particular source and target language, not act as a universal replacement list. Before commissioning glossary integration for a multilingual website, decide which meanings need controlled wording, who approves each direction and what happens when a term means different things in different parts of the business. Uploading a spreadsheet is only the beginning of that decision.

Start with a meaning, not a column of familiar words

Imagine a company whose English website uses “case” for a customer support matter and also sells a protective case. These are different concepts even though the source spelling is identical. A single unexplained preferred translation can make one part of the website wrong while appearing perfectly consistent elsewhere.

Prepare a small terminology brief containing the concept, an example sentence, the intended audience and the approved target expression. Record whether the expression is a product name that should remain unchanged or ordinary wording that should read naturally. Use fictional or public examples rather than uploading confidential customer material during a demonstration.

This is not a request to translate every sentence in advance. Concentrate on words whose inconsistent treatment would confuse a customer about a product, service or next step. A qualified language reviewer should resolve terminology disputes before the developer turns the list into machine instructions.

Approve the direction explicitly

DeepL’s glossary management documentation describes a glossary as containing one or more dictionaries. Each dictionary maps source phrases to target phrases for one language pair in one direction. A reverse mapping requires another dictionary.

For the commissioning brief, that means English to German approval is not evidence of German to English approval. Two English expressions may intentionally have the same German translation; automatically reversing both does not establish which English expression is appropriate. Ask for separate review of every direction actually used by the publishing workflow.

Do not assume a glossary configured for one pair covers the rest of a multilingual site. List the required source and target languages alongside the part of the site using them. Verify current provider support before promising a working combination. Adding a language to the content plan and enabling a supported glossary dictionary are separate tasks.

Consistency does not mean identical spelling in every sentence

DeepL explains that it adapts glossary entries to grammatical features such as case, gender and tense where the target language has inflection. A reviewer should therefore judge the translated sentence, not simply search for an exact unchanged target string.

Choose representative sentences that exercise the term in context, including a plural or another grammatical form where relevant. A product name may need deliberate treatment different from an ordinary noun. Decide with the reviewer what must remain recognisable and what should change naturally. A glossary is neither a language-quality certificate nor a substitute for checking the rest of the sentence.

For a genuinely ambiguous source word, ask how the integration will keep the appropriate terminology context separate. That might mean separate content workflows or separately selected dictionaries, if the chosen system supports the arrangement. Do not promise that the glossary will infer every business meaning from one conflicting entry.

Make selection and editing visible

In the documented DeepL API workflow, translation requests must identify the glossary and explicitly specify the source language; automatic source-language detection cannot be used with glossaries. The practical requirement is to demonstrate that the intended content takes the intended dictionary path, rather than merely showing that a glossary exists in an account.

Editing deserves a separate check. DeepL documents dictionary replacement and entry merging as different operations. Ask whether an imported file replaces the complete dictionary or adds to existing entries. Otherwise removing an outdated row from a local spreadsheet may not have the effect the editor expects. These are provider-specific integration details, not a guarantee about every translation plugin.

Accept a controlled terminology workflow

Use a small approved example set to check the forward direction, any separately approved reverse direction, an ambiguous term and natural grammatical forms. Change the selected dictionary and inspect the next draft. If replacement imports are in scope, verify that an omitted obsolete entry is handled as agreed without deleting unrelated approved terminology.

Keep the reviewed input set and resulting drafts available for comparison. Publishing remains a separate editorial decision; do not claim that changing a glossary repairs existing public pages automatically. Record which content needs another translation and review after a terminology decision changes.

Bring this terminology brief to a website or web-app project discussion. The useful deliverable is a demonstrable connection between meaning, language direction and reviewed output, not an impressive count of glossary rows.