To deliver entirely different Pages or Sections based on visitor locale, use targeting by locale. Example use cases include a site nav, banner, or Page that's structurally different for one locale than for another locale. If the structure is the same, consider inline localization instead.
Use whole entry localization when you want to change the structure of a content entry depending on the user's locale.
If you need a content entry to display the same structure but only change the contents of the blocks inside the entry, consider using Inline Localization instead.
To successfully use localization in Builder, make sure you've already done the following:
This example demonstrates using localization for a whole page, but you can localize a Page, Section, or Data Model. To localize the whole entry:
- Duplicate the content entry you want to localize. Alternatively, you can create an altogether new content entry, which might be more appropriate if the structure is radically different.
- Click the targeting icon at the top of the Visual Editor.
- In the Targeting modal, click + Target and select Locale.
- Choose the locale you want to use.
You can target a content entry to multiple locales, so that all specified locales receive the same content.
Note that if you are targeting specific locales, the other locales that you aren't targeting won't get that content entry. For example, if you're only targeting en-US for a particular Section, users with any other locale won't receive that Section.
In this case, make sure you have created a separate content entry for each locale that should access particular content. Unlike inline localization, entry-level localization doesn't have a default content entry that can serve content to users of locales without a specific content entry.
For more information, read How Builder Determines Priority.
The last part of setting up localization is to integrate. For instructions, continue to Integrating Builder Localization with your code.
