Weglot alternatives for WordPress

What Weglot does that AumLang does not

No AI account needed

Weglot translates through its own infrastructure. Nothing has to be connected and no provider account has to exist. AumLang needs an AI connection, either the one WordPress 7.0 already holds or one you configure.

Not WordPress-only

Weglot works in front of sites built on other platforms. AumLang is a WordPress plugin and nothing else.

Professional translators on the same invoice

Weglot sells human translation through the same account, priced per word. AumLang has no equivalent: a machine translation is produced, and editing it is your own work.

A paid plan includes support

AumLang’s support is a wordpress.org forum thread.

If any of those four matter to the site, Weglot is the correct choice and the rest of this page does not apply.

Where the Weglot limits sit

What the two limits mean in practice

The word allowance counts unique words across all languages, and Weglot states on the same page that it is a fixed limit which does not renew. It is not a monthly budget that comes back: once the site has translated that many unique words, translating more means moving up a tier.

Languages are metered separately. The paid tier above the free one still allows one translated language; a third language starts at the tier above that. For a site that wants four or five languages, the language count decides the price long before the word count does.

AumLang meters neither. It has no tiers, so there is nothing to move up to.

What the free tiers actually allow

What happens to a page builder layout

Translating a builder page means replacing text inside a structure the builder owns. The question is whether anything other than the text changes.

AumLang reads Elementor’s own control metadata and extracts only the TEXT, TEXTAREA and WYSIWYG controls, including the text controls inside repeaters. Every other control type — colour, select, slider, URL, media, dimensions — is never read and never written. That holds for custom widgets as well as standard ones, with no per-widget configuration; where Elementor’s control metadata is not loaded, a fixed fallback list is used instead.

Weglot works differently in a way that matters here: it translates the page as served, rather than storing a translated copy of the builder’s own data. Neither approach is better in the abstract; they fail in different places, and which one suits a site depends on how its pages are built.

Where the cost goes

AumLang has no paid tier and takes no account. It does not follow that translation is free: the plugin either uses the AI provider already connected to WordPress 7.0, or a connection you configure yourself. Either way the provider’s bill is yours.

The difference from Weglot is not that nothing is paid for. It is that what is paid for is metered by the provider, by use, rather than by a tier that also decides how many languages the site may have.

When to choose which

Choose Weglot

if the site should be translated without holding an AI account, or runs on something other than WordPress, or needs human translation ordered through the same service.

Choose TranslatePress

if one extra language is enough and you would rather stay inside a plugin with its own visual editor.

Choose AumLang

if the site needs several languages, will keep adding content, and you would rather be billed by an AI provider for what you actually translate than by a tier that caps both words and languages.