AumLang

Features

• Translates Elementor and Gutenberg pages text-only. Custom widgets and repeaters are identified through the builder’s own type system, and layout and styles are left unchanged.
• Configures per-language URLs, hreflang alternates, per-language canonical URLs and a multilingual XML sitemap.
• Maintains a glossary, so brand names remain untranslated and approved terms are translated consistently on every page.
• Translates visitor-facing interface strings and installs official WordPress.org language packs where available.
• Translates WooCommerce products with price, stock and gallery retained.

Intended use

Sites built with Elementor or Gutenberg that serve more than one language market, including WooCommerce stores.

Requirements

WordPress

6.0+

PHP

7.4+

Version

1.7.2

Common questions

Is an API key required?

On WordPress 7.0, usually not. AumLang uses the AI client included with WordPress by default: the site owner connects a provider once under Settings > Connectors, and all plugins share that connection. A direct connection with a separate API key is available as a fallback for networks that cannot reach those providers.

Who pays for translation?

Translation usage is billed directly by the AI provider connected to the site. AumCreate charges no per-translation fee, sets no quota and requires no AumCreate account.

Does translation change Elementor layouts?

No. AumLang translates the text in each element and leaves the page structure unchanged, rather than translating the page as a single block of content.

Can machine translation be published without review?

For catalogues and interface strings, a review pass is generally sufficient. For key sales pages, such as the homepage and service pages, the output is best treated as a first draft for editing.