WPBakery AI Translation with Polylang AI

Robbert Vermeulen

Robbert Vermeulen

· 5 min read

Let’s talk about WPBakery Page Builder (yes, the one formerly known as Visual Composer).

It’s been around forever. Millions of sites still run on it. And if you’re managing WPBakery sites that need multilingual content, you’ve probably been stuck in translation hell for years.

Version 2 of our Polylang AI Automatic Translation plugin changes that. After 2.5 years of development, we’ve built something that actually works with WPBakery’s unique structure.

Why WPBakery AI Translation Has Been Nearly Impossible

WPBakery stores everything as shortcodes in your post content. Deeply nested shortcodes with tons of parameters:

[vc_row][vc_column width="1/2"][vc_column_text]Your content here[/vc_column_text][vc_single_image image="123"][/vc_column][/vc_row]

Except real pages have dozens of rows, multiple columns, galleries, buttons, tabs, accordions – all stacked inside each other like Russian dolls.

Here’s the problem with automatic AI translation: AI models see shortcodes as just… text. They don’t inherently understand that [vc_row] is structure and "Your content here" is what needs translating. Without proper guidance, AI will either translate the shortcode names themselves (breaking everything), skip content buried in nested structures, or translate configuration parameters that should stay in English.

Most translation plugins see this mess and give up. They’ll either:

  • Translate the shortcode names themselves (breaking everything)
  • Skip your WPBakery content entirely
  • Require you to manually map every single field
  • Force you into a workflow where you’re essentially rebuilding pages in other languages

And here’s what makes it even more complicated: real WordPress sites don’t use just one builder. Some pages are WPBakery landing pages, some are standard Gutenberg blog posts, maybe a few static pages with just text. Traditional translation plugins force you to handle each differently – or they only support one type of content.

The AI Approach: Teaching Intelligence, Not Rules

Here’s what makes version 2 different.

We didn’t sit down and write code for every WPBakery element. That’s impossible – there are too many elements, too many third-party add-ons, too many custom configurations.

Instead, we taught AI how to think about WPBakery content.

Using tool calling with ChatGPT, Claude, and Gemini, our plugin gives the AI actual instructions on how to:

  • Navigate WPBakery’s shortcode structure
  • Distinguish between content and configuration
  • Preserve layouts while translating text
  • Handle custom elements it’s never seen before

The AI reads your page, understands what it’s looking at, and figures out the right way to translate it. Even if you’re using custom WPBakery elements or third-party add-ons.

One Plugin for Your Entire Mixed Site

Here’s where it gets really powerful: your WordPress site doesn’t care that some pages are WPBakery, some are Gutenberg, and maybe some are just plain HTML.

Our plugin understands everything.

The same AI that parses WPBakery shortcodes also handles:

  • Gutenberg blocks with their JSON attributes
  • Plain post content in your blog articles
  • ACF fields in your custom post types
  • Any other content structure WordPress throws at it

You don’t need different workflows for different pages. You don’t need to categorize your content before translating. The AI looks at each page, identifies what it’s dealing with, and translates it appropriately.

Scale Without the Headache

Managing one WPBakery site is manageable. Managing five sites, each with 100+ pages mixing WPBakery and Gutenberg, in three languages? That’s where manual translation breaks down.

Our plugin handles volume:

  • Start bulk translation with one click
  • Action Scheduler runs everything in the background
  • Dashboard shows you exactly what’s done and what’s pending
  • Process hundreds of pages without timing out or crashing

You can finally translate that portfolio site, that client’s corporate website, or your own agency site without dedicating your entire week to copy-pasting content.

Update Once, Translate Smart

This feature might be our favorite.

You go back and update a WPBakery page – change a headline, swap an image, add a new section. Most translation tools would retranslate the entire page, potentially messing up translations that were already perfect.

Ours is smarter:

  • Checks the existing translation
  • Compares it against your updated source
  • Identifies exactly what changed
  • Translates only the new or modified content

Everything else stays exactly as it was. Your translations stay consistent, you don’t waste API credits, and updates don’t introduce new translation errors.

Built for WordPress Reality

After 2.5 years of development, here’s what we learned: WordPress sites are messy. They use different themes, different builders, different plugins. Some pages use WPBakery, others use Gutenberg, maybe there’s an Elementor page someone built last year. There’s no “standard” way sites are built.

So we built a plugin that embraces that chaos.

The same AI intelligence that handles WPBakery’s complex shortcodes also works with Elementor’s JSON, Divi’s nested structures, Beaver Builder’s serialized data, and plain Gutenberg blocks. We’re not maintaining separate code for each builder – the AI just figures it out.

This is especially important for agencies managing diverse client sites. You don’t need different translation plugins for different builders. One plugin, universal intelligence.

For Everyone Still Building with WPBakery

Just because WPBakery isn’t the new shiny page builder doesn’t mean your sites deserve worse translation tools.

Version 2 gives WPBakery sites the same modern, AI-powered translation that newer builders get. And when you mix WPBakery with other content types on the same site? No problem. The plugin adapts to whatever it encounters.

Ready to modernize your WPBakery translation workflow? Get Polylang AI Automatic Translation


Whether you’re maintaining legacy sites, managing mixed-builder websites, or still actively building with WPBakery (and plenty of people are), you deserve translation tools that actually work. After 2.5 years, we’ve finally built them.

Questions? Success stories? We’d love to hear how version 2 works on your WPBakery sites.

Robbert Vermeulen

Robbert Vermeulen

Founder EPICWP & 13y+ WordPress dev

View all posts →