A Practical Guide to Keeping Translations in Sync
Managing content across languages, including what gets translated, who approves it and how updates flow.
Dana Whitfield
Where most projects go wrong
The usual mistakes:
- Translations frozen while the source changes
- Market pages with outdated claims
- Machine translation without review
- One legal disclaimer translated across markets
What good looks like instead
- Define the source language and update flow
- Track which translations are current
- Use in-market reviewers
- Flag content that must differ legally
- Review the translation backlog regularly
Why it matters
Translations drift from the source as pages change, leaving some markets with outdated information.
The specs that matter
| Measure | Figure |
|---|---|
| Source of truth | one language usually leads |
| Update propagation | source changes must trigger translation updates |
| Local review | in-market reviewers catch errors and tone problems |
| Legal variation | some content differs by market for legal reasons |
Knowing when to hand it over
Tip: Bring in help when sites serve several language markets.
Where this comes from
- W3C — Internationalization techniques: authoring HTML and CSS
- Microsoft Learn — Microsoft Writing Style Guide: Global communications
The figures and practices above come from the sources listed.
Working on something like this?
We take on Content Strategy work for teams who want it done once, properly. Tell us what you are building and we will tell you honestly whether we are the right studio for it. Start a project.
Where to go next
Spotted something wrong? Report an error on this page. We correct on the page and say what changed.
