To translate SharePoint pages into another language, enable multilingual features in the site’s language settings, add your target languages and open a default-language page’s Translation pane. Choose Create for all languages or select specific languages. SharePoint creates language copies for an editor to translate; it does **not** automatically translate the authored page content in the standard modern multilingual workflow. Publish the reviewed page so readers with the appropriate language preference can see it.
People searching for **SharePoint multilingual pages**, **how to translate SharePoint sites**, **SharePoint translation settings** or **translate SharePoint news** need a distinction between language-aware menus, manually translated page copies and file contents stored in document libraries. A translated site title doesn’t mean linked policies, PDFs or records are translated or accessible.
Quick setup: create a translated SharePoint page
Open the site → Settings → Site information → View all site settings → Language settings → enable multilingual translation → add target languages. On an approved default page, select Translation and create language copies. Have a permitted translator edit the copy, check facts and links, then Publish or Submit for approval as appropriate. See Microsoft’s official multilingual SharePoint guide.
Fifteen principles for trustworthy multilingual SharePoint
How multilingual SharePoint differs from ordinary machine translation
Modern SharePoint multilingual features let an authorized site owner create a corresponding page for a selected language, then assign someone to translate and publish it. Microsoft’s official documentation states that creating language copies does not automatically translate their page content. Published versions can be shown to readers who prefer the corresponding language. This is a workflow for maintaining reviewed pages, not a guarantee that every list, file and personal document in the site has been rewritten by a machine.
Choose a source site’s default language carefully
SharePoint’s default site language is set when the site is created and cannot normally be changed later. Plan the appropriate source language before building a major multilingual intranet. The default language of site menus and the approved source text are related but not identical design decisions. If the project already has a default-language site, use its supported multilingual options instead of promising that changing one user preference will rebuild the whole source site in another language.
Enable translation into multiple languages
Microsoft’s supported workflow begins with the site Settings menu, Site information, View all site settings and Language settings. Turn on Enable translation into multiple languages and add languages with the selection control. A site owner can assign translators to particular languages. The assigned person still needs edit permission to modify a page; being named as a translator does not automatically grant authorization. Check the actual eligible site type and administrator settings before proceeding.
Create language versions from an approved default page
Open the default-language page and select Translation at the top. The translation pane can create versions for all enabled languages or only selected target languages. SharePoint creates corresponding pages, which an editor translates. If the default page has unpublished changes, Microsoft cautions that it may need to be republished so language pages and news web parts display properly. Do not create translations from a stale source and then treat their publication as proof the current original was reviewed.
Translate, save draft and publish only when approved
A designated translator may receive an email with a Start translating button. In the target page, choose Edit and replace source-language prose with approved target-language content. Save changes as a draft until the wording, layout, links, images and authorization have been reviewed. Publish or submit for approval according to the site’s actual publishing rules. A translation page’s draft status is not a live public edition, even when its editor preview looks complete.
Approval and publishing are separate controls
When SharePoint page approvals are enabled, the source and target versions may both require approval and publication before readers can see the target version. A translation request, translator assignment or saved draft does not imply the page was officially released. The site owner should define who may translate, who verifies factual or legal claims, and who approves publication. For important policies, preserve each actor’s authority and the status of the required approvals in every language.
Language preference controls the displayed version
SharePoint uses viewers’ personal language and region preferences to select available language editions, subject to the site’s configuration. The page’s language dropdown can switch between available translated versions for the current browsing session. This does not necessarily change the viewer’s persistent Microsoft 365 language preference. If a target page is absent, SharePoint may fall back to the default language content in appropriate web parts. Test as a real reader rather than assuming every colleague sees your editor’s chosen language.
Site navigation and page body are not the same translation surface
The multilingual user interface can show localized site titles, navigation labels, default columns and descriptions according to settings. These UI translations are distinct from the authored content inside modern pages. Microsoft’s Overwrite site translations option applies to certain UI elements, not to the authored modern page body. A translated navigation label can be useful while the linked policy page still contains English instructions; inspect both the menu and its actual destination.
Updates to the source do not automatically update translations
Microsoft explicitly states that changes to a default-language page are not automatically synchronized into every translation page. After a source update and republishing, assigned translators can be notified that a target needs review. A Spanish page with yesterday’s refund terms may remain unchanged after the English policy changes. Keep a revision ledger and request target approval for material updates instead of treating automatic notification as automatic rewriting.
Translate SharePoint news and highlighted content properly
Multilingual SharePoint can show language-appropriate news posts and pages in News and Highlighted content web parts after they are approved and published. An untranslated source post may appear in the default language. A site owner should not interpret fallback as failure, or promise that every news card will display translated text when the target page was never published. Test the home page and the individual news article for each supported language.
Document libraries and Office files need their own workflows
A SharePoint library may contain Word documents, PDFs, spreadsheets, images and other assets. Enabling page translation does not automatically localize all the contents of those files. A Word document may require its own authorized document translation; a scanned PDF may require checked text extraction; an Excel model needs separate care with calculations and numeric data. Preserve exact file IDs, revisions and original access rules. A translated page’s link should not claim a target-language policy exists if its destination is still the source edition.
List and column translations are functional, not just prose
Lists contain typed values, lookup fields, dates, statuses, labels and business rules. SharePoint can present certain interface elements and custom column labels through multilingual UI features, but data records and workflows require separate checking. Renaming a target display label must not turn Pending review into Approved or change what a filter selects. Test a few representative items, including one blocked and one completed, before claiming users in both languages see the same status.
Keep SharePoint permissions, audience and links aligned
A translation page must not expose personal records or confidential links to an audience that could not access the source legitimately. Translator assignment alone does not grant edit rights, and a published page can have links to more restricted documents. Check the actual target recipient’s access, not only the editor’s. Translation can widen comprehension without widening the permitted audience. Never grant public access to an entire document library simply to repair one translated download link.
Handle date, currency and technical identifiers faithfully
An intranet page may contain product model codes, legal deadlines, budgets and technical abbreviations. Translate descriptions but preserve real figures, their units and identifying strings. A fee of SGD 250 does not become EUR 250 because the target is French. An international deadline must retain its actual time zone or a verified converted instant. For a sensitive policy, preserve may, must, not, unless and subject to exactly in functional meaning.
Use a practical multilingual site QA process
Create a small matrix of source page, translated page, current status, reviewer, navigation label, linked resources and last source update. For each language, open the site as a reader using the relevant language preference. Verify the landing page, one news post, one legal or business rule and one download link. Ask the reader what to do next. If the target directs them to a different form, amount or authority, revise before release.
Official documentation: Create Multilingual SharePoint Pages · Multilingual Features Overview · Overwrite Site Translations · Notion Pages and Databases · Master Art of Translation.
Forty-two practical SharePoint translation cases
These fictional scenarios show how language copies, navigation, permissions, documents and publishing can affect what an employee or customer actually understands. The quality measure is accurate source meaning and a usable, properly authorized final site.
1. A site owner expects machine translation after clicking Create
The SharePoint multilingual pane creates a French copy of an English page, and the owner assumes the copy has already been translated. Microsoft’s standard modern page workflow actually prepares content for an editor to translate manually. The target page may still show original text until someone updates it. Review every important field, assign an authorized translator and publish the completed target through the site’s actual approval process rather than describing an empty or unedited copy as final.
2. The default language was chosen incorrectly
A company built a SharePoint communication site in a language it later wishes to change. Microsoft says the default site language is fixed at site creation. Do not promise a Settings toggle that converts the underlying source site to another default. Use the supported multilingual feature for alternate displays or plan a separately authorized migration if a different source is truly required. Existing URLs, permissions, navigation and files need a coordinated approach.
3. The translator receives a notification but lacks edit rights
An administrator enters a staff member as the Spanish translator for a site. The employee opens the request email but cannot edit the target page. Microsoft’s documentation cautions that translator assignment does not automatically grant the required site permissions. Give only the appropriate editing access through the authorized site-owner process, then return to the target page. A translation request email is not a security role or proof that the person can publish.
4. A Spanish page is left in draft
A translation worker finishes the content but chooses Save as draft rather than Publish or the required Submit for approval action. Colleagues using Spanish may continue seeing the default-language edition. Check the translation pane’s status and any page-approval workflow. A draft preview that looks correct to its editor is not evidence the page is live to the intended audience. Publish only after authorized QA and approval.
5. A page approval is mistaken for automatic translation
An organization enables page approvals and expects approving the source to convert all language copies. These are separate operations: translators edit copy, reviewers approve, and the site publishes language versions. Check both original and target status. A policy can be factually approved in English while its German wording still needs language review. Do not confuse a notification about source changes with a completed target release.
6. A source page has unpublished changes
The default English policy has a pending edit when its owner generates target-language copies. Microsoft warns that republishing the default page may be needed for translations and language navigation to display correctly. Clarify which source revision is approved before translation. Publish the authorized original and then check each language version’s actual association. Avoid circulating a translation that combines old approved text with new unapproved policy changes.
7. A legal disclaimer is missing from the target page
The English source page has a refund condition in a collapsible section, while the translated French copy includes only its main marketing text. A reader may infer a broader right than the organization offers. Translate meaningful hidden or expandable web parts as part of the intended deliverable. Inspect each interactive section and obtain responsible approval for legal terms before publishing a target page as complete.
8. A source policy changes after publication
A company corrects its leave policy in English, republishes the source and receives translator-update notifications. The existing Malay copy remains old until a human edits it. Microsoft’s multilingual system does not automatically synchronize the actual authored target words. Track source revision and required language updates, and mark outdated target content as pending or superseded. A notification is a useful trigger, not proof the target already reflects the correction.
9. A source update affects only one language
A project owner changes a safety instruction and the Japanese translator completes the update, while the Spanish page still contains the previous rule. Different groups may then take different actions. Maintain a translation status ledger listing each required language, last reviewed source revision and publishing status. Do not declare the whole site updated because one target edition is current. For safety-related instructions, escalate discrepancies until all required audiences receive the right information.
10. An untranslated news article falls back to default language
A new SharePoint News item is published only in English, but the Spanish site navigation is already translated. Microsoft’s guidance explains default-language fallback when a matching news page isn’t available. Readers may see English headlines in the translated site. This is not proof that automatic news translation has failed; the target article may not exist. Create, edit, approve and publish a Spanish news copy as needed, then test its appearance in the actual News web part.
11. A home page wasn’t translated
Individual French news posts exist, but the site home page has no approved French version. The News and Highlighted content experiences may show default-language content according to SharePoint’s documented fallback behavior. Test the target-language home page, not just the article’s direct URL. If the organization wants a coherent French landing experience, create and publish the relevant approved home-page translation and verify the user’s language settings.
12. The language dropdown doesn’t show a new page
A translation has been drafted, but the language selector on the public page does not include it. The source may need republishing, the target may be unpublished or the page association may be broken. Microsoft’s multilingual guide documents checking the default page’s Translation panel and republishing after fixing associations. Avoid inventing unrelated DNS or browser configuration explanations before verifying page and publishing state.
13. A user changes the language dropdown but not personal preferences
A visitor switches a SharePoint page’s dropdown to Japanese and assumes this permanently changes their Microsoft 365 interface language. Microsoft’s guidance says this page-language choice applies to the browser session, while personal language and region preferences independently influence normal site display. Describe the scope accurately. Readers can choose a target page without rewriting their account profile or every organization’s site.
14. A translated site menu points to an English policy
An organization translates its navigation label into Spanish but leaves the linked source policy as English-only. A user may infer the linked rules are also Spanish. Check actual destinations and target-language availability. A menu’s words and the page body belong to different localization surfaces. Link to the approved translated policy where it exists, or describe the original resource’s language honestly instead of promising a non-existent version.
15. Overwriting UI translations does not rewrite page content
A site owner enables SharePoint’s Overwrite translations option and expects all Spanish modern page content to refresh after edits to English navigation. Microsoft explicitly states this option concerns certain site interface elements and does not apply to authored modern page body content. Maintain a separate translation-update workflow for pages. A working navigation setting is not evidence that a policy paragraph or news article has changed.
16. One language gets a navigation term with a different meaning
The source menu uses Policies for current organizational rules, but a target label uses a word meaning casual advice. The reader may not realize the linked content contains mandatory requirements. Verify the functional category and choose a term appropriate to an official rule set. Check which pages the menu opens and whether the audience correctly distinguishes helpful guidance from binding policy.
17. A translated page links to private employee records
A target-language HR announcement contains a link to a spreadsheet with personal records. The translator tests the link using their broad editor access and assumes every reader can open it. Verify access from an intended staff account and review whether the target’s audience actually needs that data. Do not widen permissions on the entire library to make one language page functional. Provide a suitable authorized summary instead.
18. The PDF in a library remains in English
A German SharePoint policy page explains the new process in German but its Download handbook button opens an English-only PDF. Enabling multilingual pages does not translate the contents of stored files automatically. The editor should identify the linked PDF’s actual language or create a separately approved German file and link to it. A translated button is not the same as a translated attachment.
19. A scanned PDF is included in a translated page
A compliance page embeds a photographed signed form. The surrounding webpage is localized but the scan remains in the original language. A reader may miss an exclusion in the image. Determine whether a translated reading copy is authorized and prepare it separately using a verified source transcription; do not present the scan as fully translated or as a newly signed legal instrument. Preserve the original’s formal status.
20. A list column’s status is mistranslated
A SharePoint task list contains Pending review, Approved and Completed. A target-language label describes Pending review as Already approved. Users may bypass a real control. Distinguish data values from interface labels and verify each source status’s functional meaning. Test one item at each stage and review any flow or report that uses the field before renaming shared categories.
21. A financial total is rewritten while translating a list
A project list shows SGD 12,500 as an approved budget. A translated report casually changes the currency to EUR 12,500 without conversion. This changes the amount’s denomination. Keep typed numeric values and their units stable, or use a separately authorized calculation and explicit rate. A target view should convey the same actual budget and project scope as the source.
22. A date changes with locale formatting
A source page displays 04/05/2026, and a target reader uses another month-day convention. The translator guesses the event date rather than inspecting the underlying calendar value. Confirm the actual day and write an unambiguous target label when necessary. Language preference can affect display, but it is not evidence that the true deadline moved. Time-zone conversions require the relevant date and zone.
23. A target-language approval request goes to the wrong person
A translator assigns a publication request to a person with the same surname as the authorized manager. The recipient may have no approval authority, even if they can edit the page. Keep exact identities and approval roles. Check the organization’s publishing workflow before making the target live. Translation is neither a substitute for access control nor permission to assign publication to an unrelated colleague.
24. A page says Published while its translation isn’t approved
A source SharePoint page is publicly published, and a draft Korean version exists. The editor tells users the Korean policy is live because the English source is visible. Check language-specific approval and publishing state in the Translation pane. A translated draft is not an approved public page. SharePoint’s language selector cannot replace the authorized publication decision for each edition.
25. A page title changes its legal scope
An English page is called Employee Benefits for Singapore Staff, while the French target omits Singapore and says Employee Benefits for Everyone. Readers outside the covered jurisdiction may infer eligibility the policy never granted. Preserve geographic, role and contract scope. A clear localization should not remove the source limitation, even if it makes the headline shorter and more welcoming.
26. A card in Highlighted content leads to the wrong language
A target-language home page presents a German title, but its highlighted card opens the default English article even though a German copy exists. The site might be missing an approved association, the target page may be unpublished or the web part could need review. Test the actual card and publishing status in the user’s language. Do not claim automatic matching without verifying the final navigation behavior.
27. A user’s preferred language isn’t supported on the site
A user prefers a language that the organization has not enabled. SharePoint may display default content according to its fallback behavior. Do not tell the user that switching account language guarantees an authored page in that language. Check which target language copies exist and which ones are approved, then offer an authorized alternative if their required language isn’t available.
28. A translator invents a different company identity
The organization’s name includes a common English noun and the target machine draft replaces it with a generic term. This can make policies appear issued by a different institution. Preserve recognized legal names, contract parties and employee identities. Use an approved localized company name if one exists, and keep organization registration or relevant source identifiers traceable.
29. A technical identifier gets translated
An intranet engineering page references application version 4.3.1 and a specific API endpoint. Translation changes path segments or numbers because they resemble English words. Keep machine-readable strings literal, and translate only their descriptions. Test important links and code against the actual application. A user should be able to reproduce the same troubleshooting step from either language.
30. A source warning says not yet
A release note says a security fix is not yet available to all users. A Spanish rewrite omits not and suggests everyone can deploy it immediately. This changes software release status and can create operational risk. Preserve staged availability, negative qualifiers and required prerequisites. Review against the responsible product owner’s actual release record rather than inferred marketing expectations.
31. A customer case is under investigation
A target-language service page says a case was resolved, but the source says an investigation is underway. A user may stop reporting a serious issue. Keep Reported, Investigating, Fix deployed and Resolved distinct. The target reader should know what is complete and what remains pending. Any official status should come from the authorized incident owner, not a translator’s desire for confident prose.
32. An image caption moves beneath another image
A translated SharePoint page includes two product photographs and two captions. Longer German text reflows the web part and associates the wrong description with each product. Check rendered target layout at desktop and narrow screen widths. A linguistically correct caption about a safety feature is misleading if placed beneath the other model. Verify figure IDs and actual items.
33. A call-to-action button promises more than the link
A Spanish translated card says Apply now, but its link goes to an information page with no open applications. Alternatively, the link may offer only an English form. Open the destination and check what a user can really do. The target label cannot create an application or translate the separate resource. Use accurate actions and describe the availability conditions.
34. A dated news story is treated as current
A SharePoint news post written months ago says the office will close tomorrow. The newly translated version appears today and reads as if tomorrow means the day after publication. Keep original announcement date and historic context. If the information is still actionable, ask the owner for a current update. Translation time and event time are separate facts.
35. A source correction doesn’t reach Spanish readers
The English source updates a mandatory training deadline, then translators receive change notifications in a later batch. Spanish staff continue reading the prior date. Microsoft notes the notifications can be batched and page content requires manual updating. Define an escalation process for high-impact changes and avoid describing email notification as immediate synchronization. Publish a visible correction when necessary and verify each language edition’s last approved version.
36. A source page is deleted but target association persists
A site owner deletes a French language copy and assumes no further action is necessary. Microsoft’s support describes cleaning up language association through the default page’s Translation pane and republishing in relevant cases. Check the actual site’s language selector and affected web parts. Avoid dangling links and do not treat deletion of one language edition as permission to remove the approved source.
37. A navigation translation is overwritten
A local translator updates an important Spanish navigation label, but a site configuration later overwrites UI translations after a default-language change. Microsoft’s overwrite option can affect UI labels, not modern page body text. Review whether the preference is appropriate for your governance, and audit labels after source changes. Readers need accurate navigation and source content independently.
38. A multilingual site is used on an unsupported subsite
An organization enables multilingual features on a top-level communication site and expects the same modern page workflow on every legacy subsite. Microsoft documents limits on certain subsites and publishing infrastructure configurations. Identify the actual site type and settings before promising a button. Where unsupported, plan a permitted alternative rather than inventing a workaround that could break intranet navigation.
39. An old SharePoint Server guide causes confusion
A colleague uses instructions for the classic Variations feature from an older on-premises SharePoint Server edition. The current Microsoft 365 modern-page translation workflow uses language copies, manual editing and publication. These are not interchangeable tools. Match the instructions to the actual platform and version, especially if a legacy guide mentions XLIFF packages or machine translation options that do not apply to the modern site.
40. A SharePoint page is bilingual in one body
A site owner places full English and Spanish content together on one page and expects the modern page-language selector to show only the chosen language. Microsoft explicitly advises against putting multiple languages into the same modern page body as the multilingual solution. Create proper language editions, maintain approvals and test what each audience sees. Combining both versions in one page can harm usability and break the intended automated page selection.
41. The translator changes a hyperlink to a different policy
An authorized German page links to a similarly named but older PDF while the English source links to the current signed policy. The target may look complete but direct employees to outdated terms. Compare underlying resource identity, version and access rather than just file title. A multilingual site needs reliable references to the same operative documents, with separately approved target resources if they exist.
A complete multilingual SharePoint workflow
Verify the real site and default source
Check the modern SharePoint site type, default language, approved source page, publishing infrastructure and who owns content. Do not apply legacy Server Variations instructions to a modern Microsoft 365 site.
Enable multilingual controls with authorized permissions
Use the documented Site information and Language settings path. Enable target languages and designate translators, ensuring each person has the necessary actual editing permission.
Create and review translated page copies
Use the source page’s Translation pane to create chosen language editions. Translate full relevant page content and check links, charts, navigation labels, dates and qualifying conditions before submitting approval.
Publish and test reader visibility
Approve and publish source and target as required. Open the language selector and home-page News or Highlighted content as a viewer with the relevant preference. Confirm the actual version and access.
Maintain source-change control
After source updates, record new revision, notify reviewers and update every affected target page. A notification cannot substitute for a verified translated source correction.
Audit linked files and security
Open target library links from the intended audience account and check actual file language and permissions. Preserve private data, numbers, IDs and workplace status codes independently of page wording.
Frequently asked questions
How do I enable multilingual pages in SharePoint?
Open site Settings → Site information → View all site settings → Language settings, enable multilingual translation and add languages. On an approved default page choose Translation to create copies.
Does SharePoint automatically translate page text?
In Microsoft’s standard modern multilingual workflow, no. It creates a language page for manual translation; the editor saves and publishes the content after review.
Can I change the default language of a SharePoint site?
Microsoft says the site’s default language is set when created and cannot normally be changed later. Use supported language editions or an authorized migration plan.
What if a translator can’t edit the new page?
Assigning someone as translator does not automatically give editing rights. Ask the site owner to grant appropriate site access through normal security controls.
Why doesn’t a translation appear in the language dropdown?
Check whether the source was republished, the target approved and published, and page associations are intact. Microsoft’s official guidance describes checking the Translation pane.
Are language pages updated when I edit the English source?
No. A source update can notify translators, but target page content must be reviewed and updated manually.
What is the difference between SharePoint language UI and page translation?
Multilingual UI handles eligible labels such as site navigation, while modern page copies contain the authored content that editors translate and publish.
Does translated news appear automatically in News web parts?
Published language editions can appear in the correct language. If no approved target exists, the experience may fall back to default-language content.
Are document libraries automatically translated?
No. PDFs, Office files, images and other library documents require their own appropriate content translation and permission checks.
How do page approvals affect translations?
When enabled, the original and relevant language editions must follow their approval and publishing workflow before readers can see the target.
Do target language pages inherit all permissions?
Access is governed by the actual SharePoint site and linked resources. Check what intended readers can view and edit, and avoid widening sensitive file permissions.
What is the final quality test?
A reader should find the proper language page and understand the same current policy, actor, amount, deadline and next action as the source-language reader.
Final SharePoint localization checklist
Before calling a target page published, check the default-language source and its revision, the enabled site languages, translator edit rights, source republishing, language-page status, approval and publication, navigation, home and news web parts, exact links, file contents, true guest permissions and any recent policy corrections. A fluent target is useful only if it directs readers to the same authorized facts, status and action as the source.
Official Microsoft documentation: Create Multilingual Sites and Pages · Multilingual SharePoint Features · Overwrite Interface Translations · Classic Variations (Different Workflow).
Related eduKateSG articles: Translate Notion Documents · Translate Google Drive Files · Master Art of Translation.