After 2.5 years of building, testing, and rebuilding, I’m excited to finally announce version 2 of our Polylang AI Automatic Translation plugin. And if you’re an Avada user, you’re going to love this.
Why Avada Translation Has Been Such a Pain
Look, I’m not going to sugarcoat it. Translating Avada sites has always been a nightmare.
Avada stores its page data as shortcodes in your database. Strings like [fusion_builder_container][fusion_builder_row][fusion_builder_column] with dozens of parameters nested inside each other. Traditional translation plugins? They either break your layout completely or just… give up.
We’ve seen it happen. You translate a page, and suddenly your carefully designed Avada layout looks like it went through a blender. Columns shift. Fusion Builder elements lose their styling. Background images disappear.
It’s enough to make you want to manually copy-paste everything.
How We Actually Solved This
Here’s what makes v2 different: we stopped treating the AI like a simple text translator.
Instead, we taught it how Avada actually works. How it stores data. How its shortcodes are structured. What each parameter means.
When you click translate, here’s what happens:
- The AI looks at your Avada page and understands it’s looking at Fusion Builder shortcodes
- It reads through the entire structure – not just the visible text, but the layout logic
- It translates the content while preserving every single Avada parameter, every setting, every design element
- It saves the translated version back in the exact same format Avada expects
We’re using the same LLM technology as ChatGPT and Claude, but with something called “tool calling.” Basically, we gave the AI a set of instructions on how to read Avada’s database structure and how to handle its shortcodes properly.
The Smart Re-Translation Thing
This might be my favorite feature.
Let’s say you translated your Avada homepage last month. Now you’ve updated one section – maybe changed a heading or added a new paragraph in the original language.
Old translation plugins would re-translate the entire page. All your Avada elements, all your text, everything. Even the stuff that didn’t change.
Our AI? It compares the old version with the new version, figures out exactly what changed, and only translates that part. Everything else stays exactly as it was.
It’s like having a translator with a perfect memory who knows exactly what they already translated.
Bulk Translation That Actually Works
We built this plugin with real WordPress sites in mind – sites with 50, 100, 500 pages.
You can select all your pages, posts, or custom post types, hit translate, and walk away. The plugin uses Action Scheduler to work through everything in the background. No timeouts. No crashed processes.
You get a dashboard showing what’s translated, what’s in progress, and what still needs to be done. For Avada sites with lots of Fusion Builder pages, this is huge.
Why This Took 2.5 Years
Honestly? Because we wanted to get it right.
We could have shipped a plugin that just connected to ChatGPT and called it a day. Lots of plugins do that. But they don’t actually understand WordPress. They don’t understand Avada’s shortcode structure, or how Fusion Builder nests elements, or why certain parameters can’t be translated.
We wanted to build something that actually works with WordPress as it is – messy, flexible, with dozens of page builders and themes all storing data differently.
Avada is just one of many page builders we support. But it’s a big one, and we made sure it works flawlessly.
Try It Yourself
If you’re running Avada with Polylang and you’re tired of manual translation or broken layouts, check out the plugin here.
We’ve tested it on Avada sites with hundreds of Fusion Builder pages. Complex layouts, nested elements, custom styling – it handles all of it.
This is the Avada AI translation solution we wished existed when we started. Now it does.