Multilingual & Localization
A multilingual CMS that speaks your customer’s language
Deploying multilingual content across channels ensures that your customer experience is both borderless and engaging for all.
With dotCMS, you can publish content in different languages, configure the language of your content based on the geolocation of the user, and give end users the ability to quickly switch between languages.
How Multilingual Headless CMS Works
With an extensive list of NoCode capabilities and an API-first infrastructure, dotCMS is the multilingual content foundation that you have been longing for. With dotCMS it is simple to build and deliver engaging experiences for your brand, regardless of the channel.
Translation Workflow
Translation Workflow
Deliver content in the language of your audiences by integrating the content management process with external translation engines and services. Streamline operations for ad-hoc and continuous processing.
FAQ: Multilingual & Localization
In dotCMS, each piece of content can have a version in every language you add. Every language version belongs to the same content item and uses the same URL, and dotCMS shows each visitor the version in their language. You translate at your own pace, one market at a time. If your markets need different content rather than translated content, you can give each language its own folder or its own site in the same dotCMS instance, with its own permissions.
Yes. dotCMS has two automatic translation options, and both run as a step in your content workflow. The built-in Google Cloud Translation integration can be set up for one site or all of them. AI translation in dotAI uses the AI provider you have connected. Either way, an editor writes the content once and dotCMS creates a version in each language you choose. dotCMS recommends that a fluent speaker
Yes. AI translation in dotAI can work from a glossary of up to 1,000 approved terms, stored as language variables, so it uses your translations for product names and specialist wording. You can also exclude fields from translation entirely, such as legal text that must be written by a person.
Yes, using rules. A rule can set a visitor's language based on their browser language, country or location. You can also give each language its own URL path, such as /es/. Country and location targeting relies on a GeoIP database.
Yes. Each locale in dotCMS pairs a language with a country, such as en-GB, en-US or es-ES, so each region can have its own version of the same content. You can also create custom locales.
Every headless request can ask for a specific language, through the Page API or content queries including GraphQL. Your website, app and other channels all pull the same published translation from one place. Marketers can switch between a page's languages in the Universal Visual Editor to check each version.