Themes & Page Builders

Omnalingo translates the rendered HTML your site sends to the browser, rather than hooking into individual themes or builders. That’s why it’s broadly compatible with almost anything: if WordPress renders it, Omnalingo can translate it — with no theme- or builder-specific setup.

Any theme

Omnalingo works with virtually all themes. It also translates the text built into your theme and plugins — buttons, labels, and messages (gettext strings) — alongside your own content.

Even text that JavaScript inserts dynamically is captured — Omnalingo watches the page for changes and picks those strings up. The one case that needs a nudge is text that only appears after a visitor interaction (opening a menu or popup, switching a tab). Open the page in the Visual Editor and perform that interaction once: Omnalingo records the strings as they appear, and you can translate them right there.

Page builders

Because page builders render their content server-side, that output is in the HTML and gets translated like any other page. The major builders are all compatible with no extra configuration:

• Gutenberg (block editor), including Full Site Editing templates
• Elementor
• Divi
• WPBakery
• Bricks
• Etch
• …and others

Note

Builder features that reveal content only after an interaction — popups, live chat, on-demand templates — are captured once they appear: trigger the interaction once in the Visual Editor, then translate the strings right there.

Tip

If any string isn’t picked up, the quickest fix is always the Visual Editor: click the element and save a translation. Manual edits take priority and are never overwritten.