Languages

Plan a site in several languages: translated titles, paths, content, SEO and workflow.

Languages are on the Pro plan and above. Project managers add them in Project settings → Project information → Languages, or when creating the project.

Each language has its own title, slug, content, SEO, status, assignees and due date, so a translator can be assigned and tracked separately. Paths in other languages start with the language, for example /es/tienda/perros.

Translating a page

Switch the editor's language. If the page has no translation yet, choose Copy from English (or your default language) to start from a copy, or Start blank. Project managers can also start translations from the content overview.

Translate with AI

Choose Translate with AI from English on a page that has no translation yet. The AI translates the whole page: its title and URL slug, every text field (including tables, FAQ answers, card descriptions and form labels), the SEO title, description and keywords, translatable metadata and image alt text. Formatting, links and images stay as they are. It follows the project's AI brief: tone, style rules, glossary and the language's own notes (formal or informal, spelling, terms not to translate).

Pick a quality:

  • Standard: right for most pages.
  • Extra high quality: our most capable model, for your most important pages. It uses twice the credits.

It costs 1 credit per 1,500 words, up to 10 credits a page (twice that for Extra high quality). The translation is saved as a draft, ready for a translator or reviewer to check. Code and internal notes are copied, not translated.

To translate many pages, open Content, switch to the language, select the pages (or use Translate all with AI beside the "pages not translated" count) and choose Translate with AI. It runs in the background and shows each page's progress.

When the original changes

If someone edits the English page after it was translated, the translation shows The English page changed since this was translated, and the content overview marks the page Out of date. Choose:

  • Update translation: only what changed is translated (and charged). The result is an update to review: tick the changes to keep and choose Apply selected. Text changes arrive as tracked changes you can accept or reject as usual. Nothing is replaced until you apply it.
  • Mark as up to date: when the change doesn't need translating.

Re-translate with AI (in the editor's menu) translates the whole page again, also as an update to review.

For example, Jenny's Pet Supplies adds a paragraph about free delivery to the English Dog food page. The German page shows that it is out of date; Update translation translates just that paragraph, and the German editor applies it.

Working with a translation agency (XLIFF)

In Content, switch to the language and open XLIFF:

  • Export: downloads the selected pages (or all of them) as an XLIFF 1.2 or 2.0 file, which translation tools such as Trados, memoQ and Phrase open. Existing translations are included.
  • Import translated file: pages without a translation get one, as a draft. Pages that already have one get an update to review, as above. Passages whose English text changed after the export are left out, so an old translation never replaces newer text.

Everywhere else

  • The sitemap shows translated titles and flags pages that aren't translated. You can add pages in any language; moving and deleting pages is done in the default language.
  • The content overview and calendar filter by language.
  • Share pages have a language switcher.
  • Exports: the page inventory CSV has one row per page and language, and sitemap.xml includes hreflang links.

Removing a language asks you to type its code, because its content is deleted.