AutoLingo translates your Polylang or WPML site automatically. Publish a post in your language and AutoLingo creates its translations in every other language, with DeepL, Google Translate, Microsoft Translator, OpenAI (ChatGPT) or DeepSeek, on your own API keys, with no markup.

The free version includes

All five providers, with automatic fallback when a quota runs out: about 3,000,000 free characters a month with free DeepL, Google and Microsoft accounts
Translation on publish, a Translate link in the post list and the editor, and the whole site in one click from the admin (or with WP-CLI)
Categories, tags, menus and image alt text, not just posts
Gutenberg, the Classic Editor and shortcode builders (Divi, WPBakery, Flatsome)

AutoLingo Pro adds Elementor, Bricks and Beaver Builder, SEO meta (Yoast, RankMath, SEOPress, The SEO Framework), ACF fields and WooCommerce, plus AutoLingo AI with no API key.

Features (Free)

Translate Gutenberg content (title, blocks, excerpt) on publish or manually
Manual translate button in the post editor and post list
Translate the whole site from Settings AutoLingo Tools: one button creates every missing translation, a few seconds per request so that no host or cache time limit stops it, with no shell access needed (or wp pdat translate-missing, translate-all)
Review before publishing: new translations can be published right away, saved as drafts, or left pending review; updates keep the status a translation has
Repair tools: translations whose address is still the original’s get one from their translated title, and the old address redirects to the new one; duplicates linked to no original are listed and can be moved to the trash, the translation kept getting its clean address back (wp pdat repair, wp pdat duplicates)
Nav menu translation (Polylang and WPML)
Five providers: DeepL (Free and Pro, auto-detected from the :fx key suffix), Google Translate, Microsoft Translator, OpenAI and DeepSeek
Automatic fallback: when the selected provider runs out of quota, the next one that has a key translates — free DeepL, Google and Microsoft accounts add up to about 3,000,000 characters a month
Credit balance check before each translation
Admin alert + dashboard widget when credit runs low
Category and tag translation — term names (and descriptions) are genuinely translated via your chosen provider, not just linked to an existing Polylang/WPML translation
Image alt text translation — when a translated media item exists, its alt text is translated too, not just copied
Image alt and title text inside your content (Gutenberg images, HTML) translated in the same call as the rest
Context-aware: the provider is told what it translates (blog post, page, product, category, menu item) for better short texts
Post meta copy on creation (theme settings, page templates, layout options)
Shortcode-based builders (Divi, WPBakery, Flatsome) — shortcodes preserved verbatim

Features (Pro)

AutoLingo Pro adds:

Page builder support: Elementor, Beaver Builder, Bricks Builder
SEO meta translation: Yoast SEO, RankMath, SEOPress, The SEO Framework
ACF field translation: text, textarea, wysiwyg, link, repeater, flexible content
WooCommerce: custom product attributes, variations and purchase note; without Polylang for WooCommerce or WooCommerce Multilingual, translated products also get prices, variations and linked products, with a shared stock
Theme and plugin strings: Polylang’s Languages Translations or WPML String Translation (site title, widgets, cookie banner, plugin texts)
Lingo, the review agent: rereads each translation next to its original, like a proofreader, fixes what it is sure about and lists the rest
Lingo, the assistant: ask in your own words (“translate my products into Spanish as drafts”), from any admin page; Lingo looks at the site and proposes the actions, which run only when you confirm them

Lingo, the review agent (Pro)

Machine translation is fast, not flawless: a price or an opening time that changes, a sentence left in the original language, a brand name translated word for word. After each translation, Lingo rereads it next to its original, the title, excerpt, content passage by passage, Elementor, Bricks and Beaver Builder texts, and SEO fields, and checks the meaning, numbers and names, passages left untranslated, your glossary, grammar, fluency and the tone you chose.

“List the points to check”: each point shows the passage, a suggestion and why, with Apply and Ignore buttons in the editor; a point you ignore does not come back
“Fix the sure ones, list the others”: the corrections any professional would make are applied for you
Translations created as drafts can be published once Lingo finds nothing to check
The whole site at once from Settings AutoLingo Tools, or wp pdat review
Reviews with AutoLingo AI (no key, on the same monthly credit)

