Translate your CMS content in the format it exports
Webflow, WordPress, Contentful, Sanity or a headless setup of your own. Export the content, describe your brand voice once, and get every page back with its structure and metadata intact.
Translate CMS content
Tell AI Glot how to translate this file…
From export to localized site in 3 steps
The export you already produce is the file AI Glot reads. Nothing is reshaped on the way in or out.
1. Export your content
A CSV or Excel export from a traditional CMS, JSON from a headless one, or XLIFF if your platform speaks it. Slugs, IDs and reference fields come along and stay untouched.
Upload an export →2. Set your voice and your rules
Brand tone, product names that never translate, how formal each market should sound. Written as a sentence and applied to every page in the export.
Write your instructions →3. Import the localized file back
The same format, the same identifiers, the same field structure. Your importer sees the file it expects.
Export result →Only the fields your readers see
Body copy, headings, meta titles and descriptions get translated. Slugs, IDs, reference fields, publication dates and internal names stay exactly as your CMS wrote them.
Built for content teams shipping in several markets
One voice across every page
A single brief plus your glossary is applied to the whole export, so page 200 sounds like page 1.
Metadata translated properly
Meta titles and descriptions are translated as marketing copy with their length in mind, not as leftover fields.
Import-safe by construction
AI Glot works on the file as a structure, so headers, keys and row logic survive the round trip and the import does not fail.
Several markets in one job
Add every target language to the same run and get one file per language, all under identical rules.