Internationalization

Sites can be multilingual with very little work. Content is translated automatically into many languages, each language gets its own URLs, and visitors are routed to their language — all handled by the platform.

Automatic translation

When you publish, the site's content is translated into its enabled languages. Translation aims to preserve tone and brand voice rather than reading like machine output. You add or remove a site's languages in the app (see Languages).

Manual and mixed

Where you want exact wording, you can provide a hand-authored translation for a language and it takes precedence over the automatic one. You can mix automatic and manual per language, and override individual terms with a glossary so product names and key phrases stay consistent.

A language can also be hand-authored outright — free, unlimited, and never machine-translated — for when you want to write every word yourself. Pages you don't write fall back to the primary language.

Languages are a setting, not a file

The site's language list is the single source of truth for what it serves. A locale folder in the project overrides the translation of a language the site already has; it can never add one. A folder for a language the site doesn't have is rejected at publish, and its name must match the enabled language code exactly.

So the order is always: enable the language first, then write its files. This is also why an AI agent editing your site can't quietly change which languages it serves.

Routing and detection

• Locale-prefixed URLs — each language is served on its own path, so every language is independently indexable for SEO.
• Automatic negotiation — visitors are sent to their preferred language based on their browser and prior choice, with a language switcher to change it.
• Right-to-left languages are handled automatically, including layout direction.

Database content too

Translation isn't limited to page templates — content stored in the database is translated as well, so articles, product descriptions, and listings appear in each language.

Note on single-page apps

Content inside a single-page app area is rendered in the browser, so it falls outside the automatic page translation. Keep marketing and content pages as server-rendered pages to get translation and SEO; use SPA areas for app-like surfaces where that matters less.