---
schema_version: "1"
id: e8088ec82941e7e6e23b9c35163bb87b349e0a84d221d88290814105ae94e325
title: Multilingual Sites
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/experience/264-0-0/community_builder_multilingual_overview.md
canonical_url: https://help.salesforce.com/s/articleView?id=experience.community_builder_multilingual_overview.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 87ed52e90e0acda8f54dd5ab6c8a068fd6abcbe96e7b9b42e1ff3c15937d6e09
description: 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.
products:
  - Experiences
release: "264"
---
# 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

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: Experience Builder sites accessed through Lightning Experience, Salesforce Classic, and mobile devices, and is available in <strong>Essentials</strong>, <strong>Enterprise</strong>, <strong>Performance</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> editions.</td></tr></tbody></table>

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
      <colgroup>
        <col style="width:50%">
        <col style="width:50%">
      </colgroup>
      <thead class="slds-text-title_caps ">
        <tr class="">
          <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="text-align:center;vertical-align:top;" id="d22738e65">User Permissions
            Needed</th>
        </tr>
      </thead>
      <tbody>
        <tr class="">
          <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d22738e65 ">To create an Experience Cloud site:</td>

          <td class="slds-cell-wrap" style="vertical-align:top;" headers="d22738e65 ">Create and Set Up Experiences AND View Setup and Configuration</td>

        </tr>
        <tr class="">
          <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d22738e65 ">To customize or publish an Experience Cloud site:</td>

          <td class="slds-cell-wrap" style="vertical-align:top;" headers="d22738e65 ">
            <ul>
              <li>Create and Set Up Experiences AND View Setup and Configuration AND be a member
                of the site<p>OR</p>
              </li>

              <li>View Setup and Configuration AND be a member of the site AND have appropriate
                <a href="https://help.salesforce.com/s/articleView?id=experience.networks_access_control_overview.htm&amp;language=en_US" target="_blank">role-based site access</a>
              </li>

            </ul>
          </td>

        </tr>
      </tbody>
    </table>

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](https://help.salesforce.com/s/articleView?id=experience.community_builder_multilingual_create.htm&release=264.0.0&type=5)**  
    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](https://help.salesforce.com/s/articleView?id=experience.community_builder_multilingual_default.htm&release=264.0.0&type=5)**  
    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](https://help.salesforce.com/s/articleView?id=experience.community_builder_multilingual_add.htm&release=264.0.0&type=5)**  
    Add the languages that you want your site to support.
- **[Set Language Options](https://help.salesforce.com/s/articleView?id=experience.community_builder_multilingual_settings.htm&release=264.0.0&type=5)**  
    After you add Experience Builder sites languages, you can define separate settings for each language.
- **[Edit Language Content on the Page](https://help.salesforce.com/s/articleView?id=experience.community_builder_multilingual_editing_about.htm&release=264.0.0&type=5)**  
    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](https://help.salesforce.com/s/articleView?id=experience.community_builder_multilingual_export.htm&release=264.0.0&type=5)**  
    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](https://help.salesforce.com/s/articleView?id=experience.community_builder_multilingual_import.htm&release=264.0.0&type=5)**  
    After your translation service has completed the translations, import the translated .xml file into your Experience Builder site.
- **[Delete a Language](https://help.salesforce.com/s/articleView?id=experience.community_builder_multilingual_delete.htm&release=264.0.0&type=5)**  
    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](https://help.salesforce.com/s/articleView?id=experience.community_builder_multilingual_best_practices.htm&release=264.0.0&type=5)**  
    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](https://help.salesforce.com/s/articleView?id=experience.networks_chatter_translate.htm&release=264.0.0&type=5)**  
    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.

#### See Also

- [_Blog post_: Localization within Experience Cloud Sites](https://www.learnexperiencecloud.com/article/Localization-within-Experience-Cloud-Sites)
- [Language Selector](https://help.salesforce.com/s/articleView?id=experience.rss_language_picker.htm&release=264.0.0&type=5 "Add the Language Selector component to multilingual sites so guest users can select their preferred language on public site pages.")