Creating a multilingual WordPress website should not force you to rebuild the same design over and over again.
But for many agencies, freelancers, and WordPress teams working with Oxygen Builder, translating a website with WPML can become a more complicated workflow than expected. The problem is not just translating texts. The real challenge is preserving the original structure of the page created with Oxygen while the content is displayed correctly in several languages.
Why Oxygen + WPML can be complicated
WPML is one of the most widely used multilingual systems in WordPress. Oxygen Builder, for its part, is a very powerful visual builder used by many agencies and developers to create custom websites.
The difficulty appears when a website built with Oxygen needs to become multilingual.
A page created with Oxygen does not contain only visible text. It contains structured builder data: sections, containers, buttons, links, images, accordions, forms, menus, and templates. If the translation workflow does not understand that structure, problems can appear such as:
- texts that do not appear where they should;
- translated pages that keep old layouts;
- buttons or links that are not detected correctly;
- manual duplication of pages by language;
- fragile workflows where each language becomes difficult to maintain;
- extra work every time the original page changes.
On a small website, this may seem manageable. In an agency that maintains multilingual websites for clients, it becomes a real production problem.
The goal is not simply to “translate texts”. The goal is to translate the website while preserving the layout created with Oxygen.
The right workflow: keep Oxygen, keep WPML, and translate safely
A good workflow for a multilingual Oxygen website should follow three principles.
First, Oxygen should continue to handle the visual structure of the page.
Second, WPML should continue to be the multilingual system that manages languages and translations.
Third, there must be a bridge between the two that detects Oxygen’s translatable content without forcing the user to manually rebuild each page.
That is the role of WPML Oxygen Connector.
Instead of asking an agency to duplicate and rebuild layouts in every language, WPML Oxygen Connector scans Oxygen content, detects translatable texts, connects them with WPML String Translation, and displays the translated version on the frontend while preserving the builder’s original structure.
This lets you keep using Oxygen as the builder and WPML as the multilingual system, while adding a practical workflow between them.
What WPML Oxygen Connector does
WPML Oxygen Connector is designed for real production workflows on multilingual websites.
It helps you to:
- detect Oxygen pages, templates, and reusable content;
- scan Oxygen content to find translatable strings;
- review detected strings from its own dashboard;
- translate directly inside WordPress;
- export translations in JSON;
- import completed translations in a controlled way;
- use AI-assisted translation workflows, for example with ChatGPT;
- regenerate cache after translation changes;
- keep Oxygen layouts intact.
The plugin supports Oxygen Builder 6 and Oxygen 4 Classic, so it can be useful both for modern projects and for existing Oxygen websites that need multilingual support.
It does not replace WPML. It does not replace Oxygen. It acts as a compatibility connector between both systems.
Basic workflow: translating an Oxygen page with WPML
A common workflow would be the following.
1. Create or edit the original page in Oxygen
Start with the page in the source language.
Design the page normally in Oxygen. Add sections, buttons, texts, forms, accordions, or any supported elements you need.
When the original page is ready, save it.
2. Scan the page with WPML Oxygen Connector
Go to the WPML Oxygen Connector panel inside WordPress.
The plugin detects Oxygen content and allows you to scan a specific page. During the scan, it registers Oxygen’s translatable content in WPML String Translation.
This gives you a structured list of texts associated with that specific page.
3. Review the detected strings
After the scan, you can open that page’s string view.
From there, you can review the original text, see what is missing from the translation, and work in an interface focused on Oxygen content, without having to manually search through loose strings across the whole website.
This is especially useful for agencies because it keeps the workflow organized by page.
4. Translate inline or export to JSON
You can translate directly from the plugin dashboard or export the page in JSON format.
The JSON workflow is very useful if you work with translators, external tools, or AI-assisted translation.
For example, you can export the translatable content of an Oxygen page, translate it externally with your preferred tool, review the result, and import it back into WordPress.
This greatly speeds up the process without losing human control before publishing.
5. Import safely
The import must be controlled.
WPML Oxygen Connector is designed to allow safer imports, with checks, backups, and cache regeneration. This helps reduce the risk of overwriting content without review or publishing incomplete translations.
The idea is simple: speed is useful, but control is essential.
6. Review the translated frontend
Once the translations are saved, review the page in the target language.
WPML Oxygen Connector displays the translated content on the frontend while preserving the builder structure.
The goal is for the translated page to keep the same design, composition, and layout as the original page.
Why JSON export/import is so important
One of the most useful parts of the workflow is JSON export and import.
In many agencies, translation is not always done inside WordPress. Sometimes the content must be reviewed by a client, translated by a collaborator, processed with an external tool, or accelerated with AI.
JSON makes this workflow more practical.
Instead of manually copying texts from the WordPress panel, you can export the translatable data from a page, work outside WordPress, and import the result again when it is ready.
This is especially powerful for AI-assisted translation workflows.
For example, an agency can export an Oxygen page, translate the content with ChatGPT or another tool, review the tone and terminology, adjust whatever is needed, and import it back into WordPress.
The important point is that the layout is not being rebuilt. You only work on the translatable content.
Designed for agencies and professional projects
WPML Oxygen Connector is especially useful for agencies and freelancers who maintain websites already created with Oxygen.
It can save more time in situations like these:
- the client already has a website built with Oxygen;
- now it needs to become multilingual;
- the agency wants to keep using WPML;
- rebuilding layouts by language would be too slow;
- the website has templates, buttons, forms, links, or reusable structures;
- the team needs a repeatable workflow to translate pages.
For an agency, the value is not only technical. It is also operational.
A clearer workflow means fewer fragile manual steps, fewer layout errors, and fewer hours spent rebuilding pages language by language.
Important note: independent third-party connector
WPML Oxygen Connector is an independent extension developed by Kademar.
It is not affiliated with, endorsed by, or officially maintained by WPML or Oxygen.
Its goal is to provide a practical compatibility workflow for teams that already use Oxygen and WPML and need a safer way to manage multilingual Oxygen content.
Recommended best practices
Before applying any multilingual workflow on a production website, the recommended approach is to work on staging first.
For better results:
- scan the source page after editing content in Oxygen;
- review detected strings before translating;
- use JSON export/import carefully;
- keep backups before large imports;
- review the translated frontend before delivery;
- regenerate cache when necessary;
- do not assume that every custom element from every addon is automatically supported.
This approach keeps the workflow more professional and safer for client projects.
Conclusion
Translating an Oxygen website with WPML should not mean manually rebuilding the same layout in every language.
WPML Oxygen Connector gives agencies, freelancers, and WordPress teams a practical workflow for multilingual Oxygen projects: scan the page, translate the content, import when needed, and keep the builder structure intact.
Keep Oxygen. Keep WPML. Translate safely.
A website built with Oxygen is usually not a simple page with plain text. It normally includes sections, columns, buttons, links, forms, accordions, templates, menus, reusable blocks, and carefully designed visual structures. Manually rebuilding all of that for each language is slow, fragile, and expensive.
WPML Oxygen Connector was created precisely to solve that workflow.
WPML Oxygen Connector is an independent compatibility connector between Oxygen Builder and WPML. Its goal is to help you translate websites built with Oxygen using WPML without rebuilding layouts and without losing the builder’s original structure.
In this guide we will look at the usual problem, which workflow makes the most sense, and how WPML Oxygen Connector can help you manage multilingual Oxygen websites more safely.
Translate websites created with Oxygen using WPML without rebuilding your layouts.