LATW AI Translation for Polylang – Automatic Translation of Posts, Pages & Strings
LATW AI Translation for Polylang – Automatic Translation of Posts, Pages & Strings

LATW AI Translation for Polylang – Automatic Translation of Posts, Pages & Strings

0/5 (0 ratings) — active installs Updated Nov 13, 2026
The Translations screen lists every post with its status in each language. Tick the languages and click Translate; the job runs in the background.

The Translations screen lists every post with its status in each language. Tick the languages and click Translate; the job runs in the background.

LATW AI Translation for Polylang adds automatic AI translation to the Polylang site you already have. Polylang keeps your languages, URLs, language switcher and translation groups. This plugin fills in the translations.

Pick a post, tick the languages and click Translate. The job runs on your server, in the background, so you can close the tab and move on. The finished translation lands in Polylang as an ordinary post, linked to the original, exactly as if you had written it yourself.

Why LATW for Polylang

  • Translates in the background, not in your browser. Jobs are queued and finished on the server. Close the tab, and long pages still translate without timing out.
  • One screen for your whole site. Posts, pages, custom post types, categories, tags, Polylang strings and SEO titles all have their own translation screens, with the status of every language at a glance.
  • Your engine, your API key. OpenAI, Google Gemini, Google Translate, the free MyMemory, or LATW Cloud with no API key at all. Pro adds Claude, DeepL and your own model. The provider bills you directly, at their price, and we add nothing on top.
  • You see what every translation cost. The History screen records the model, the tokens and the actual cost of each job.
  • Works with Polylang free and Polylang Pro. No need to buy Polylang Pro to get automatic translation.
  • Your translations stay yours. They are ordinary Polylang posts, terms and strings. Delete this plugin, and every translation stays on your site.
  • The free version is not a trial. Unlimited translations into every language set up in Polylang, with no expiry.

Three ways to translate

  • With your own API key (free). Paste an OpenAI, Gemini or Google Translate key, or start with MyMemory, which needs no key. The provider bills you directly.
  • With LATW Cloud (free plugin, pay per word). Click Connect with LATW and AI translates on LATW’s servers. You don’t need an API key, a Pro licence or a working WP-Cron. Your first connected site gets 10,000 free words to try it. LATW Cloud is an optional paid service (see Third-Party Services below).
  • With Pro. Every current model from OpenAI, Anthropic and Google, plus DeepL, bulk translation, automatic translation of new posts, a glossary, and translation straight from your Claude or ChatGPT chat.

How it plugs into Polylang

Polylang has no translation pipeline of its own to plug into: a translation is just another post, linked to the original through Polylang’s translation groups. So this plugin does the whole job itself. It reads the content, sends only the text to your engine, and writes the translation back as a linked Polylang post, term or string.

On Polylang Pro it reuses Polylang’s own export and import machinery, so what counts as translatable always matches what Polylang understands. On Polylang free it uses its own content walker, built to follow the same rules.

Who it is for

  • Site owners on Polylang who want their content translated without copying it into a chatbot page by page
  • Agencies running client sites on Polylang that want translation cost on a metered API key instead of a subscription
  • Elementor sites, where only the text should travel to the model and the layout should stay untouched
  • Anyone who wants their content to travel only between their own server and one named provider

Features

What it translates

  • Post titles, content and excerpts, pages and custom post types Polylang is set to translate
  • Gutenberg blocks, including Spectra blocks, with their attributes preserved
  • Elementor layouts: only the text inside known widgets is sent to the model, never the layout, styling or IDs
  • Categories, tags and custom taxonomies, on a dedicated screen with per-term status
  • Strings registered with Polylang, in batches
  • SEO titles and descriptions from Yoast SEO, Rank Math, SEOPress and All in One SEO
  • Advanced Custom Fields (ACF), image alt texts and any custom field you choose

Engines

  • Language models: OpenAI and Google Gemini (selected low-cost models in free), Anthropic Claude and every current model (Pro)
  • Machine translation: Google Translate, MyMemory (free, no key), DeepL (Pro)
  • Your own model or any OpenAI-compatible API: a model on your own server, OpenRouter, Groq (Pro)
  • LATW Cloud: no API key, pay per word

Workflow

  • Translate a post into several languages in one click, in the background
  • Processing modes: Synchronous, Background and Batch at roughly half the price (OpenAI)
  • Choose the status of new translations, and which parts of a post are translated
  • A manual “Check Responses” button for hosts where WP-Cron does not run
  • Pages built with Bricks, Divi, Beaver Builder, Oxygen or WPBakery are detected and skipped with the reason shown, instead of producing a broken translation
  • Bulk translation: queue dozens of posts in one action (Pro)
  • Automatic translation of new posts of selected types, with daily limits (Pro)
  • Re-translate only what changed: edit one paragraph, pay for one paragraph (Pro)
  • Translate from your Claude or ChatGPT chat: no API key and no per-token cost (Pro)

