No integration required

If WordPress can render it, we can translate it.

  • Every page builder: Elementor, Divi, Bricks, Gutenberg, etc
  • Every theme: Astra, Kadence, GeneratePress, Avada, Enfold, etc
  • Every plugin that puts text on your page
  • Your custom post types and taxonomies too
  • Menus, widgets, forms, popups and sliders
  • Even the strings baked into your theme
wp-admin/omnalingo

Whatever you built it with

Gutenberg, Elementor, Divi, WPBakery, Bricks, Beaver Builder — we never hook into a builder, so there's no integration to install in the first place.

Whatever plugins you run

Buttons, labels, notices and error messages that live inside your plugins and theme get translated alongside the words you wrote yourself.

Even the text that isn't there yet

Open a popup, tab or dropdown once and Omnalingo records those strings as they appear — including content JavaScript builds after the page loads.

We read the finished page

Not each builder's internals — whatever your site sends to the browser is what gets translated. That's why nothing needs configuring.

Updates can't break it

There's no integration to re-sync when your theme, builder or plugins update — and any new text they bring along is picked up on the next scan.

Images, not just words

Swap an image per language when it has text baked in, and give every image its own translated alt text.

Anything you can see, you can fix

If a string ever escapes detection, click it in the Visual Editor and your wording is saved for good.

Nothing gets duplicated

No copy of every page per language. Your original stays the single source, whatever built it.

Custom post types included

Your CPTs and taxonomies sit in the list beside pages and posts — no special handling.