Translating content

Translate single content page

1. Save the source culture, including any draft changes you want Omni to read.
2. Open the document's Translate workspace view or entity action.
3. Choose source (to translate from) and target culture (to translate to) and, when permitted, overwrite behaviour.
4. Preview the report and select the supported properties.
5. Start the job and inspect its property-level results.
6. Review and manually publish the target-culture draft.

Umbraco backoffice

Enlarge ↗

×

Choose the source and target cultures, then preview the supported properties before starting a page translation.

Translate multiple pages

Choose Page and descendants to scan culture-variant content below the selected root page. The aggregate preview lets you refine the pages and properties included before starting a monitored job that tracks translation progress.

Section jobs continue past individual page errors and can be cancelled while active. Configured page and property limits prevent accidental oversized jobs.

Umbraco backoffice

Enlarge ↗

×

Preview and refine the pages and properties included in one monitored section-translation job.

What Omni preserves

• Block layout, order, keys, settings and connected content
• Media references, picker values, URLs and identifiers
• Rich-text elements, links and attributes
• Existing target values unless overwrite is explicitly selected

Review and publishing

Content translations are saved as normal Umbraco language variants in draft state. Omni never publishes translated pages; editors retain the final review and publishing decision.

Umbraco backoffice

Enlarge ↗

×

Review the translated draft in the normal Umbraco editor, then publish when it is ready.

Dictionary items

For reusable interface text and other Dictionary values, follow the dedicated Dictionary translation guide. It covers selecting languages and profiles, bulk jobs, finished-job review and consistent terminology.