Free on WordPress.org
AumLang
AumLang makes a WordPress site multilingual with one-click AI translation that leaves page-builder layouts intact. It translates the text a builder holds — not the structure around it — and sets up the SEO side as well: per-language URLs, hreflang alternates, per-language canonical and a multilingual XML sitemap.
What it does
- Translates Elementor and Gutenberg pages text-only, reading custom widgets and repeaters from the builder’s own type system, so layout and styles are untouched.
- Sets up per-language URLs, hreflang alternates, per-language canonical and a multilingual XML sitemap — the part that decides whether four languages are read as one site or four duplicates.
- Keeps a glossary, so a brand name stays untranslated and a term you have decided on stays the same across every page.
- Translates interface strings the visitor actually sees, and pulls official WordPress.org language packs where they exist.
- Carries WooCommerce products across with their price, stock and gallery intact, so a translated product is still a working product.
Who it is for
Sites that sell to more than one language market and were built in a page builder — which is where most multilingual plugins hurt, because they translate the page into something that no longer looks like the page. If your site is a handful of hand-written templates, you may not need it.
Requirements
- WordPress
- 6.0+
- PHP
- 7.4+
- Version
- 1.0.10
Common questions
- Do I need an API key?
- On WordPress 7.0 usually not. It prefers the AI client that ships with WordPress: the site owner connects a provider once under Settings > Connectors, and every plugin shares that one connection. A direct connection with your own key is offered as a fallback for networks that cannot reach those providers.
- Who pays for the translation?
- You do, directly to whichever AI provider you connected. There is no per-translation fee from us, no quota, and no account with us of any kind.
- Will it break my Elementor layout?
- It translates text and leaves the structure alone. That is the whole design of it — the alternative, translating a page as a blob, is what makes builder sites come out broken.
- Is machine translation good enough to publish?
- For a catalogue and interface strings, usually yes with a read-through. For the pages that sell — the homepage, the service pages — treat the output as a first draft. We write our own four languages by hand for exactly that reason.
Need the part no plugin does?
These are the pieces that were general enough to finish once and hand over. When the requirement stops being a plugin, that is the work we do to order.