內容簡介
LATW AI Translation for Polylang 外掛為 Polylang 工作流程新增自動化 AI 翻譯功能，讓使用者能夠輕鬆管理多語言內容，並使用自選的翻譯引擎進行翻譯，提升網站的多語言體驗。
【主要功能】
• 自動 AI 翻譯整合 Polylang 工作流程
• 支援多種翻譯引擎，如 OpenAI、Google
• 無需訂閱或額外費用，使用者自帶 API 金鑰
• 兼容 Polylang Pro 的內容匯出與匯入功能
• 專為 Elementor 設計的內容提取器
外掛標籤
開發者團隊
② 後台搜尋「LATW AI Translation for Polylang」→ 直接安裝（推薦）
原文外掛簡介
LATW AI Translation for Polylang adds automatic AI translation to the Polylang workflow you already use.
Polylang keeps doing what it does today: languages, the language switcher, translation groups, string translation, the multilingual structure of your site. This plugin fills those translations in for you, using the AI model or translation engine you pick and your own API key.
You bring your own API key
There is no subscription, no credit pack and no per-word price list here. You connect your own provider key, and every request goes straight from your WordPress server to OpenAI, Google or MyMemory, at their published rates, with nothing added on top by us.
Nothing passes through our servers, and no content is stored outside your site and your chosen provider. You are responsible for your own provider billing and usage limits. The one exception is LATW Cloud, an optional engine you connect yourself: it translates on LATW’s servers instead (see Third-Party Services).
How it plugs into Polylang
Polylang has no built-in translation-management pipeline to plug into — a translation is just another post, linked to the original through Polylang’s own language and translation-group system, with nothing that extracts content or writes it back automatically. So this plugin does that whole job itself.
On sites running Polylang Pro, it reuses Polylang’s own content export and import machinery, so what counts as translatable content always matches what Polylang itself understands. On Polylang free, which ships none of that machinery, the plugin extracts content with its own equivalent, built to match Polylang’s own rules. Either way, Elementor is handled by a dedicated extractor that pulls out only the text inside known widgets — the layout, styling and IDs never leave your site.
Pick your content on the plugin’s own Translations screen, tick the target languages, and start. Jobs are collected in the background by WP-Cron, so a long page never holds a request open or times out. The finished translation lands back in Polylang exactly as if you had created it by hand — an ordinary post, term or string, findable, editable and linked the same way as everything else on your multilingual site. If you later delete this plugin, the translations stay; they belong to your site.
Who it is for
Agencies running client sites on Polylang that want translation cost moved off the invoice and onto a metered API key
Site owners with a few hundred pages, where per-word or subscription pricing stops making sense
Anyone who needs translated content to travel between their own server and their chosen provider, with no intermediary in between
Features
Deep Polylang integration — writes finished translations straight into Polylang’s own language and translation-group model, so a translated post, term or string is no different from one you created by hand
Five engines, your choice — MyMemory, Google Translate, OpenAI, Gemini and LATW Cloud, and in Pro also your own model or any OpenAI-compatible API
LATW Cloud — connect the site to LATW Cloud and translate on external servers: no WP-Cron needed, no translation load on your site, and no API key required
Your own model, or any OpenAI-compatible API — point the plugin at a model you host yourself, or at a gateway such as OpenRouter or Groq, and translate through it (Pro)
Polylang string translation — batch-translate the strings registered with Polylang
Elementor support — only the text inside known widgets is sent to the model, never the layout, styling or IDs
ACF support — translates Advanced Custom Fields content
Taxonomy translation — a dedicated screen for categories, tags and custom taxonomies, with per-term status
SEO metadata — Yoast SEO, Rank Math, SEOPress and All in One SEO titles and descriptions
Website context — describe your site once and every language-model translation is done with that context in mind
Custom field control — translate extra meta keys, or exclude ones you do not want touched
Cost tracking — every completed job records what it actually cost, priced against the engine that produced it
Translation history — review any past translation, inspect what was sent and what came back, track status over time
Custom prompt and glossary — control tone, register and terminology, and lock specific terms to specific translations (Pro)
Processing modes — translate synchronously for immediate results, or send OpenAI jobs to the Batch API for roughly half the price
Automatic translation — automatically start a translation when creating posts of a selected type (Pro)
Translate from a chat with Claude or ChatGPT (MCP) — connect your site once and ask your assistant to translate a post, page or term; it runs inside the subscription you already pay for, with no API key and no per-token cost (Pro)
Re-translate only changes — edit one paragraph, pay for one paragraph instead of the whole page (Pro)
Bulk translation — queue dozens of posts for translation in a single action instead of one at a time (Pro)
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
Taxonomy translation — categories, tags and custom taxonomies
Polylang string translation
Elementor layouts
ACF fields
SEO metadata — Yoast SEO, Rank Math, SEOPress, All in One SEO
Custom field control — translate extra meta keys, or exclude ones you do not want touched
Translation history and per-job cost tracking
Batch processing, at roughly half price (OpenAI only)
Engines: MyMemory, Google Translate, OpenAI GPT-6 Luna and GPT-5.4 Nano, Gemini 3.5 Flash Lite
LATW Cloud
Pro
Everything in free, plus:
Bulk translation — queue many posts in a single action instead of one at a time
Glossary — lock specific terms to specific translations
Editable translation prompt — control tone, register and terminology
Your own model, or any OpenAI-compatible API — point the plugin at a model you host yourself, or at a gateway such as OpenRouter or Groq, and translate through it
Translate from a chat with Claude or ChatGPT (MCP) — connect your site once and ask your assistant to translate a post, page or term; it runs inside the subscription you already pay for, with no API key and no per-token cost
More engines and models — Claude (Opus 5.5, Sonnet 5, Haiku 4.5), DeepL, and the larger OpenAI and Gemini models, for higher quality on difficult content
Premium support
Upgrade to Pro
Supported content
Post titles, content and excerpts
Custom post types Polylang is set to translate
Categories, tags and custom taxonomies
Strings registered with Polylang
Elementor widgets — only the text inside them is sent to the model, never the layout, styling or IDs
ACF fields
Yoast SEO, Rank Math, SEOPress and All in One SEO titles and descriptions
Image alt texts
Any meta key a plugin declares to Polylang as translatable, plus any key you add yourself
Translation engines
Two language models, two machine translation engines and the optional LATW Cloud, plus more models, Claude, DeepL and a custom endpoint with Pro. Language models read your website description, follow the translation prompt and handle nuance. Machine translation engines are faster and cheaper per word but take no instructions, because there is nothing to instruct.
Language models
OpenAI — GPT-6 Luna and GPT-5.4 Nano; the larger models come with Pro
Google Gemini — Gemini 3.5 Flash Lite; more models come with Pro
Machine translation
Google Translate — Neural Machine Translation, billed per character
MyMemory — translation memory with machine translation fallback, free within a daily quota, no API key required
Your own endpoint (Pro)
Any API that speaks OpenAI’s chat format: a model you host yourself, or a gateway such as OpenRouter or Groq. You enter the address, the model name and what it costs.
Each engine stores its own API key and model separately, so switching between them, and back again, costs you nothing in reconfiguration.
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 or on WP-Cron.
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.
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
Service URL: https://api.openai.com/
Privacy Policy: https://openai.com/privacy/
Terms of Use: https://openai.com/terms/
Google Gemini API
Service URL: https://generativelanguage.googleapis.com/
Privacy Policy: https://policies.google.com/privacy
Terms of Use: https://ai.google.dev/gemini-api/terms
Google Cloud Translation API
Service URL: https://translation.googleapis.com/
Privacy Policy: https://policies.google.com/privacy
Terms of Use: https://cloud.google.com/terms
MyMemory (Translated S.r.l.)
Service URL: https://api.mymemory.translated.net/
Privacy Policy and Terms of Use: https://mymemory.translated.net/terms-and-conditions
Usage limits: https://mymemory.translated.net/doc/usagelimits.php
LATW Cloud
Service URL: https://app.latw.ai/
Privacy Policy: https://latw.ai/privacy-policy/
Terms of Use: https://latw.ai/terms-of-service/
