A multilingual site uses the same page structure in every language. You translate the words and the CMS content, not the layout.
Last updated
This keeps the design consistent and means a new section only needs to be built once.
Open Settings, then Project settings, then General. Add a language and choose the default.
Each non-default language gets its own address prefix:
example.com/ for the default language.
example.com/es/ for Spanish.
example.com/de/ for German.
The prefix is added automatically. You do not create separate pages for each language.
Open Settings, then Translations. The list shows every page and component.
Choose a language and a page. You see the source text on one side and the translation on the other.
Translation states:
Untranslated means the text still shows the source.
Translated means a translation has been saved.
Needs review means the translation was suggested from a similar source and should be checked.
A suggestion is a starting point, not a finished translation. Review it, then save to confirm.
You can copy the source, reset to the source, or search across messages.
Open an item in the Database area and use the language selector in the item editor. Each language has its own version of the text fields.
An item appears in a language only after its translation is published. Empty fields fall back to the source language.
This means you can publish a post in the default language first and add translations later.
A dropdown field has option labels, such as "Beginner", "Intermediate", and "Advanced". Open the collection's field settings and choose Translate options to provide labels for each language.
The stored value stays the same; only the label changes.
Sign-in errors, form messages, and account messages are translated too. Open Settings, then Translations, then Visitor messages.
These are the messages visitors see on the published site. Leave a field blank to use the built-in default.
Add a Language switcher block to the header or footer. Visitors use it to move between languages.
The switcher keeps visitors on the same page in the other language. If a CMS item has no translation yet, it may not appear in that language's list until the translation is published.
Translations are part of the site design, so publish the site after changing them.
CMS item translations are live when the item translation is published.
The editor interface has its own language setting under your account. That is separate from the website languages.
Workflow messages and email text are not part of the page translation catalog.
Built-in accessibility labels in some widgets stay in English today.
For a bilingual site:
Add the second language in project settings.
Choose the default language.
Translate the navigation and footer first, because they appear everywhere.
Translate the home page.
Translate the remaining pages.
Add a language switcher to the header.
Publish all pages.
Open the site in both languages and check the menu, links, and forms.
Read Project settings for the language list, and Users and login for translated account messages.
A website builder that works like a document. CMS, forms and EU hosting included.
© 2026 Remake. All rights reserved.
