What this page shows
This page lists the languages currently active for the application and gives operators controls for changing the primary language, removing an active locale, adding more languages, and maintaining SEO locale aliases.
When to use it
- confirm the currently enabled language set
- change which language is treated as primary
- remove a language that should no longer be available
- open the modal to add new languages from the broader catalog
- add, edit, disable, or remove SEO locale aliases
How to read it
Each row represents one enabled language and shows:
CodeName, including the native language name in parentheses when availablePrimaryswitch- a remove action
The current primary language cannot be removed from the row action. Its primary switch is also disabled because it is already selected.
Set Languages modal
Use Add Languages to open the modal. The modal shows current languages as chips, a primary-language summary, SEO locale aliases, and a picker for languages that are not already active.
The language picker searches by English name or native name. Selecting a language only stages it in the modal; the active set changes only after Save Languages.
If there is no existing primary language, the first selected language becomes the primary language when the operator saves.
SEO Locale Aliases
SEO aliases create crawlable locale paths that load content from an existing source locale. Each alias has:
Public path: the URL locale segment, shown as a path such as/br-ptSource locale: the existing locale whose content should be usedhreflang: the locale value exposed for search enginesEnabled: whether the alias participates
Alias-only changes can be saved even when no new language is selected.
Known caveats
- The active-set page is different from the full language catalog. Operators can enable or remove languages here even though the admin language database contains many more entries.
- Removing a language from the active set does not delete it from the language catalog or translated content history.
- SEO aliases reuse an existing source locale. They do not generate translations.
- Public paths must stay distinct from built-in locale codes and reserved application route names.