How it works
- Pick the site’s languages. In your project’s General settings, open Languages. Choose which languages the site serves and which one is principal: the language you write in. Each page remembers the source it was created with: changing the site’s source later applies to the navbar, footer and pages you create afterwards, while existing pages keep serving the language they were written in at their bare URL.
- Write in your language. The page editorial (badge, headline, description) and the navbar and footer are yours to write exactly as before, in the source language.
- The rest is filled in. After every save, anything missing in the other languages is machine-translated automatically (with the exceptions listed under What gets translated). Saving stays instant in the language you edited; the translations land a few seconds later and the public pages update on their own.
One URL per language
Each language gets its own address, which is what makes translated pages real pages (shareable, cacheable and indexable):/es, /en)
are reserved: a page cannot live at those paths.
Search engines are told about every variant with hreflang alternates in your sitemap,
each variant is its own canonical URL, and a variant whose translation has not landed yet
is served with a fallback and kept out of search indexes until it is complete. The navbar
offers only the language variants that are ready for that page.
Your edits always win
Every translated text remembers where it came from:
To edit a translation, select its language in the content editor and type over it. The
original stays visible as a reference. Update automatic translations fills gaps and
refreshes outdated automatic text; it never overwrites something you wrote.
What gets translated
- The page editorial: badge, headline, highlighted fragment and description.
- The page’s SEO title and meta description: the texts a search engine shows. They follow the same automatic / manual / needs-review rules as the editorial; the page’s social image is shared across languages.
- The navbar and footer: link labels, footer group titles and the legal name. Link destinations are shared across languages; only the text is per-language.
- The agent’s display copy: the title, message placeholder and suggested questions a visitor reads before typing. It belongs to the agent rather than the page, and is translated into the languages the agent itself speaks, so the same brain greets visitors in the right language on every page and every embed that uses it.
- Offers and forms owned by the agent: plan names, feature bullets, button text, field labels, choices, placeholders and the success message. Internal ids, destinations, prices and prompt-facing descriptions are shared and are never translated.
- The body of a document page (privacy, terms): a legal or informational document is yours to word, so the machine never translates it. Add each language yourself when you edit the page; a language you have not written serves the source document whole.
- Your knowledge base: the agent already answers in the visitor’s language, whatever language your documents are in.
- Asset alt text you curated per language, and internal names that visitors never see.
The conversation
The agent has always answered in the language the visitor writes in. With language variants, the conversation starts right too: a visitor on/en/… gets the English page,
English suggested questions, and an agent whose framing matches the page they are reading.