Control and cost

  • Website description: tell the model once what your site is about, and every translation uses it
  • Custom prompt and glossary to control tone and lock terminology (Pro)
  • Custom field control: translate extra meta keys, or exclude ones you do not want touched
  • The cost of every job is recorded, priced against the engine and model that produced it
  • Translation history: what was sent, what came back, status and errors

Free vs Pro

The free version is not a trial. It translates unlimited content into every language you have set up in Polylang, permanently.

Free

  • Unlimited translations, every Polylang language
  • Posts, pages and custom post types
  • Gutenberg, Spectra and Elementor
  • Taxonomy translation and Polylang string translation
  • ACF fields, custom fields and SEO metadata
  • Translation history and per-job cost tracking
  • All processing modes, including Batch at roughly half price (OpenAI)
  • Engines: MyMemory, Google Translate, selected OpenAI and Gemini models
  • LATW Cloud

Pro

Everything in free, plus:

  • Every current model from OpenAI, Anthropic (Claude) and Google (Gemini)
  • DeepL
  • Your own model, or any OpenAI-compatible API: a model on your own server, OpenRouter, Groq
  • Translate from your Claude or ChatGPT chat, with no API key and no extra token cost
  • Bulk translation
  • Automatic translation of new content
  • Re-translate only changes
  • Editable translation prompt and glossary
  • Premium support

Pro is an add-on: it installs next to this plugin and adds its features to the screens you already know. Get Pro

LATW Cloud

With LATW Cloud, your server doesn’t call an AI provider or wait for WP-Cron to collect the answer. LATW’s servers read the text from your site, translate it and write the translation back, so long pages and large batches no longer depend on your host’s timeouts.

LATW Cloud is a good fit if:

  • you don’t want to create an account with an AI provider or generate your own API key (pay with LATW Credits instead),
  • WP-Cron doesn’t run reliably on your site,
  • your server is small and you don’t want translations to load it,
  • you want to manage translations for several sites from one dashboard.

Connecting. Under AI Translation Settings General, pick LATW Cloud as the engine and click Connect with LATW. A window opens where you sign in to your LATW account and authorize the site. The plugin does the rest and checks that LATW Cloud can reach your site. No Pro licence is needed.

Requirements. The site must be reachable from the internet. If a security plugin, firewall or password protection blocks access, LATW Cloud tells you when you connect or click Test connection.

Your data. LATW Cloud does not store your source texts. They are processed only while a translation is running. Finished translations are written straight back to your site. A translation is stored on LATW’s servers only when your site can’t be reached at that moment. In that case it is kept for up to 7 days until it can be delivered, and then deleted.

Page builders

Elementor is supported. Only the text inside known widget fields is extracted and sent to the model, as a flat list of strings. The widget tree itself — layout, styling, IDs, responsive settings — never leaves your site, and the translation is written back into a copy of the original tree, so nothing the model never saw can be damaged by it.

Spectra blocks are supported. Pages built with Spectra — the block library Astra’s starter templates install — are translated like any other block editor content: headings, paragraphs, buttons, tabs, accordions and their labels.

Other builders are refused rather than mangled. Bricks, Divi, Beaver Builder, Oxygen and WPBakery keep their content in their own storage format instead of the post content. Translating such a post would either produce an empty page or copy the original layout across untouched — both of which look like a broken plugin. Posts built with them are detected and blocked in the interface, with the reason shown, and refused server-side as well.

Polylang and Polylang Pro

Both editions work. With Polylang Pro the plugin delegates string extraction and reassembly to Polylang’s own export machinery, so block parsing stays in step with whatever Polylang supports. On Polylang free it uses its own content walker instead. Elementor always goes through the plugin’s own extractor, on both editions.

Requirements

  • WordPress 6.2 or higher
  • PHP 7.4 or higher
  • Polylang 3.2 or higher, with at least two languages configured — this is an add-on for Polylang, not a standalone translation plugin
  • An API key for the engine you choose. MyMemory needs none, and LATW Cloud needs a LATW account instead.
  • Working WP-Cron, or a real server cron job calling wp-cron.php. If neither is available, the plugin offers a manual “Check Responses” button instead. LATW Cloud needs neither, but your site must be reachable from the internet so LATW Cloud can read and write through the WordPress REST API.

Third-Party Services

Content is sent only to the engine you selected in the plugin settings, and only when you start a translation. Nothing is sent without your action, and every request goes directly from your WordPress server to that provider — except with LATW Cloud, described last, where LATW’s servers do the translating.

OpenAI API

Google Gemini API

Google Cloud Translation API

MyMemory (Translated S.r.l.)

LATW Cloud