Skip to the content
Documentation
Help Start
Reading in:
  • German: 9,059 of 9,059 pages
About the help in other languages
All help pages

Adding a language

What a site owner plans and decides before adding a content language to an Exponential site - adding a language translates nothing and shows nothing by itself, what the siteaccess needs, translators and approvers, which…

Download as PDF

Address: https://doc.exponential.earth/exphelp/viewer/help/customers/growth/adding-a-language.md

On this page

Adding a language

This page is for the owner who wants to offer the site in another language. In Exponential this has two technical halves (a content language, and a siteaccess that shows it) and one large human half: the translation work. The administrator's steps are in Content languages; the planning view is Multilingual planning.

Contents

  1. What adding a language does, and does not
  2. Decisions before you start
  3. The steps, and who does them
  4. What to translate first
  5. Launch checks

What adding a language does, and does not

From Content languages:

  • Setup > Languages > Add language adds a content language; 132 locales are in the list on a standard installation, and a custom one can be made from a locale file.

    Setup, Languages: the content languages with the Add language button above the list
    Setup, Languages: the content languages with the Add language button above the list
  • Adding translates nothing and changes no siteaccess: no visitor sees anything new yet.

  • What a visitor sees is decided per siteaccess by SiteLanguageList: the content languages it shows, most preferred first. An item is shown in the first of these it has; items in none of them are hidden unless always available (or ShowUntranslatedObjects is enabled).

  • A content language is not the interface language: buttons and menus come from the siteaccess's Locale and the translation files.

  • An installation holds at most 62 content languages.

Decisions before you start

QuestionOptionsRead
How do visitors reach the language?a path (/de), a host (de.example.com) or a domain per countryLanguage switcher and language URLs
What do visitors see when a page is not translated?hidden, or shown in the main languageContent languages
Everything, or a subset?a full site, or the main pages onlyMultilingual planning
Who translates and who approves?staff, agency, freelancers, assisted by the writing assistantTranslation routine
Right-to-left?Arabic, Hebrew, Persian and others need the design to support itRight-to-left markets
Currencies, dates and formats?the locale decides dates and numbers; a store also needs pricesCurrencies, dates and formats

The steps, and who does them

StepWho
1. Decide the questions aboveowner
2. Add the content language in Setup > Languagesadministrator
3. Create or adjust the siteaccess, its address and SiteLanguageList; add a language switcher to the designpartner
4. Give translators accounts limited to the language; set up per-language approval if wantedadministrator (Approvals and review)
5. Translate the content (below)translators
6. Test on the new address, signed outowner and a native speaker
7. Make the address public; tell search engines (sitemap per language)partner (XML sitemaps)

The new siteaccess can be tested before it is public; ask your partner for a test host (One installation, many sites).

What to translate first

  1. The start page and the menu folders: visitors reach everything else through them (Translation workflow).
  2. Contact, legal and privacy pages.
  3. The pages visitors from that market use most (your search statistics and analytics help).
  4. Forms and their confirmation texts; newsletter lists for that language.
  5. Everything else, in the order of the Content calendar.

Launch checks

  • To do: Every page in the menu has a translation, or is deliberately shown in the main language.
  • To do: The language switcher leads from each page to the same page in the other language.
  • To do: Dates and numbers are written the local way.
  • To do: Forms, error messages and mails are in the language.
  • To do: A native speaker read the main pages.
  • To do: The Multilingual checklist is ticked off.

Become an Exponential Partner

Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.

Something wrong on this page? Report an error

Documentation license

This documentation is free documentation, licensed under the GNU Free Documentation License 1.3 or later.

Exponential Copyright © 1998-2026 Exponential Foundation and 7x