Multilingual Pages

Multilingual support lets a single SharePoint site present its content in more than one language so each visitor sees it in their preference. On a communication site you enable alternate languages, and the translation feature then lets you create a language-specific copy of any page or news post. The copies are not translated automatically: you, or an assigned translator, write each translation by hand, and SharePoint serves the right version based on the viewer's personal language setting. Separately, the multilingual user interface translates the site's own chrome - navigation, site title, and footer - into supported languages, and the term store carries multilingual labels so managed metadata terms display in each user's language. Together these out-of-the-box capabilities cover page content, site navigation, and metadata. The trade-off is that real translation is manual work, so multilingual sites need an owner and translators who keep every language version in step.

Managed Metadata, News Post, Page, Site Navigation, Term Set, Term Store

Global intranets: one homepage shown in each region’s language
Multinational HR: policies and news in employees’ languages
Bilingual organizations: serve two official languages from one site
International communications: news posts translated per audience
Localized navigation: menus and labels in the viewer’s language
Multilingual taxonomy: managed metadata terms shown per language

How It Works

Enable languages: a site owner adds alternate languages to the site
Translation copies: each default-language page can have per-language versions
Manual translation: a person writes each translation, not the system
Viewer-based display: SharePoint serves the language from user settings
Translator assignment: owners assign who translates into each language
Update notifications: translators can be notified when a source page changes

Details

Feature Category: Pages & Publishing

Multilingual User Interface

Site chrome translation: title, navigation, and footer adapt to language
Communication sites: the polished page translation experience lives here
Team sites: the interface and default elements support multiple languages
Default language fixed: a site’s default language is set at creation
Per-user preference: each person sets their display language in Microsoft 365
Supported set: a defined list of languages is available to enable

Term Store and Metadata

Multilingual labels: each term can carry a label per language
Default per language: set a preferred label for each working language
Synonyms too: terms support synonyms in each language
Manual entry: translations of terms are added by hand, not generated
Viewer language: users see terms in their preferred language
Shared across sites: translated terms apply wherever the term set is used

Limits and Nuances

No automatic translation: every language version is created manually
Versions drift: source updates do not push to translations automatically
Default language is permanent: it cannot be changed after site creation
Owner overhead: someone must keep all languages synchronized
Not everything localizes: some content still shows in the default language
Right-to-left care: some languages need layout consideration

Common Questions About Multilingual Pages

How do multilingual pages work in SharePoint?

On a communication site, an owner enables one or more alternate languages, and the translation feature then lets each page or news post created in the default language have a matching version in another language. SharePoint shows each visitor the version that matches their personal language setting. The key point is that the translations are written by people, not generated automatically, so each language version is a real, separate page.

Does SharePoint translate pages automatically?

No. SharePoint creates an empty language-specific copy of a page when you ask for a translation, but the actual translating is manual. You or an assigned translator writes the content in the target language. SharePoint helps by tracking which translations exist and can notify translators when the source page changes, but it never machine-translates the page content for you. That manual step is the main effort in running a multilingual site.

What is the multilingual user interface?

The multilingual user interface, or MUI, translates the site’s own elements – the site title, navigation links, and footer – into each user’s display language, separate from page content. A user picks their language in their Microsoft 365 settings and sees the interface in that language where translations exist. It means the framing of the site can feel native even before you translate the individual pages.

How does the term store handle multiple languages?

Each term in the term store has a unique ID and can carry a label in every language the store supports, so the same term displays in the viewer’s preferred language. You designate a default label per language and can add synonyms in each one. As with pages, these translations are entered manually, not generated. Because term sets are shared, translated terms apply everywhere the term set is used.

Can I change a site’s default language later?

No. A site’s default language is chosen when the site is created and cannot be changed afterward. You can add alternate languages on top of it, but the default remains fixed, so it is worth choosing carefully up front. If the default is wrong for your audience, the cleanest fix is usually to create a new site with the correct default language.

When should I get help with a multilingual site?

Multilingual sites look simple until you are maintaining several synchronized language versions of every page and term. Greg Zelfond, the consultant behind LookBook 365, plans the language strategy first – default language, which alternates to enable, who translates, and how updates are kept in step – so the structure holds up as content grows. For organizations serving more than one language, that planning is exactly where his help pays off.