Getting Started

#1. Set up Polylang first

This plugin translates into the languages Polylang already knows about, so Polylang has to be
installed and configured before anything here will do much.

1. Install Polylang (the free version is enough) and activate it.
2. Under Languages, add at least two languages — the language your content is written in, and
   the ones you want it translated into.

Polylang Pro works too. The plugin notices which edition is running and adapts: with Pro it reuses
Polylang’s own machinery for pulling strings out of posts, and on the free edition it uses its own.
The screens and the results are the same either way.

#2. Install the plugin

Plugins → Add New, search for LATW AI Translation for Polylang, install and activate it.
You can also download it from its page on WordPress.org:
wordpress.org/plugins/latw-ai-translation-for-polylang.

That is the whole plugin. It is not a trial and it does not expire: every language you have set up
in Polylang can be translated, with no per-language limit.

If you also bought PRO, see Installing the PRO Add-on — it installs alongside this plugin rather
than replacing it.

#3. Choose an engine and enter its API key

Go to AI Translation → Settings → General, pick an Engine and paste its API key. OpenAI is
selected by default; its keys are created at
platform.openai.com/api-keys and start with sk-.

The free plugin also offers Google Gemini, Google Translate, and MyMemory, which needs no account
and no key at all — handy for a first test. PRO adds Anthropic Claude and DeepL. What each one does
well is described in Translation Engine – AI Providers.

You bring your own key, so translations are billed to you by the engine directly, at their published
rates. The plugin never charges per translation and nothing passes through our servers — requests go
from your WordPress server to the engine and back.

You will need billing set up on your provider account before requests succeed.

There is one way to translate that needs no key at all: connecting the site to Claude or ChatGPT and
translating from inside the conversation, where the assistant does the work and nothing is billed per
translation. See Translating from Claude and ChatGPT (MCP). Everything else on this page assumes an
engine key.

#4. Describe your website

Still on Settings → General, the Website Description box is worth two minutes.

Whatever you write there is sent to the model with every translation. A shop selling climbing gear
and a law firm use the same words to mean very different things, and this is what tells the model
which one it is looking at. It is the single cheapest thing you can do to improve translation
quality.

#5. Translate something

Go to AI Translation → Translations, pick a post, tick the target languages and start. See
How to Translate?.

Translations are collected by a background task that runs every minute. Check History to see
what was sent, what came back, and what the job actually cost.

If you would rather translate from Claude or ChatGPT, using the subscription you already pay for
instead of an engine key, set that up under AI Translation → Settings → MCP — see
Translating from Claude and ChatGPT (MCP).

#What to check if nothing happens

Translations are collected by WP-Cron. On hosts where WP-Cron is unreliable, the Dashboard
shows a warning about it, and Settings → Advanced → Manual Check Responses adds a button that
collects finished jobs on demand. If you have WP-CLI, wp latwaitp run does the same from the
command line. See Translation stuck in “Queued” status.