| 开发者 | szymon0zawadzki |
|---|---|
| 更新时间 | 2026年11月19日 01:10 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
Yes. This is an add-on for TranslatePress, not a standalone translation plugin. It needs TranslatePress active with at least two languages, and does nothing without it.
Both. Everything works with the free TranslatePress. The only thing that needs a paid TranslatePress add-on is slug translation, which TranslatePress itself offers only with its SEO Pack.
Either, or both. As a TranslatePress engine, a page is translated when a visitor first opens it in another language. It is simple, but the first visitor waits while the model answers. The Pages screen does the same work ahead of time, in the background, and can use OpenAI's Batch API for roughly half the price. Many sites translate their existing pages from the Pages screen and leave the engine on for whatever appears later. A site connected to LATW Cloud translates from the Pages screen only: the engine is paused while it is connected.
TranslatePress learns a page's text when that page is rendered in a translated language. Until then there is nothing for the plugin to translate. Open the page once in any of your translated languages, and it appears on the Pages screen with its string counts. Text that only shows up for some visitors, or only after an interaction, is collected when TranslatePress first sees it.
Not unless you ask it to. A normal translation only fills in strings TranslatePress has no translation for. A string you edited in the TranslatePress editor, and a theme string translated by its own language file, are never sent to the engine and never written over. The one exception is Translate Again, on the Pages screen and as "Translate again" in LATW Cloud. It translates the whole page from scratch in the languages you pick and replaces every translation the page has, including the ones you corrected by hand. The confirmation says so before anything is sent. To add only the missing translations, use Translate on the Pages list instead.
Translate unlimited content into every language configured in TranslatePress, using MyMemory, Google Translate, selected low-cost OpenAI and Gemini models, or LATW Cloud. Use it as TranslatePress's engine, page by page from the Pages screen, string by string, or from the TranslatePress editor. It is not a trial and it does not expire.
It depends on the engine and the volume. You pay the provider directly, at their rates. Language models bill per token, Google Translate bills per character, MyMemory is free within its quota. As a rough guide, on our test site a short blog post cost about $0.0002 and an Elementor home page about $0.0003 per language with GPT-6 Luna. Every completed job records what it actually cost, so the History screen shows real figures for your own content rather than an estimate. Translation done through the TranslatePress engine is counted by TranslatePress's own character counter and daily limit.
No. Content goes from your server to the engine you selected and back. It does not pass through our servers, and we neither see nor store it. The exception is the optional LATW Cloud engine, if you connect it: LATW's servers then read the text from your site, have it translated by the AI model chosen for the site and write the translation back. Source texts are not stored. A translation is kept on LATW's servers only while your site can't be reached to receive it, for up to 7 days (see LATW Cloud above).
If quality on nuanced content matters most, use a language model: OpenAI or Gemini. It follows the translation prompt and your website description, and keeps tone consistent. If you are pushing large volumes of straightforward text and cost is the priority, Google Translate is cheaper and faster, and MyMemory is free within its daily quota.
Yes, at any time. Each engine keeps its own key and model setting, so switching back does not mean re-entering anything.
No. They ignore the translation prompt and the website description. They are machine translation engines rather than language models, so there is nothing to prompt.
This plugin ships one prompt, and the Settings page prints it in full so you can see exactly what is sent. You can still add a website description, which is passed to the model with every translation. Writing a prompt of your own, and a glossary for locking specific terms, come with Pro.
Every language you have configured in TranslatePress. There is no per-language limit in the free version.
These apply to translation from the Pages and String Translation screens. Synchronous waits for the provider and fills in the translation in the same run. Background is OpenAI-only. It finishes without holding a long request open, and is the default where available. Batch is OpenAI-only too. It sends the job to OpenAI's Batch API for roughly half the price and collects it when ready, usually within the hour, though OpenAI only guarantees a 24-hour window. Gemini, Google Translate and MyMemory run synchronously only. Translation through the TranslatePress engine is always synchronous, because the visitor is waiting for the page.
Yes. TranslatePress collects text from the page as it is rendered, so it does not matter which builder produced it: Elementor, Bricks, Divi, Beaver Builder, Oxygen, WPBakery or the block editor.
Only with TranslatePress's SEO Pack add-on, which is what lets TranslatePress translate slugs at all. With SEO Pack active and its automatic slug translation switched on, slugs are translated by this plugin's engine like everything else.
Yes, with Pro. Pro includes an MCP server: connect your site once to Claude or ChatGPT, then ask the assistant to translate your strings. It runs inside the subscription you already have, so there is no API key and no per-token charge, and the result is saved into TranslatePress. The free version does not include MCP.
Yes. The History screen shows every past translation from the Pages and String Translation screens: what was sent, what came back, the status of each job and what it cost. The Logs screen carries the technical detail. Translations made through the TranslatePress engine also appear in TranslatePress's own machine translation log.
Jobs go to your chosen engine and are collected by WP-Cron in the background, so long pages do not time out. Cron health is shown on the dashboard. If your host blocks WP-Cron, enable Manual Check Responses in Settings > Advanced to get a button that collects finished jobs on demand. With LATW Cloud no cron is involved.
They stay. Translations are stored in TranslatePress's own tables and belong to your site. Deleting the plugin removes its own queue table, settings and logs, and never touches TranslatePress's data.
The version you have keeps working, but you stop receiving updates until you renew. The free version continues working regardless, with no licence at all.