Locale drift is what happens when localized content slowly falls out of alignment with the source it was translated from. A price changes on the English page but not the German one. A feature is renamed in the product, and three of your eight languages keep the old name. No single change looks serious. Aggregated across markets and release cycles, they add up to language versions that no longer say the same thing.

Drift is rarely a translation-quality problem. It is a workflow problem: source content keeps moving, propagation is manual, and no one owns keeping the versions in step. That means it is preventable — but only with controls in the workflow, not with better individual translations.

Why locale drift happens

Four conditions produce almost all of it:

• The source keeps changing and updates ship in one language first.
• No single source of truth — content lives in a CMS, a few spreadsheets, and some email threads, so no one can say which version is current.
• Propagation is manual — someone has to notice a change and remember every place it needs to be reflected, in every language.
• Ownership is unclear — when everyone is responsible for keeping a locale current, no one is.

Five controls that prevent it

1. Establish a single source of truth. One canonical version of each content item, with a clear record of what is current. Everything downstream localizes from it. If you cannot answer “which version of this page is live right now?” for your top markets, fix that before anything else.

2. Enforce terminology, don’t leave it to preference. The term used on the label, in the UI, in the help center, and on the website must be the same term in every language. That requires a maintained glossary and termbase applied on every job — not each translator’s individual choice.

3. Define review ownership per locale. Every language should have a named owner or review path, so a change has a clear route to being reviewed and approved rather than sitting in limbo.

4. Build update propagation into the workflow. When the source changes, the workflow — not a person’s memory — should surface every affected asset in every language and route it for update on a deadline. This is where most drift is actually stopped.

5. Keep audit-ready version records. A record of what was published, where, and when. In regulated categories this is a compliance requirement; everywhere else it is what lets you diagnose drift when it appears instead of guessing.

A quick self-check

Ask three questions about your multilingual content:

• Can you name the current version of any page across all markets?
• Is there one enforced glossary, or does terminology vary by translator?
• When the source changes, does something automatically find every affected translation?

If the answer to any of these is no, that gap is where drift enters. It is almost always cheaper to close it than to keep re-reconciling versions after the fact.

Keeping localized content aligned as the source changes is the core of website localization done as a workflow rather than a one-time job. See how we structure that workflow for where the controls above fit.