The full reference, including right-to-left language support, is in the Translations documentation.
Enable site languages
- Go to
Dashboard → Settings → General → Front-End Languages. - Click the language picker. Search the catalogue of 31 predefined languages (right-to-left languages are badged), or add a custom language with its own code, label, and flag.
- Toggle on the languages you want. English stays on as the default.
Each enabled language gets its own URL prefix automatically: your About page at /about is served in Spanish at /es/about, in French at /fr/about, and so on. Anything you haven't translated yet falls back to the default language, so a partially translated site never shows blank spots.
Right-to-left languages (Arabic, Hebrew, Persian, Urdu) flip the page direction automatically.
Translate blog posts, locations, and other records
Records like blog posts, events, locations, and content items each carry their own translations:
- Open the record's edit page (e.g.
Dashboard → Blog, edit a post). - Find the Translations card. It has one tab per enabled language with inputs for each translatable field — including the SEO title and description.
- Type translations manually, or click Auto Translate to have the configured AI provider fill them in.
Bulk Auto Translate
To translate many records at once:
- On the listing page (e.g. the Blog index), use the Auto Translate button in the toolbar.
- Click the main button to translate every record into every enabled language, or use the dropdown arrow to pick one language.
- A progress window shows the current item and lets you cancel at any time.
Auto Translate only fills in missing translations — anything you've translated by hand is left untouched, and re-running it later only fills the gaps (for example after adding new posts or a new language).
Translate page content
Text built in the page editor — headlines, paragraphs, button labels — is translated from inside the editor:
- Open the page in the editor.
- Use the editor's Translate tool to generate per-language versions of the page's row text.
Menus have their own Translate dropdown on Dashboard → Menus, so your navigation labels follow the visitor's language too — see Menus and Navigation.
What translation covers
| Surface | Where to translate |
|---|---|
| Page editor rows (headlines, buttons, etc.) | Page editor → Translate tool |
| Blog posts, events, locations, content items | Translations card on each edit page, or bulk Auto Translate on the index |
| Forms (labels, options) | Auto Translate on the Forms index |
| Menus | Translate dropdown on Dashboard → Menus |
| SEO fields (meta title, description) | Included in the record's translations — see Improving Your SEO |
Search engines and languages
Every page automatically advertises its language alternates to search engines (hreflang tags), and each language version has its own cacheable URL — there is nothing extra to configure.
Translating the dashboard itself
Separately from the public site, the dashboard's own interface can run in another language:
- Enable admin languages under
Dashboard → Settings → General → Admin Languages. - Use the Auto Translate button there to generate the interface translations.
- Each team member picks their dashboard language from the switcher in the sidebar — it doesn't affect what visitors see.
Tips
- Auto Translate uses your configured AI provider, so an AI key must be set up under Settings before the buttons will work.
- Translate the high-traffic pages first — the fallback behavior means everything else keeps working in the default language meanwhile.
- After adding a new language, run the bulk Auto Translate once per content area (blog, locations, menus, pages) to fill it end to end.