First release.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3709036,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3709036,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3709036,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3709036,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.0"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3709036,"resolution":"1","location":"assets","locale":"","width":1920,"height":962},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3709036,"resolution":"2","location":"assets","locale":"","width":1920,"height":962},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3709036,"resolution":"3","location":"assets","locale":"","width":1920,"height":962}},"screenshots":{"1":"Translations screen: pick content and target languages, with per-language status","2":"Settings: pick an engine, its key and model, and the website description passed to every translation","3":"History: what was sent, what came back, and what each job cost"}},"plugin_section":[],"plugin_tags":[220668,12519,279010,4318,10601],"plugin_category":[],"plugin_contributors":[255069],"plugin_business_model":[],"class_list":["post-373916","plugin","type-plugin","status-publish","hentry","plugin_tags-ai-translation","plugin_tags-automatic-translation","plugin_tags-llm-translation","plugin_tags-machine-translation","plugin_tags-polylang","plugin_contributors-szymon0zawadzki","plugin_committers-szymon0zawadzki"],"banners":{"banner":"https:\/\/ps.w.org\/latw-ai-translation-for-polylang\/assets\/banner-772x250.png?rev=3709036","banner_2x":"https:\/\/ps.w.org\/latw-ai-translation-for-polylang\/assets\/banner-1544x500.png?rev=3709036","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/latw-ai-translation-for-polylang\/assets\/icon-128x128.png?rev=3709036","icon_2x":"https:\/\/ps.w.org\/latw-ai-translation-for-polylang\/assets\/icon-256x256.png?rev=3709036","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/latw-ai-translation-for-polylang\/assets\/screenshot-1.png?rev=3709036","caption":"Translations screen: pick content and target languages, with per-language status"},{"src":"https:\/\/ps.w.org\/latw-ai-translation-for-polylang\/assets\/screenshot-2.png?rev=3709036","caption":"Settings: pick an engine, its key and model, and the website description passed to every translation"},{"src":"https:\/\/ps.w.org\/latw-ai-translation-for-polylang\/assets\/screenshot-3.png?rev=3709036","caption":"History: what was sent, what came back, and what each job cost"}],"raw_content":"\n
LATW AI Translation for Polylang<\/a> adds automatic AI translation to the Polylang workflow you already use.<\/p>\n\n 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.<\/p>\n\n 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.<\/p>\n\n 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.<\/p>\n\n Polylang has no built-in translation-management pipeline to plug into \u2014 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.<\/p>\n\n On sites running Polylang Pro<\/strong>, 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<\/strong>, 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 \u2014 the layout, styling and IDs never leave your site.<\/p>\n\n 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 \u2014 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.<\/p>\n\n The free version is not a trial. It translates unlimited content into every language you have set up in Polylang<\/strong>, permanently.<\/p>\n\n Free<\/strong><\/p>\n\n Pro<\/strong><\/p>\n\n Everything in free, plus:<\/p>\n\n Upgrade to Pro<\/a><\/p>\n\n Two language models and two machine translation engines, 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.<\/p>\n\n Language models<\/strong><\/p>\n\n Machine translation<\/strong><\/p>\n\n Your own endpoint<\/strong> (Pro)<\/em><\/p>\n\n Each engine stores its own API key and model separately, so switching between them, and back again, costs you nothing in reconfiguration.<\/p>\n\n Elementor is supported.<\/strong> Only the text inside known widget fields is extracted and sent to the model, as a flat list of strings. The widget tree itself \u2014 layout, styling, IDs, responsive settings \u2014 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.<\/p>\n\n Other builders are refused rather than mangled.<\/strong> 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 \u2014 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.<\/p>\n\n Both editions work. With Polylang Pro<\/strong> 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<\/strong> it uses its own content walker instead. Elementor always goes through the plugin's own extractor, on both editions.<\/p>\n\n 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.<\/p>\n\n OpenAI API<\/strong><\/p>\n\n Google Gemini API<\/strong><\/p>\n\n Google Cloud Translation API<\/strong><\/p>\n\n MyMemory (Translated S.r.l.)<\/strong><\/p>\n\n Translations arrive in the background. Check History<\/strong> to see what was sent, what came back, and what each job cost.<\/p>\n\n Pro is a separate add-on plugin that runs alongside this one. Install this plugin first, then upload the Pro .zip under Plugins > Add New > Upload Plugin<\/strong> and activate it. Bulk translation, the glossary, the editable prompt, the extra engines, the custom endpoint and MCP appear on the screens you already know \u2014 there is no second settings page and nothing to migrate.<\/p>\n\n The settings screen links straight to the right page for each engine, with step-by-step instructions:<\/p>\n\nYou bring your own API key<\/h4>\n\n
How it plugs into Polylang<\/h4>\n\n
Who it is for<\/h4>\n\n
\n
Features<\/h4>\n\n
\n
Free vs Pro<\/h4>\n\n
\n
\n
Supported content<\/h4>\n\n
\n
Translation engines<\/h4>\n\n
\n
\n
\n
Page builders<\/h4>\n\n
Polylang and Polylang Pro<\/h4>\n\n
Requirements<\/h4>\n\n
\n
Third-Party Services<\/h4>\n\n
\n
\n
\n
\n
Quick start<\/h4>\n\n
\n
Adding Pro<\/h4>\n\n
Where to get an API key<\/h4>\n\n
\n