Choose your website's source language, publish translated content, and control what visitors see when a translation is missing or out of date.
Understand the language settings
Default website language
The default website language is the source language for your existing pages, new sections, generated defaults, blog posts, and categories. It is separate from the language used by your Piraja CRM interface.
The default language is always enabled and cannot be removed from the website's content languages.
Multilingual website
Turn on Multilingual website when visitors should be able to view published content in more than one language. Select at least two enabled content languages before saving.
If multilingual mode is off, only the default language is available publicly. Translation-specific controls remain inactive until multilingual mode is enabled.
Set up another language
- Open Website → Settings → Website languages.
- Confirm the language your existing content was written in under Default website language.
- Turn on Multilingual website.
- Select every content language you intend to publish.
- Save the settings.
- Use the content-language switcher in the page builder, Posts, or Categories to open the target language.
- Create or propose translations, review them, and publish each language when ready.
Enabling a language does not automatically publish unfinished translations. Visitors only receive content that has passed the relevant publish workflow.
Choose safe translation policies
Public fallback to source content
When fallback is off, sections missing a translation are hidden on non-default language pages. This is the recommended production setting because it avoids mixing languages on one page.
When fallback is on, missing translated sections may display source-language content. Use this temporarily while preparing a new language, then review the full visitor experience before launch.
Machine-assisted translation proposals
When enabled, workspace admins can propose translations from the builder translation overview. Proposals are drafts that require review; they are never published automatically.
Stale translation publish policy
A translation becomes stale when its source content changes after the translation was reviewed.
- Warn allows publishing and reports the stale content.
- Block prevents publishing until stale content has been reviewed.
Use Block where language consistency is mandatory. Use Warn when your team prefers to publish quickly and complete review immediately afterward.
Review and publish
Before launching a language:
- Review the content locale launch checklist in Website settings.
- Check pages, navigation, footer, posts, and categories in the target language.
- Resolve missing and needs-review items.
- Check stale content according to your selected policy.
- Preview public URLs and navigation.
- Publish the translated content.
Changing your CRM interface language does not change the website content language. Use the website content-language switcher when editing translations.
Troubleshooting
A language does not appear on the public site
Confirm that multilingual mode is enabled, the language is selected, and the relevant page or translation is published.
Parts of a page are missing
The section may not have a published translation. Switch to that content language in the builder and review the translation overview. If public fallback is off, untranslated sections are intentionally hidden.
A page contains two languages
Public fallback is probably enabled. Translate the missing sections or turn fallback off.
Publishing is blocked
Review missing translation units first. If the stale translation policy is Block, review stale units before publishing again.