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

Multilingual planning

The decisions a business takes before publishing in several languages with Exponential - which languages and markets, addresses per language, fallbacks for untranslated content, who translates, and the limits to know.

Download as PDF

Address: https://doc.exponential.earth/exphelp/viewer/help/businesses/multilingual/multilingual-planning.md

On this page

Multilingual planning

This page is for owners, marketing leads and project managers who plan a website or store in more than one language. It lists the decisions to take before the build, explains each in business terms, and points to the technical page for the team that implements it. The longer planning guide for project managers is Planning multisite and multilingual projects.

Contents

  1. Start from markets, not languages
  2. How Exponential shows languages
  3. Addresses per language
  4. What visitors see when a translation is missing
  5. Who translates, and who approves
  6. Limits to know before you promise
  7. The decision table

Start from markets, not languages

A language is a cost that recurs: every page you publish later needs a translation, every correction too. Before adding one, write down for each market:

  • To do: Which customers or members it reaches, and what you expect from them.
  • To do: Which content they need: the whole site, the shop, or only key pages (products, contact, terms).
  • To do: Who writes and checks the language: staff, an agency, a partner, or a machine draft with a human review.
  • To do: Whether prices, taxes, shipping and legal texts differ in that market (see Currencies, dates and formats and the Stores section).

A smaller set of well-maintained languages usually serves customers better than many half-translated ones.

How Exponential shows languages

From Content languages:

  • Adding a language translates nothing and changes no site address. Editors translate content; an administrator adds the language to the language list (SiteLanguageList) of each siteaccess that should show it.
  • Each siteaccess shows an object in the first language of its list that the object has.
  • Every object has a main language, the one it was created in or chosen later.
  • Removing a translation deletes content for good; removing a whole language is only possible when nothing uses it, so it never deletes content.

Most multilingual sites therefore have one public siteaccess per language, all sharing one database and one content tree (Building a multilingual site).

Addresses per language

ShapeExampleGood for
Path per languageexample.com/de/One certificate, one host; simplest
Host per languageexample.de, de.example.comCountry domains
Host and pathexample.com/de on one host, other hosts elsewhereMixed setups

From Language switchers and addresses per language. The start page can also redirect once to the visitor's language, chosen by host and browser language, with one address per language and no cookie (Siteaccess by host prefix, and the redirect to the language).

Note

Search engines understand hreflang links between language versions. Exponential does not print them by itself; the design builds them from the language switcher's result (Telling search engines). Put this on the design team's task list.

What visitors see when a translation is missing

Decide this per language siteaccess:

You wantSetting (for the technical team)
Show English where German is missingGerman first, then English in the language list
Hide what is not translatedOnly German in the list, untranslated objects not shown
Show everything in its main language when nothing else fitsShowUntranslatedObjects=enabled
A logo or a PDF appears in every language as it isMark the object "always available"

Source: Fallbacks and untranslated content. For a store, hiding untranslated products can hide things customers want to buy; showing them in another language can confuse. Decide product by product category if necessary.

Who translates, and who approves

Limits to know before you promise

LimitValueSource
Content languages per installationat most 62 on 64-bit PHP, 30 on 32-bit PHPLanguages, section 11
A language added and never usedstill takes its place until removedsame
Administration in the editor's own languagecomplete in every shipped translation; English for a language without oneLanguages, section 2
Changing the default content language of a site with contentcan hide objects that do not exist in the new language10.14 Multi-language sites

The decision table

Language plan for <organization>                               <date>

| Market | Language (locale) | Address | Fallback language | Untranslated: hide/show | Translator | Approver |
|--------|-------------------|---------|-------------------|-------------------------|------------|----------|
|        |                   |         |                   |                         |            |          |

Content in scope per language: <whole site / shop / key pages>
Right-to-left languages: <none / list>
Machine-assisted drafts: <yes, reviewed by ... / no>
Content languages in use: <n> of at most 62

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