Pages built with Elementor, Bricks or Beaver Builder are reread text by text, and a fix is written back into the builder’s own data (Beaver Builder global modules, shared between pages, are left alone).

Lingo, the assistant (Pro)

Settings AutoLingo Lingo is a chat: say what you want, in your language. Lingo looks at the site (what is missing, a page by its title, the review points) and answers with real numbers, then proposes the actions: translate what is missing, by content type, language and status; translate pages again; repair translations; move duplicates to the trash; have translations reread; translate menus and theme strings; change a setting; add a glossary term.

Nothing changes until you confirm: each proposal is a card with Confirm and Cancel, and the card says what will run, written by AutoLingo from the action itself, not by the AI
Site content is treated as data: text written for an AI in a title or a page is detected, Lingo warns you, and actions that delete or change settings are not proposed after reading it
Every confirmed action goes to the AutoLingo log (who, what, when; the previous value of a changed setting); at most 40 messages an hour per person
With AutoLingo AI, on the same monthly credit as translation (no key); Lingo never uses another AI
One click away on every admin page: a Lingo item in the top bar and a Lingo bubble in the corner open the chat in a panel (the bubble can be turned off); the conversation stays in your browser tab

Page builder support (Pro)

Elementor — _elementor_data (JSON), all common widget types
Beaver Builder — _fl_builder_data (serialized PHP), global nodes skipped
Bricks Builder — _bricks_page_content_2 (JSON), nested items (accordion, tabs)

Shortcode-based builders (Divi, WPBakery, Flatsome) are supported on the free plan — their shortcodes are preserved verbatim during translation.

SEO plugin support (Pro)

Yoast SEO — title, meta description, focus keyword
RankMath — title, description, focus keyword
SEOPress — title, description
The SEO Framework — title, description
SEO template variables (%%title%%, %sep%, %sitename%…) are preserved automatically
Translations whose SEO title or description stayed in the source language (copied by hand, or translated before the SEO module was on) are found and translated in Settings AutoLingo Tools or with wp pdat repair

ACF (Pro)

Translates text, textarea, wysiwyg, and link (title only) fields, including repeater and flexible_content layouts.

WooCommerce (Pro)

Translates custom product attributes (name + pipe-separated values), variation descriptions and the purchase note.

Without Polylang for WooCommerce or WooCommerce Multilingual (which keep translated products in sync themselves), AutoLingo makes each translation sellable like its source: same product type, prices and sale dates, tax, stock and shipping settings, images and downloads; one variation per source variation, with its attributes pointing at the translated ones; upsells, cross-sells and grouped products pointing at their translations. Saving the source updates its translations, and the stock is shared: a sale, a refund or an edit in any language sets the same stock everywhere. The SKU is never copied, as WooCommerce wants it unique. For products translated before, wp pdat sync-products brings the whole catalogue in line without translating the texts again (--dry-run, --ids=, --lang=).

Theme and plugin strings (Pro)

Themes and plugins declare their interface texts for translation: site title and tagline, widgets, footer and header texts, cookie banner, e-mail templates. Settings AutoLingo Tools fills in the missing translations, language by language, or wp pdat translate-strings does it from the command line. Translations already entered are never changed; date and time formats, addresses and placeholders such as %s or {title} are kept as they are.

Polylang — the strings of Languages Translations.
WPML — the strings of WPML String Translation (version 5 or later), each translated from the language it is written in and marked complete. You pick the domains to translate; those of installed plugins and themes, which their own .mo files translate, are left out by default (wp pdat translate-strings --list-domains, --domains=).

Reliability

Exponential back-off retry on HTTP 429 (rate limit): 2 s 4 s 8 s, up to 3 retries
Dual lock (static + transient) prevents duplicate translations on Gutenberg REST saves
Translation log viewer in the admin (DB-backed, 30-day retention)
Integration test suite — 54 tests covering all modules

External Services

This plugin optionally connects to one of four external translation APIs depending on which provider you choose in Settings AutoLingo. No data is ever sent without an explicit translation action and a valid API key that you supply yourself.

