Skip to content
Documentation

Page Builder Compatibility

Omnalingo translates pages by scanning the HTML that WordPress sends to the browser. Because it works at the output level rather than hooking into individual builders, it is broadly compatible with all major page builders — no builder-specific setup is required.

A Note on JavaScript-Rendered Text

Section titled “A Note on JavaScript-Rendered Text”

One limitation applies across all builders: if a string is injected into the page purely by JavaScript after the initial HTML has loaded (and therefore does not appear in the page source at all), the scanner will not capture it automatically.

This is uncommon but can happen with certain builder widgets that load content asynchronously (live chat, popups loaded on demand, etc.). If you find a string that isn’t being picked up, open the visual editor and click directly on that element to translate it manually.

Gutenberg (Block Editor)

Section titled “Gutenberg (Block Editor)”

✓ Compatible

Block content is rendered server-side and included in the page HTML, so Omnalingo scans it the same way it scans any other page content. Core blocks, third-party blocks, and Full Site Editing templates are all handled correctly.

No additional configuration is needed. Run a scan after publishing or updating content and translations will be picked up on the next scan cycle.

Elementor

Section titled “Elementor”

✓ Compatible

Elementor renders its widget content server-side, and that output is included in the initial HTML response. Omnalingo captures it during scanning without any additional setup.

A few things to be aware of:

  • Elementor popups that load via AJAX after a user interaction may not appear in the initial scan. Use the visual editor to translate those strings directly.
  • Dynamic tags that pull data from custom fields or external sources are translated if their rendered output appears in the HTML. The translation targets the rendered text, not the field source.

Divi

Section titled “Divi”

✓ Compatible

Divi renders page content server-side, and Omnalingo scans it like any other page. Module text, section labels, and button text are all captured normally.

The same note about JavaScript-loaded content applies: Divi’s popup and dynamic content modules that load content after page interaction may require manual translation via the visual editor.

WPBakery

Section titled “WPBakery”

✓ Compatible

WPBakery Page Builder renders shortcodes server-side into HTML before the page is served. Omnalingo scans the rendered output, so all text content built with WPBakery is captured normally.

No special configuration is required. Run a full scan after you finish building your pages.

Bricks Builder

Section titled “Bricks Builder”

✓ Compatible

Bricks renders its elements server-side and Omnalingo captures the output during scanning. Text elements, headings, buttons, and other text-bearing elements are all handled correctly.

As with other builders, elements that load content dynamically after page load (e.g., via AJAX-fetched templates) may require the visual editor for precise targeting.