Introducing Diplo Translator Omni: AI translation for Umbraco
Translate Umbraco pages, rich text and nested blocks into reviewable drafts, then keep languages current with source-change tracking and coverage tools.
Translating an Umbraco website involves much more than translating paragraphs. One page might contain a heading, rich text, a Block Grid, nested cards and a handful of shared Dictionary labels. There are links and media references to preserve, and someone still needs to review the result.
Copying each piece into a translation tool and putting it back in the right place quickly becomes a job of its own. Then the source page changes, and you have to work out which translations need updating.
That’s the problem I wanted to tackle with Diplo Translator Omni: AI translation inside the Umbraco backoffice, with the content model and editorial work kept together. Omni supports Umbraco 17 and 18 on .NET 10, using the matching package version for your site.
From Dictionary labels to page content
My free Diplo Dictionary Translator started with the small, shared phrases that appear throughout a multilingual site. It remains free and open-source, and may be all you need for Dictionary values.
Omni is a separate commercial package for the wider task: translating page content, supported blocks and whole content sections, as well as Dictionary items, with tools to manage that work over time.
A page translation in practice
Imagine an English product page that needs a French version. It has an introduction, formatted body copy with links and an image, and a grid of feature cards.
In Omni, you save the source page, choose the source and target languages, select an approved AI profile and preview the supported properties. You can choose which fields to include before starting the translation.
Omni translates the selected text and saves a target-language draft. You open the variants side by side in the normal Umbraco editor, check the French wording in context, make any refinements and publish when it’s ready. Existing target values are skipped by default, and normal content permissions still apply.
The website’s page translation walkthrough demonstrates this with English and French content across several editor types. For a larger rollout, you can include a page’s descendants, refine the page and property selection, and follow the section translation as a background job.
Keep the structure around the words
Omni finds translatable text inside supported Rich Text, Block List, Block Grid and Single Block values, including nested blocks. It preserves the surrounding structure, block order, keys, links and media references while translating the readable text.
Selected Contentment editors are supported too. Developers can explicitly support custom editors through configuration or an adapter where the stored format is understood. Unsupported values are skipped and reported; the supported editor documentation sets out the details.
What happens when the English page changes?
Suppose you revise one feature card after the French page has been reviewed. Repeating the whole translation could undo useful editorial work.
For tracked translations, Omni identifies changed source text, including text inside supported blocks, and lets you retranslate the affected text. It also flags target values that have been edited independently, so an editor can review those cases.
The management tools help organise the ongoing work:
- Coverage and Missing Variants show where language variants or supported translations need attention.
- Source Changes identifies changed, added or removed source text and independently edited translations.
- Glossary rules provide preferred translations or protect brand and product terms from translation.
- Translation Jobs records who requested a job, its languages and AI profile, progress, results and errors.
Choose the AI provider for your site
Omni uses compatible Umbraco.AI chat providers, with administrators choosing the profiles editors can use. That lets you select models and instructions for your languages, content style and budget.
Translation requests use your site’s provider connection and credentials; translation content isn’t routed through a Diplo service. AI provider usage is billed separately from the Omni licence. The provider and profile guide explains the setup and data handling.
Try it on your own content
Start with the getting-started guide to check requirements, configure your languages and AI provider, and activate a licence.
The free evaluation allows five accepted single-page draft translation runs on one installation, with no time limit. Section and Dictionary translation, overwrite and forced retranslation require a paid licence; provider usage costs remain separate. See the current evaluation and licensing details before starting.
If you’d like to see the workflow first, watch the product tour. The aim is simple: spend less time moving words between tools and more time making the translated website work for its readers.