Translating words is not localisation
An interface can display four languages correctly and still feel foreign. The cause is often structural: a sentence cut to fit Vietnamese, a date kept in an English reading order or a button that does not say what will happen. Good localisation starts with the context of an action.
Keep one meaning, allow different phrasing
Every message needs a stable key and a description of when it appears. A translation may change word order, formality or counting rules while protecting the same meaning and state. Do not assemble sentence fragments in the UI; pass data into a complete message.
- Name keys after meaning, not the current Vietnamese sentence.
- Record the speaker, audience and action state.
- Use each locale’s date, number and plural rules.
- Let a native speaker review the whole situation, not one line.
Length is part of the design
Japanese and Chinese can be compact, while English or Vietnamese may need more words for the same idea. Instead of forcing one height, allow the layout to breathe, set deliberate limits and inspect errors, tables and small buttons. A correct translation that is clipped is still a broken experience.
SEO needs shared meaning, not shared URLs
Each locale deserves its own title, description and canonical URL, while hreflang links explain their relationship to search engines. Slugs can remain stable or be localised with care; the important part is not creating empty duplicates just to reach a language count.
- Review titles and descriptions in the real language.
- Write image alt text for the locale and the actual scene.
- Never use translated copy as business data.
- Make the fallback explicit when a translation is incomplete.
The editorial workflow is a feature
When a post is ready, the admin should show which locales are complete, which cover lacks alt text and which field is outside the SEO budget. A small completion state makes publishing accountable instead of leaving notes across chats. A translation may arrive later, but it should never arrive silently.
Good localisation does not make languages identical; it makes each language feel natural inside the same product.
Conclusion
Stable keys, context and a review path let content grow without compounding translation debt. When a fifth locale or a new brand arrives, the team can still tell which strings are UI, which are data and where a native speaker must decide.