AumLang – AI Multilingual Translation & SEO
AumLang turns your WordPress site multilingual with one-click AI translation that keeps your page builder layouts intact. It uses the AI client that ships with WordPress 7.0, so on a site that already has a provider connected there is nothing to configure and no key to enter.
Highlights
- Builder-aware translation. Elementor and Gutenberg pages are translated automatically — text only, layout and styles untouched. Custom widgets and repeaters are detected from the builder’s own type system, with zero per-widget configuration.
- One-click, fully automatic. Translate a post, page or product and AumLang handles the title, content, excerpt, categories, tags and more.
- SEO complete. Per-language URLs (/zh/…), hreflang alternates, per-language canonical, and a multilingual XML sitemap.
- Glossary. Pin how key terms are translated (e.g. keep a brand name, force “post” a chosen term) so AI output stays consistent and on-brand.
- Interface string translation. Capture the theme/plugin interface strings your visitors actually see and translate them on demand — and pull official WordPress.org language packs automatically.
- Taxonomy translation. Categories, tags and custom taxonomies get per-language versions, with translated archives and language-filtered term lists.
- Language switcher. Shortcode, template tag, block and widget — drop it anywhere.
- Navigation menus. One menu serves every language; items auto-switch to their translation.
- WooCommerce. Products, product categories, tags, brands and attributes are translated, and the full product data (price, stock, gallery) is carried over so the translation stays a working product.
Either way the AI account is yours, so translation cost is under your control — no per-translation fees, no quotas from us, and no account with us of any kind.
Translation engines
AumLang prefers the AI client that ships with WordPress 7.0, and new installs use it by default. The site owner connects a provider once under Settings > Connectors; this plugin then sends only the text to be translated, holds no API key of its own, and shares that one connection with every other plugin on the site.
A direct connection is also offered, because the connectors WordPress ships cover Anthropic, Google and OpenAI, and a site whose network cannot reach any of those still needs a way to translate. It is entirely opt-in and requires your own key.
External Services
Nothing leaves your site until you pick an engine and start a translation. The plugin has no account with us, sends no telemetry, and makes no request on its own.
Using the WordPress AI Client: the text being translated goes to whichever provider the site owner connected under Settings > Connectors. WordPress owns that connection and its credentials; the terms that apply are those of the provider chosen there.
Using the direct connection: the plugin is a client for the OpenAI-compatible chat API, so it can talk to any service implementing it. It sends the strings being translated together with the source and target language, and nothing else. You supply the endpoint, the model and the key; presets are offered purely to fill the endpoint and model fields for services people commonly use:
- DeepSeek – https://api.deepseek.com – Terms | Privacy
- OpenAI – https://api.openai.com – Terms | Privacy
- OpenRouter – https://openrouter.ai – Terms | Privacy
Choosing a preset changes two text fields; it does not contact anything. Any other compatible endpoint can be entered by hand, in which case its operator’s terms are the ones that apply.
Text that has already been translated is served from your own database and never leaves the site again.
Source code
The released source is on GitHub at https://github.com/aumcreate/aumlang — bug reports and pull requests are welcome there.
External and bundled resources
This plugin bundles flag-icons 7.2.3 by Panayiotis Lipiridis, unmodified, as the flag images in
src/assets/flags/. It is licensed MIT; the licence text ships alongside them in
src/assets/flags/LICENSE.txt.
- Source: https://github.com/lipis/flag-icons
The plugin makes no requests to any external service to render a switcher: the flags are served
from this plugin’s own directory.