Multilingual CMS
A multilingual CMS is a content management system that links each piece of content to its versions in several languages and manages their publication separately. It has to know which fields vary by language, which stay shared (a date, a price) and what to display when a translation is missing.
Definition and how it works
Two models coexist. Translation at field level keeps shared elements in sync. A separate item or page tree per language allows more local freedom, but updates have to be carried across by hand. The article How to Choose the Best Multilingual CMS: 9 Criteria covers the selection criteria.
Related terms: Multisite CMS · Content workflow · Content management system · Content item · Enterprise CMS · Vanity URL
Resources that cover this term
- Choosing the Best Multilingual CMS: the 9 Criteria That Matter
- European Synchrotron Radiation Facility (ESRF)
- What Is a Content Management System?
- 10 strategic criteria for choosing the best enterprise CMS
- Enterprise CMS: Definition, Key Features and Benefits
- Headless CMS personalization: How to deliver truly adaptive experiences
Multilingual CMS vs localization: the differences
A single site can be multilingual. A portfolio of sites can run in one language.
| Concept | What separates it |
|---|---|
| Localization | It adapts content to a market: currencies, legal notices, examples. It can vary within one language, between the US and the UK for instance. |
| Multisite CMS | Several sites on one platform, each with its own languages. |
| Content workflow | It organizes approvals. In a multilingual setup, it must be able to approve one language without blocking the others. |
Multilingual CMS in practice
A multilingual project is won or lost in the content model, on four decisions. The source language and direction of translation. The list of translated versus shared fields. What happens when a translation is missing. The approval path per language.
Frequently asked questions
Does machine translation make a multilingual CMS unnecessary?
No, it moves the work. A translation engine produces a first draft in seconds, but someone still has to review it, adapt it to the market and publish it at the right time. That is what a multilingual CMS manages, with the status of each language, its approval and its publication.
What should a site display when a page has not been translated?
There is no single answer, but there has to be one, decided in advance: hide the page, show the source language or redirect. What to avoid is silently serving the other language at the translated address, without telling visitors or search engines.