Loading
Feature Degradation | Agentforce Voice Read More
Experience Cloud
Table of Contents
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

          Search all of Salesforce Help
          Multilingual Sites

          Multilingual Sites

          Experience Builder lets you create different language versions of your site to serve separate international audiences. For example, let’s say that you have customers in France and Germany. You can deliver the same site experience to each in the language that’s appropriate for their region.

          Required Editions

          Available in: Experience Builder sites accessed through Lightning Experience, Salesforce Classic, and mobile devices, and is available in Essentials, Enterprise, Performance, Unlimited, and Developer editions.
          User Permissions Needed
          To create an Experience Cloud site: Create and Set Up Experiences AND View Setup and Configuration
          To customize or publish an Experience Cloud site:
          • Create and Set Up Experiences AND View Setup and Configuration AND be a member of the site

            OR

          • View Setup and Configuration AND be a member of the site AND have appropriate role-based site access

          When you create a multilingual site, you don’t have to create a separate site for each language. And there’s also no need to duplicate pages within the site for each language. Instead, Experience Builder lets you add translated content to the properties of each component. Translating content through properties lets you maintain all languages within the site.

          After you choose which languages you want your site to support, an in-built language menu lets you switch between languages when editing component properties. Content editing is quick and easy because you never have to leave the page to change to another language.

          Alternatively, if you use a translation service, you can export site content as an .xml file and send it for translation. After you receive the edited file, simply import it back into your site to populate each page component with the translated content.

          You can also apply your own Google Cloud Translation API key to integrate Google Translate into your feeds. Give your site the ability to instantly translate posts, questions, polls, and their comments, answers, and replies.

          • Create a Multilingual Site
            Creating a multilingual site involves a few main steps. Define the languages that you want your site to support. Add translated content for each language. And enable site visitors to choose their preferred language.
          • Set the Default Language for Your Aura Site
            The default language is the language that’s used in a site before a user has selected another language. By default, the default language is set to English (US).
          • Add Languages to Your Aura Sites
            Add the languages that you want your site to support.
          • Set Language Options
            After you add Experience Builder sites languages, you can define separate settings for each language.
          • Edit Language Content on the Page
            Experience Builder provides its own language menu that you can use to switch between languages as you edit content on each page. Switch languages and provide spot translations, like fixing a typo. You can also use this method for full page translations instead of exporting and importing site content.
          • Export Language Content
            Export and prepare Experience Builder site content as one or multiple .xml files. Prepare the files for translation by creating nodes for specific languages. Then send the file to your translation service.
          • Import Translated Content
            After your translation service has completed the translations, import the translated .xml file into your Experience Builder site.
          • Delete a Language
            When you delete a language, the translated content isn’t deleted—it’s just no longer visible. When you add the language back to the Experience Builder site, you can access the translated content again.
          • Best Practices and Considerations for Multilingual Sites
            Keep these practices and considerations in mind when you’re setting up a multilingual site.
          • Add a Translate Button to Feed Items in Experience Builder Sites
            A translation setting in Experience Builder puts a Translate with Google menu on every feed item. Translations are offered through a Google Cloud Translation API key that you provide.
           
          Loading
          Salesforce Help | Article