Multi-Locale Guide


This guide will walk you through setting up a locale and choosing a locale context methodology.

Add Your Locale(s)

First, you will need to add a new locale (if you have not already done so). You can do this by navigating to Settings > Locales and click on the “New” button.

How to Add a New Locale

If you receive an error message, your license may not support an additional language. If this is the case, please contact

Choose Your Locale Context

Next, you’ll need to decide how to keep track of the locale context. There are generally three options – Locale Code in URL, Separate Domain per Locale, or Cookie Locale.


Locale Code in URL

Having the Locale Code in the URL means that the current locale will always be the first path in the URL such as or


- For .NET Sites, this must be enabled in Settings > Development Framework.

- For Jamstack sites, this will need to be handled manually in your code. See here for an example of Multi-Locale Support with Next.js.


Separate Domain per Language

Having a separate domain per locale means that each locale will be mapped to a specific domain. In this case, you may have URLs that appear like or

Adding your Sitemap:

  1. Go to Settings > Sitemaps > then click on "Add a Sitemap" to add a new Sitemap and domain.Screen_Shot_2021-06-15_at_3.18.56_PM.png
  2. On the Sitemap Details fly out, enter a Name, Reference Name, and select whether this is your default Sitemap.Screen_Shot_2021-06-15_at_3.19.51_PM.png

Adding your Domain:

  1. Click on "Setup Deployment".
  2. Select a Deployment Provider, or proceed with a Custom Deployment.Screen_Shot_2021-06-15_at_3.23.10_PM.png
  3. Enter your Deployment Details. For .NET, ensure you set your Default Language and the Force Default Language checkbox. This will ensure that when a user arrives on that domain that the appropriate language is automatically used.
0 out of 0 found this helpful



Please sign in to leave a comment.