Translation workflows for multilingual websites: memory, glossaries, machine translation and review

Why multilingual sites drift

Most multilingual websites start well. Content is translated for launch, reviewed and published. Then the source language changes: new service pages, updated prices, revised legal texts, product changes. Some updates reach other languages quickly, others late, some never. Within a year, language versions differ in ways nobody planned.

Drift creates real problems. Customers see outdated offers, legal information conflicts between languages, search engines receive inconsistent signals across hreflang versions, and marketing teams lose confidence in non-primary markets. The cause is rarely poor translators; it is a missing process.

The building blocks

Professional translation workflows rely on a few tools and assets that most companies can adopt, whether they work with an agency, freelancers or internal teams.

Translation management system

Software that receives content from the CMS, routes it to translators and reviewers, and returns translations.

Translation memory

A database of previously translated segments, reused automatically so identical or similar sentences are not translated again.

Glossary or termbase

Approved translations for product names, legal terms, industry vocabulary and terms that must not be translated.

Style guide

Rules per language for tone, formality, forms of address, spelling variants, numbers, dates and currencies.

Exchange formats

Standard formats such as XLIFF that allow content to move between CMS and translation tools without copy and paste.

Machine translation and post-editing

Machine translation has improved considerably, and large language models can produce fluent text. Fluency is not the same as accuracy. Machine output can mistranslate terms, change meaning subtly, invent details, miss legal nuance or use the wrong register, and errors are harder to spot because the text reads well.

A common approach is to decide by content type. Machine translation with light review may be acceptable for internal documentation or high-volume, low-risk content such as product attributes. Marketing pages, legal texts, pricing, medical, financial and regulated information need full human post-editing or translation by qualified linguists. Glossaries and translation memory should be applied to machine output as well.

Be transparent about quality. If content has been machine translated without native review, avoid claiming otherwise, and consider noting it for content where accuracy matters to the reader.

Review in context

Translators often work with text segments stripped from their layout. A word that fits a button in English may be too long in German, a headline may break awkwardly, and a sentence may be ambiguous without the image beside it. Reviewing translations on the actual page catches issues that segment-by-segment review misses.

Some translation management systems offer visual context or preview links. At minimum, reviewers should check key pages in staging for each language, including navigation, forms, error messages, emails and checkout, not only marketing copy.

Design should anticipate language differences: text that becomes longer, right-to-left scripts where relevant, different date and number formats and names that do not follow Western conventions.

Keeping languages in sync

Connect the CMS to the translation workflow so that changes in the source language create translation jobs automatically. Track which pages are outdated in each language, and decide for each content type whether an outdated translation stays online, is hidden or falls back to the source language until updated.

Legal texts, prices and product availability should never be left inconsistent between languages. Marketing articles can sometimes be published in fewer languages, as long as hreflang annotations only link pages that truly correspond.

Governance and cost

Assign an owner for each language who can approve terminology and resolve questions, ideally someone close to the market. Keep glossaries and style guides in shared, maintained locations rather than in individual translators’ files.

Translation memory reduces cost over time, because repeated and similar segments are charged at lower rates or not at all by many providers. Owning the memory and glossary, rather than leaving them only with a supplier, protects the investment if the company changes providers.

A clear workflow costs less than repeated emergency fixes and gives every market a website it can rely on.

Where this sits in what we do

This article covers one decision inside a wider engagement. The solution page sets out how that engagement runs, what it includes and what it costs to find out.

• Digital Growth — The ongoing programme — strategy, content, paid, organic and reporting — run as one thing that answers to pipeline rather than to channel dashboards.
• When to build software instead of buying it
• The order of operations in a digital transformation
• NIS2 for digital suppliers: what changes when your customers are in scope
• Passkeys for customer logins: fewer resets, less phishing and the recovery flow you still need
• All insight articles