Built-in AI Translation using DeepL
Copy content and pages into another locale and DeepL translates them on the way. Every copy lands as a draft, so someone who reads the language looks it over before it goes live.
Running a site in two languages shouldn't mean doing the work twice
If you run a site in more than one language, you know the routine: copy the page into the other locale, paste every field into a translator, paste the result back, and repeat until lunch. Agility now does the copying and the first translation, and leaves the part that needs a person, reading it over, to a person.
Three steps, and the last one is yours
- Pick your content. Select items or a whole list and choose Copy to Locales, or open a page in the other locale and click Initialize Page. Tick Translate Content.
- DeepL translates it. Text, rich text, page components and the text inside custom fields go to DeepL on your own API key.
- Review and publish. Each locale gets a draft, and nothing goes live until you publish it.
Everything that used to be copy and paste
The locale tools, including the new Other Locales column and filter, are on for every instance, with or without DeepL. Install DeepL and they translate as they copy.
Copy to Locales
Copy one item, a selection or a whole list into one or more locales in a single step.
Save & Localize
Save an item and copy it to your other locales at the same time.
Pages in several locales at once
Initialize a page in every locale you need, with its components, title, menu text and meta description.
The DeepL panel
Translate a few fields in place from the editor's sidebar. Nothing is saved until you save the item.
Custom fields too
The text inside Power Fields Markdown and Block Editor content is translated, while IDs and Friendly URL fields are left alone.
Regional versions
Every language DeepL supports, including Canadian French, Latin American Spanish, Traditional Chinese, and Brazilian and European Portuguese.
Nothing publishes itself
A translated copy is always a draft. You publish it when it's ready, the same as any other change.
Two minutes to set up
An admin installs the DeepL app from Settings, then Apps, and pastes in your DeepL API key.
What to check before you publish
Machine translation is a strong first draft, not the final word, so we'd rather tell you where to look than have you find out later.
- URL slugs in plain text fields get translated. If your model keeps the slug in a plain text field, check it. A Power Fields Friendly URL field is left alone.
- A page keeps its URL path. Its title, menu text and meta description are translated, so set a localized path yourself if you want one.
- Code in body text can come back changed. Check any code samples or JSON pasted into rich text.
Canadian French comes out Canadian. We're Canadian, so we checked.
What you need
- An Agility CMS instance with more than one locale.
- Your own DeepL API key. API Free is fine for trying it, and API Pro is for real content. DeepL bills you directly, and its Translator and Write plans don't include API access.
- An admin with two minutes: Settings, then Apps, then paste in the key. The setup guide shows where to find it.
Frequently asked questions
Questions about translating with DeepL
Want to see it on your own content?
Bring a page you already run in two languages and we'll walk through what DeepL does with it, including the parts you'd still want a person to read.