DeepL

What it is: DeepL is a machine translation service. This plugin uses the DeepL REST API to translate your post content.

What data is sent: The text content of your posts (title, body, excerpt) is sent to DeepL’s servers for translation. If you use the Glossary feature, your glossary terms (source and target words) are also sent to create a DeepL glossary. No personally identifiable information about your site visitors is transmitted.

When it is sent: Only when a translation is triggered — either manually via the Translate button, automatically on publish (if enabled in settings), via WP-CLI, or when syncing a glossary.

Service endpoint: api.deepl.com (Pro) or api-free.deepl.com (Free plan)

OpenAI

What it is: OpenAI provides the GPT language model API. This plugin uses the gpt-4o-mini model to translate your post content when OpenAI is selected as the provider.

What data is sent: The text content of your posts is sent to OpenAI’s servers. No visitor data is transmitted.

When it is sent: Only when a translation is triggered manually or on publish.

Service endpoint: api.openai.com

DeepSeek

What it is: DeepSeek provides a GPT-compatible language model API. This plugin uses the deepseek-chat model to translate your post content when DeepSeek is selected as the provider.

What data is sent: The text content of your posts is sent to DeepSeek’s servers. No visitor data is transmitted.

When it is sent: Only when a translation is triggered manually or on publish.

Service endpoint: api.deepseek.com

Microsoft Translator

What it is: Microsoft Translator (Azure AI Translator, Text API v3) provides machine translation. This plugin uses it to translate post content when Microsoft Translator is selected as the provider, or when it takes over because the selected provider’s quota is used up.

What data is sent: The text content of your posts is sent to Microsoft’s servers. No visitor data is transmitted.

When it is sent: Only when a translation is triggered manually or on publish, and only if you entered a Microsoft Translator key.

Service endpoint: api.cognitive.microsofttranslator.com

Google Cloud Translation

What it is: Google Cloud Translation API provides machine translation. This plugin uses it to translate post content when Google Translate is selected as the provider.

What data is sent: The text content of your posts is sent to Google’s servers. No visitor data is transmitted.

When it is sent: Only when a translation is triggered manually or on publish.

Service endpoint: translation.googleapis.com

Configuration

Get one or more API keys. Free tiers: DeepL API Free (500,000 characters a month, key ends with :fx), Google Cloud Translation (500,000), Microsoft Translator (2,000,000).
Paste the keys under Settings AutoLingo and pick the provider to use first. When its quota runs out, the next provider with a key translates.
Check the source language (the one you write in) and the target languages.
Choose which content types to translate (default: posts and pages, plus products when WooCommerce is active).

WP-CLI Commands

wp pdat audit — list all source posts with translation status per language
wp pdat audit --format=csv — same output as CSV
wp pdat translate-missing --dry-run — simulate without creating anything
wp pdat translate-missing — translate only missing translations
wp pdat translate-all — translate or update all source posts
wp pdat repair --dry-run — list the translations with SEO fields or an address left in the source language; without `--dry-run`, translate them (the old address redirects)
wp pdat duplicates [--trash] — list the posts of a target language linked to no original that duplicate a translation; `--trash` moves them to the trash
wp pdat review [--ids=] [--lang=] [--all] [--dry-run] — (Premium) Lingo rereads the translations not reviewed yet, or changed since, and lists or fixes what it finds
wp pdat ask "…" — (Premium) asks Lingo, the assistant, in plain words; it answers and lists the actions it proposes, without running them
wp pdat translate-options — translate ACF Options Page fields
wp pdat audit-acf — list all translatable ACF fields

AutoLingo — Automatic Translation for Polylang & WPML

Features (Free)

Features (Pro)

Lingo, the review agent (Pro)

Lingo, the assistant (Pro)

Page builder support (Pro)

SEO plugin support (Pro)

ACF (Pro)

WooCommerce (Pro)

Theme and plugin strings (Pro)

Reliability

External Services

DeepL

OpenAI

DeepSeek

Microsoft Translator

Google Cloud Translation

Configuration

WP-CLI Commands