Building Multilingual Websites That Actually Scale
Beyond Translation
Most teams approach internationalisation (i18n) as a last-mile concern—translate the UI strings and ship. But truly scalable multilingual platforms require architectural decisions made early and content operations that evolve alongside the product.
Architecture Decisions That Matter
Locale-Aware Routing
Every locale should have its own URL segment. This is critical for SEO—search engines treat locale-prefixed URLs as distinct pages, enabling proper hreflang signals and geo-targeting.
Message Files vs. CMS
- Message Files (JSON/YAML per locale) work well for UI labels, button text, and short-form content that developers control.
- Headless CMS is preferable for marketing copy, blog posts, and long-form content managed by content teams.
A hybrid approach—message files for the product UI, CMS for editorial content—often provides the best balance.
Right-to-Left (RTL) Support
If your roadmap includes Arabic, Hebrew, or Urdu, bake RTL support into your design system from day one. CSS logical properties make this dramatically easier.
Content Operations
Translation Workflow
- Developers add new keys to the default locale file.
- A CI check detects missing keys in other locales and creates translation tasks.
- Translators work in a dedicated platform with context screenshots.
- Completed translations are merged via pull request with automated formatting checks.
Quality Assurance
- Pseudo-localisation during development catches layout issues caused by longer text strings.
- Contextual review — translators see strings alongside their UI context, not in isolation.
- Automated screenshot diffs flag visual regressions in non-default locales.
Performance Considerations
- Load only the active locale's messages; avoid bundling all languages into the client.
- Use server-side rendering (SSR) for initial page loads to ensure search engine crawlers see fully rendered, locale-specific content.
- Implement Accept-Language header detection for intelligent locale defaulting (with user override).
Takeaway
Multilingual is not a feature—it is an architectural dimension. Teams that treat it as such build platforms that reach global audiences without accumulating technical debt.
