Translate a website and publish language versions
Add languages, review page and CMS translations, and choose which pages are public in each language.
Understand the three language choices
Your dashboard display language controls the app interface. Your site's default language is chosen when the project is created and cannot be changed later in language settings. The site display language in the editor chooses the content version you are currently editing and previewing.
Publishing additional website languages requires Growth. If the project moves to a plan without multilingual publishing, saved translations are retained, but the public site exposes only its default language.
Add a website language
- Open Settings → Language and find Multilingual mode.
- Add the target language. Review the pages and CMS items included in the translation rollout, along with each page's intended visibility in that language.
- Select the content to translate. The rollout also includes the common layout and forms when present.
- Choose whether to skip existing translations or overwrite them when that choice is available. Add instructions for brand names, tone, terminology, or text that should remain unchanged.
- Start the process and keep the tab open until it finishes. Review any reported errors before treating the language as ready.
Saving language settings adds the language configuration. Page translations and language-specific page visibility still need publishing. A language being listed in settings is not proof that every page or CMS item has a complete public translation.
Review and correct translations
Switch the editor's Site display language to the target language. Review the page and shared layout, including navigation, buttons, line wrapping, and images containing text. Use the translation editor for supported page text or Translate with AI to choose a source language, target languages, and translation mode.
Review CMS content in its target language too. You can translate an individual item or use the collection list's translation controls. Check its title, body, slug, images, and references. Translated items must be published when they are ready; translating their page design does not publish their content.
Choose what to make public
Use page language visibility to show or hide a page in each enabled language. These language-specific page changes are drafts until published. A translation and its public visibility are separate decisions: you can prepare a translation before exposing that page.
Additional languages use language-prefixed addresses, such as /ko/about, while the default language normally uses the unprefixed path. Check the exact language URLs after publishing, including the header, footer, forms, and CMS detail pages.
Maintain language versions
When the source changes, review the corresponding translations. Choose “skip existing” to preserve reviewed wording, or “overwrite” when you intentionally want new AI output. Disabling multilingual mode removes additional languages from the public configuration while retaining saved translations. Review the live language options whenever the site's language settings or plan changes.