Choose where each page is live
Each page chooses which languages and markets it is published in. A product page might launch in English, German, and French first, and add Japanese later. Visitors are sent to their preferred language automatically, and search engines are told about every translated version.
A translations editor for every page
The translations editor lists every piece of text on a page, next to its translation in each language, and highlights what is missing. Translators work page by page, or across the whole site, without hunting through forms. When the source text changes, the new text shows up as missing, so outdated translations never slip through.
Publishing checks can stop a page from going live while translations are missing.
AI translation and your vendors
For speed, Root AI can translate missing strings in one click, and a person reviews the result before it is published. For professional translation, the CMS connects to translation services such as Crowdin and DeepL, and teams can export strings to Google Sheets or CSV and import the results back.
Many teams mix the two: AI for fast first drafts and low-risk copy, and a vendor or in-market reviewer for launches and legal text.
Regional variants without duplicate work
Locales can fall back to one another, so a Swiss German page can reuse the German translation and only override what differs. Teams translate once and publish everywhere it applies.
Frequently asked questions
- How do we know what still needs translating?
- Every page’s translations editor highlights missing strings, and a publishing check can block pages that are incomplete.
- Can we keep our current translation vendor?
- Most likely. Root.js integrates with services such as Crowdin and DeepL, and supports Google Sheets and CSV exchange for everyone else.
- Is AI translation reviewed before it goes live?
- Yes. AI translations are saved like any other edit, and are published only when someone publishes the page.