Most translation tools work one string at a time. The engine sees \"Home\", or\n\"Post\", or a lone product name, and guesses. Guess wrong and your menu reads\nlike nonsense to anyone who speaks the language.<\/p>\n\n
This plugin hands the entire rendered page to an AI model instead. The model\ncan see the headline above a button and the paragraph below it before it\ndecides what that button means.<\/p>\n\n
Translations go into the plugin's own table and are served under a language\ndirectory, AI translation is never perfect, so there is a screen for fixing it. Pick a\npage, read the original and the translation side by side, change any line you\ndisagree with. Your edits stay put; the next run will not overwrite them.<\/p>\n\n All three share per-page locks: two editors working at the same time will not\ntranslate the same page twice or double your API bill, while different pages\ntranslate in parallel without queueing behind each other. A lock left behind\nby a crashed job expires by itself once the request timeout passes.<\/p>\n\n Bring your own API key.<\/strong> OpenAI, Claude, Gemini, DeepSeek and OpenRouter all\nwork out of the box, and the model name usually tells the plugin which one you\nmean. You pay that provider for what you translate; the plugin adds nothing on\ntop, and with this option it contacts nobody but the provider you configured.<\/p>\n\n Or subscribe.<\/strong> If you would rather not open an account with an AI provider,\ntop up a balance and pick a model, there is a paid subscription at\nhttps:\/\/translate.aipogeo.com . Connect your site once and translation runs\nthrough Aipogeo: it holds the AI credentials, and the subscription is billed by\ntoken \u2014 the same unit the AI model itself charges in, counting both the text\nsent and the translation returned. This is the one option that sends the text\nbeing translated to a server of ours \u2014 section 3 under External Services says\nexactly what that involves.<\/p>\n\n The bring-your-own-key path stays free and complete. Nothing is held back to\npush you toward the subscription.<\/p>\n\n Be realistic about time. A long page is a lot of text, and the model thinks\nabout all of it \u2014 that is the point, and it is also why there is a progress bar\nand a stop button.<\/p>\n\n This plugin sends text to an AI service in order to translate it. Nothing is\nsent until you have configured one of the options below and asked for a\ntranslation. Which service is contacted depends entirely on that choice.<\/p>\n\n Under Translation Settings \u2192 AI service<\/strong>, choosing \"The settings below only\"\n(or \"Automatic\" with no site-wide provider set up) makes the plugin call the API\nendpoint you enter, using the API key you enter. That is typically OpenAI,\nAnthropic, Google Gemini or DeepSeek, but it can be any relay or self-hosted\ngateway whose address you supply.<\/p>\n\n Choosing \"This site's AI settings only\" hands the request to the AI client built\ninto WordPress 7.0 and later. The provider and credentials are the ones the site\nowner has configured for the whole site; this plugin neither stores nor sees\nthem. The terms and privacy policy are those of whichever provider is set up\nthere.<\/p>\n\n Aipogeo runs a paid subscription at https:\/\/translate.aipogeo.com . It is off\nunless you pick \"Subscription\" and connect an access key. When it is on, the\nplugin stops calling an AI provider directly: it sends each batch to Aipogeo,\nAipogeo calls the AI provider with its own credentials, and the subscription is\nbilled by token.<\/p>\n\n This is the one option where the text being translated leaves your site for a\nserver of ours, so here is what that means in full.<\/p>\n\n If you do not use the subscription, none of the above applies: with your own API\nkey the plugin contacts nobody but the provider you configured.<\/p>\n\n Two front-end libraries ship with the plugin as their official minified builds,\nunmodified. Sources and licenses:<\/p>\n\n The PHP libraries under The bundled php-ai library supports OpenAI, Claude, Gemini, DeepSeek and\nOpenRouter. Pick a model and the plugin works out which one you mean; if you\nare going through a gateway with an unfamiliar model name, choose the protocol\nyourself. If your server cannot reach the provider directly, there is a proxy\nsetting.<\/p><\/dd>\n In their own table, keyed by the source text and the language pair. A string\nthat shows up in your header on every page is stored once, not once per page.\nDeactivating the plugin leaves your content exactly as it was.<\/p><\/dd>\n script and No. Translate the pages that matter, leave the rest, and let visitors or the\nbackground worker pick up the slack over time.<\/p><\/dd>\n\n<\/dl>\n\n\n\/en\/<\/code> or \/ja\/<\/code>. Your posts are never touched. Because the work\nhappens after WordPress has finished rendering, it also covers menus, widgets,\nmeta tags, alt text and placeholders \u2014 not just the post body.<\/p>\n\nThree ways to get pages translated<\/h4>\n\n
\n
What you can set up<\/h4>\n\n
\n
Also taken care of<\/h4>\n\n
\n
What it costs you<\/h4>\n\n
External Services<\/h3>\n\n
1. The AI provider you configure yourself<\/h4>\n\n
\n
2. This site's own AI configuration<\/h4>\n\n
3. The Aipogeo subscription service<\/h4>\n\n
\n
Third-Party Libraries<\/h3>\n\n
\n
vendor\/<\/code> are installed by Composer and ship as plain\nreadable source. See composer.json<\/code> and composer.lock<\/code> for exact versions, and\n assets\/vendor\/CREDITS.md for the full list.<\/p>\n\n\n\n
aipogeo-context-translate<\/code> folder to \/wp-content\/plugins\/<\/code>.\nEverything it needs is in vendor\/<\/code> already. If you are installing from a\nsource checkout instead, run composer install --no-dev<\/code> once in the plugin\nfolder.<\/li>\n\n
Which AI services can I use?<\/h3><\/dt>\n
Where do the translations live?<\/h3><\/dt>\n
Will it translate things that should stay put?<\/h3><\/dt>\n
style<\/code> are skipped, along with WordPress core endpoints and\nstatic assets. Add the not-translate<\/code> class to anything else you want left\nalone, or not-translate-url<\/code> on a link to keep that address as it is.<\/p><\/dd>\nDo I have to translate the whole site at once?<\/h3><\/dt>\n
2.1.1<\/h4>\n\n
\n
2.1.0<\/h4>\n\n
\n
2.0.1<\/h4>\n\n
\n
2.0.0<\/h4>\n\n
\n
1.2.0<\/h4>\n\n
\n
1.1.3<\/h4>\n\n
\n
1.1.2<\/h4>\n\n
\n
1.1.1<\/h4>\n\n
\n
1.1.0<\/h4>\n\n
\n
1.0.0<\/h4>\n\n
\n
0.6.1<\/h4>\n\n
\n
not-translate<\/code> tends to sit flush against the text around it \u2014 and once the\nAI has reordered the sentence, it reads as one run-on word. The padding applies\nto class=\"not-translate\"<\/code>, class=\"notranslate\"<\/code>, translate=\"no\"<\/code> and\n translate=\"0\", and only when the class attribute is exactly that marker, so\nelements of your own that merely carry the marker alongside other classes keep\ntheir layout untouched.<\/li>\n<\/ul>\n\n0.6.0<\/h4>\n\n
\n
0.5.1<\/h4>\n\n
\n
<script type=\"text\/html\"><\/code>\nblock \u2014 video lightboxes, carousels and similar components are usually built\nthis way. PHP's HTML parser treats the first closing tag inside such a block\nas the end of the script, so the rest of the template leaked into the page,\nelements closed in the wrong order and stray closing tags were dropped. The\ncontents of script<\/code> and style<\/code> are now kept out of the parser's way and put\nback untouched, byte for byte.<\/li>\n0.5.0<\/h4>\n\n
\n
0.4.1<\/h4>\n\n
\n
0.4.0<\/h4>\n\n
\n
0.3.1<\/h4>\n\n
\n
?apgt_src=1<\/code>\nappended; the address is now requested exactly as it is, and the marker that\ntells the front end not to substitute translations travels in the\n X-APGT-Source request header instead. apgt_src<\/code> still works if you add it\nby hand to look at an untranslated page.<\/li>\nCache-Control: no-cache<\/code>, so a caching\nplugin cannot hand back a stale copy of the page being translated.<\/li>\n<\/ul>\n\n0.3.0<\/h4>\n\n
\n
apgt_fetch_resolve_ip<\/code> can\noverride the stored value.<\/li>\n<\/ul>\n\n0.2.0<\/h4>\n\n
\n
0.1.0<\/h4>\n\n
\n