TranslateRocket -- WordPress 插件

开发者	federicodev
更新时间	2026年10月18日 20:56
捐献地址:	去捐款
PHP版本:	7.4 及以上
WordPress版本:	7.1
版权:	GPLv2 or later
版权网址:	版权信息

https://www.youtube.com/watch?v=WsLpAISB_vo TranslateRocket makes your site multilingual, and everything it does is free. No word limits, no charge per language, and nothing switched off to push you towards an upgrade — it is not a trimmed-down version of a paid plugin. Already using WPML, Polylang, TranslatePress or Weglot? Try TranslateRocket next to it — your site does not change. Activate it alongside your current translation plugin: visitors keep seeing exactly the same site, while you import your translations, complete them and preview any page in any language as an administrator. When you are convinced, deactivate the old plugin and put TranslateRocket online with one click. Nothing of the other plugin is deleted, and switching it back on takes you straight back to where you started. You do not need an API key at all. Chrome and Edge on a computer carry a translator that runs on the device itself, and TranslateRocket can drive it: install the plugin, pick your languages, press one button and the site is translated. It costs nothing, needs no account, and the text never leaves your machine. It is the fastest way to a translated site. When you want fluent, idiomatic copy, the same pages can go through DeepL or an AI model with your own key (OpenAI, Anthropic, Gemini — you pay the provider directly), through ChatGPT or Gemini with a ready-made prompt at no cost, or through your own hands, line by line — and everything already translated is kept, so nothing is ever done twice. Switching from another translation plugin? Your existing translations come with you. One click imports everything you have already paid for or typed by hand — from TranslatePress, Polylang, WPML, Weglot, qTranslate (X and XT), WPGlobus, WP Multilang, Bogo, Multilanguage by BestWebSoft, Falang, Sublanguage, Loco Translate and Autoglot, plus CSV and TMX for anything else. Most are read straight from the tables, the posts or the files, so the import still works after the other plugin has been deactivated or even deleted — which is the usual state of a site that is moving on. Pages built with Elementor or Bricks come across too, widget by widget — their words live in a meta field, not in the page content, and most importers never look there. It detects translatable text as you browse — visible text, link titles, image alt, placeholders, ARIA labels, page titles, meta descriptions and the social preview tags a SEO plugin adds (Open Graph, X) — and serves each language under its own clean URL prefix (/it/, /de/), friendly to SEO and to page caches. You translate however you like:

🆓 In your browser, with no key — Chrome and Edge translate the whole page, or the whole site, on the device itself. Nothing to sign up for, nothing to pay, nothing sent anywhere. Available both on the live page and on the bulk screen.
🖱️ On the live page — switch on the visual editor and click any text to translate it in a small, draggable popup, with Previous/Next, a progress bar and a "skip already-translated" mode.
🆓 Free with Google Translate (no key) — every field has a link that opens Google Translate prefilled, so you translate for free on Google's own site and paste the result back.
✍️ By hand, in a clear per-page editor (also inside the post/page screen) with red highlighting for what's still missing — plus a copy & paste box for bulk Google translation.
💬 With ChatGPT or Gemini, no key — one button copies the whole page with a translation prompt written for your site; paste the answer back and every line goes to its place.
🆓 With free AI, on your own free account — Cloudflare Workers AI (about 1,900 sentences a day with Llama 3.3 70B, or 11,000 with a plain translation model), Groq (gpt-oss-120b) or OpenRouter's free models. A two-minute guide gets you the key, no card needed; a counter shows today's free share, and when it runs out the next provider in your chain carries on.
🤖 With AI — bring your own key for DeepL, OpenAI, Google Gemini, Anthropic (Claude) or Google Cloud Translate. Text is sent only to the provider you choose, only when you ask.

Highlights

🔎 Search in every language, free — a search box that always searches in the language of the page: a visitor on /it/ types in Italian and finds your pages, posts and WooCommerce products by their translated title and text, with suggestions as they type. Make one profile for the header, one for the footer and one for the phone menu, each with its own look and a live preview; add it as a block, with the [translaterocket_search] shortcode or as an item of your menu. The site's own search box, Ajax Search Lite and FiboSearch find translated text too.
🟢 Simple view: translate a site in three steps — choose the languages, press «Translate», put each language online. Nothing to configure and no key: the free engines are already there. Everything else stays one click away under «Advanced», and nothing is ever removed.
🧠 Sentences an engine cannot translate are kept — a brand name, an address or a line already in another language stays as it is and the page still counts as complete, with a «translate again» button if you want to try another engine.
📊 Visits per language, without cookies — how many visits each language gets, its most read pages and the languages your visitors' browsers ask for, so you know which language to translate next.
🍪 Cookie banners in the visitor's language — Complianz, CookieYes, iubenda, Cookiebot and Usercentrics show their banner in the language of the page, and their legal texts are never machine-translated.
💳 Checkout and e-mails in the customer's language — the WooCommerce checkout (Stripe tested), the order e-mails and the e-mails of form plugins (WPForms, Contact Form 7, Fluent Forms, Ninja Forms, Gravity Forms) reach each visitor in the language they used. WooCommerce lists TranslateRocket as compatible with High-Performance Order Storage and with the Cart and Checkout blocks.
🆓 MyMemory, free — one more free engine with no key: about 5,000 characters a day, about 50,000 with just an e-mail address.
🔑 No API key required — and not just "by hand". Chrome and Edge translate the whole site automatically, on your own computer, for free. Or do it by hand in the visual editor, or free with Google Translate, and edit any translation later. There is no signup, no account and no key to create — AI providers are optional and only used if you add one yourself.
🌍 Unlimited languages (36 built in), 100% free. Donations welcome, never required.
⚡ Built for huge sites: past ~20,000 strings the engine switches by itself to indexed per-page lookups — flat memory and the same render time at 500 or 500,000 strings (load-tested), where map-loading translation plugins hit the PHP memory limit.
🖱️ On-page visual editor: click text to translate it in a draggable popup — no admin round-trips.
🧩 Interface too: translates theme & plugin interface strings, not just page content.
🔗 SEO-ready URLs: translated slugs (e.g. /it/chi-siamo/) and hreflang tags.
🔍 One SEO panel with everything in it: open a page in the visual editor and the SEO panel lists, in order, the translated address, the page title, the meta description, the social preview (Open Graph and X), the keywords, then every image on the page and every translatable attribute — titles, placeholders, ARIA labels. Each line takes you straight to that element on the page and opens the right editor, so nothing search engines read is left in the source language by accident.
🚦 Per-page visibility: if a page has no equivalent in a language, redirect it, show a custom message, or 404 — per page, per language.
🎌 Flexible language switcher as a shortcode [translaterocket_switcher], a Gutenberg block, or a widget — inline, dropdown, or a scrollable bar with ‹ › arrows for many languages — with original SVG flags that render everywhere (including Windows). Show a switcher on desktop only, on mobile only, or both, to style a different menu for each.
📥 One-click import from thirteen other plugins — TranslatePress, Polylang, WPML, Weglot, qTranslate (X and XT), WPGlobus, WP Multilang, Bogo, Multilanguage by BestWebSoft, Falang, Sublanguage, Loco Translate and Autoglot — plus a universal importer for any other plugin: it reads your pages as visitors see them, in every language, pairs each sentence with its translation only where the pages match, and lets you preview every page side by side before you switch the old plugin off — plus CSV and TMX for everything else. Read straight from the tables, the posts or the .po files, so it works even when the other plugin is gone. Pages built with Elementor or Bricks come across too, widget by widget.
🖼️ A different image for each language — swap any picture for a translated one: switch on the visual editor, click the button on the image and pick another from your media library. For text baked into a picture, a screenshot of your own interface, or a photo that only makes sense in one country.
🎯 Different content and menus per language — show a paragraph, a block or a menu item only in some languages: with a shortcode, a class on any block, or a checkbox in Appearance → Menus.
🛒 WooCommerce aware: product and category slugs per language, the AJAX mini-cart and JS strings translated too, and customer emails rendered in the language the order was placed in.
👀 Preview mode: review new translations or a fresh import on the real pages while visitors still see the default language — publish with one click when ready.
🚦 Add a language now, publish it when it is ready: each language has a switch — green and your visitors see it, grey and only you do. While it is offline it stays out of the switcher, out of your sitemap and out of the hreflang tags, and its URLs send visitors to your default language, while you keep working on the real pages. Nothing half-translated ever reaches your visitors or Google.
📂 Built for scale: searchable, sortable page list for sites with hundreds of pages.
✅ You stay in charge — every machine translation can be reviewed and edited by hand. Translations live in your own database.

Languages Translate your site into the languages your visitors actually speak: Spanish, French, German, Italian, Portuguese and Brazilian Portuguese, Dutch, Polish, Russian, Ukrainian, Turkish, Romanian, Greek, Arabic, Hindi, Indonesian, Vietnamese, Thai, Chinese, Japanese, Korean — 36 languages ship built in, and you can add unlimited custom ones (any language code works). The plugin's own admin interface is translated into fifteen languages besides English: Arabic, Chinese, Dutch, French, German, Indonesian, Italian, Japanese, Korean, Persian, Polish, Brazilian Portuguese, Russian, Spanish and Turkish. Works with TranslateRocket translates the page your site actually sends to the browser, so it is not tied to a theme or a page builder. Every release is tested on a real site with the plugins below (tested means installed, configured and checked from the visitor's side, not only read about):

Page builders: Elementor and Elementor Pro (theme builder headers and footers included), the block editor. While a builder is editing a page - Elementor, Beaver Builder, Divi, Bricks, Oxygen, Breakdance, Brizy, WPBakery, Thrive Architect, the Customizer - TranslateRocket stays out of its way.
Shops: WooCommerce - product pages, cart, checkout and the order e-mails, in the customer's language.
Forms: Forminator, Contact Form 7, WPForms, Gravity Forms, SureForms, Formidable, Ninja Forms.
Cookie and consent banners: Complianz, CookieYes, GDPR Cookie Compliance, Cookie Notice - the banner text is collected, can be clicked in the visual editor and reaches visitors translated; iubenda, Cookiebot and Usercentrics are told the language of each page.
Payments: WooCommerce checkout with Stripe, in the visitor's language.
Search: WordPress search, Ajax Search Lite, FiboSearch.
SEO: Yoast SEO, Rank Math - translated titles, descriptions and social tags.
Caching and optimisation: Cache Enabler, Autoptimize, WP Fastest Cache.
Side by side with, and importing from: WPML, Polylang, TranslatePress, Weglot, Bogo and others.

The full list, with what was checked and the date of the last test: https://translaterocket.com/compatibility/ Something missing, or not behaving? Tell me from https://translaterocket.com/support/ and I will test it. Need a hand with your site? I can do it for you. I am the developer of TranslateRocket, and I also build and translate WordPress sites for a living: a new multilingual site from scratch, an existing site taken from one language to ten, a migration away from a paid plugin, or a stubborn theme that will not translate. You get the person who wrote the engine, not a support queue. The plugin stays free either way — nothing here is locked behind that. Write to me from the "Help & Feedback" screen inside the plugin, or from https://translaterocket.com/support/ .

1.8.11

Fixed: sentences nobody but the administrator ever sees were counted as «still to translate», and a fully translated site showed 63%: the labels of the editor WordPress loads for a signed-in admin (quicktags, links, media), the descriptions of the REST routes read by the dashboard in the admin's language, and sentences of a page rewritten weeks ago. None of them is collected any more, and when a page is read again whatever was last seen on it more than two days ago leaves its count. Sites that already have such sentences: open the page again as an administrator and they go.
Fixed: addresses, paths, domains, bare tags and language codes («https://…», «/de/», «», «en-GB») were collected as sentences and, as nothing can translate them, kept every language short of 100%. They are left out now, and the ones already collected go with the update (those somebody translated stay).
Faster Translations screen: up to 200 pages the list is drawn at once and the search box, «Only pages still to translate» and the column sort work in the browser, with no request to the server — on a shared host each one used to wait for WordPress to start. Larger sites keep the 50-rows-at-a-time list.

1.8.10

Faster suggestions in the search box: while a visitor types, the answers now come from a light endpoint (suggest.php) that starts only a slice of WordPress — no plugins, no theme — instead of the REST route, which on a shared host took 2–7 seconds, nearly all of it WordPress starting up. Measured on the same site: 0.2 s instead of 3–4 s, with exactly the same results. If a host blocks direct access to plugin files, the box falls back to the REST route by itself. The index keeps the address, title and kind of each page in a small new table, built once in the background after the update; the kind of page («Product», «Page») follows the language of the page.

1.8.9

Fixed: on WordPress Playground (the «Live Preview» on wordpress.org) and on any site that runs on SQLite, a sentence corrected in the visual editor and the translations brought in by the importers were not saved: one database query was MySQL-only. It now works the same on MySQL, MariaDB and SQLite. The Live Preview also opens on a demo page already translated into Italian, Spanish, German and French.
Improved: the search box «in the header menu» now appears in block themes too (the Navigation block of Twenty Twenty-Five and the like), on the computer and inside the phone menu.
Fixed: in the full-screen phone menu of block themes the language names were white on white — only the flags could be seen. There they now take the colours of the theme, like the other links.
Improved: a product never opened in a language is found by its translated title and excerpt (the search index is rebuilt once); while suggestions are on their way a small wheel turns in the search button; «Filters» opens as a button.
Improved: the «Save changes» bar stays at the bottom of the form and floats only when there is something to save, instead of covering the languages; the preview of the icon search styles opens the panel inside the frame, on the phone too.
Fixed: a tag between two words of a title no longer glued them together in the suggestions.

1.8.8

New: Simple and Advanced view. Simple shows only what is free and immediate — choose the languages, press «Translate», put the language online — in three steps at the top of the plugin and three entries in the side menu; everything else is one click away under «Advanced». Nothing was removed.
New: «Search» screen. The search box that searches in the language of the page has its own screen, after Switcher, with profiles (header menu, phone menu, bottom of every page, shortcode or block), four looks (field, rounded field, magnifier that opens a field, magnifier that opens the search over the page), width, placeholder, computer/phone visibility, suggestions while typing, the kinds of content it searches, search in every language, and filters for the visitor (always in sight or behind a «Filters» button), with a live preview at computer and phone width.
New: sentences an engine cannot translate (a name, text not in the site's language) are kept as they were and the page counts as complete, instead of staying at 89% forever. The notice says how many, with a link to see them in Translation memory («Only kept as they were»); «Translate again the kept ones», in a page's «⋯» menu, tries them with another engine.
New: «Recommended: …» under every option where it applies, in all 15 languages of the plugin; quality bars and a gear (to its settings) next to every engine in «Translate with»; the engine's details are a tidy grid.
New: on deactivation, a box offers immediate free help (keep the plugin active and open a ticket), the Simple view, and an optional e-mail to be contacted about that problem only, with consent and deletion after six months.
Improved: the pages list shows «Translate» (with the engine chosen above), «Review» and a «⋯» menu (open the sentences, visual editor, translate again the kept ones, start over, hide) instead of a row of similar buttons; the list and the «Only the pages still to translate» box show that they are loading; «Next steps» leaves the side menu (its drawer stays on every screen in Advanced).
Improved: numbers, dates and euro follow the plugin's language, not WordPress'; the switcher presets light up at once and the preview shows it is redrawing; the menus-per-language explanation says where menus are made, with a link to Appearance → Menus; the texts of the editor blocks (Language switcher, TranslateRocket search) are in the plugin's language.
Compatibility: cookie banners of iubenda, Cookiebot and Usercentrics get the language of each page and their legal texts are never translated (iubenda: one policy per language); Aruba HiSpeed Cache and the host caches are cleared when a translation changes; Slider Revolution 7 slides and WoodMart elements are translated.
Compatibility, from a reading of what fourteen other multilingual plugins fix for their users: WooCommerce now lists TranslateRocket as compatible with high-performance order storage and the block checkout; the mini-cart no longer shows the previous language after a switch; where a form, a booking or a checkout sends the visitor next (AJAX answers) keeps the language; the e-mails of any plugin to the visitor (membership, booking, newsletter) go out in the language of the page, only when sent to the address the visitor typed; CookieYes and every theme or plugin that draws HTML from a template script are collected and translated; Ajax Search Lite and FiboSearch find the pages when the visitor types in their language; /it/page and /it/page/ no longer answer both (301 to the one your permalinks use); Google Site Kit no longer reports a changed home URL; WordPress' own sitemap lists the translated addresses.
Fix: the hourglass stayed on after a translation ended with a message; two switcher presets were both called «Soft» in Italian, German, Spanish and French; the free engines' counters showed English thousands separators.
100+ new sentences translated in the 15 languages of the plugin.

1.8.7

Faster on large sites (tested with 5,000 pages and 75,000 sentences): the counts of every language and of every page are kept until something really changes, instead of being counted again on every screen. The admin screens no longer slow down because of TranslateRocket (the next-steps panel could add 7 to 15 seconds to every page, the WordPress page list included); Translations opens in about 3 seconds instead of 15.
Faster search in the translated languages: the sentences are read once for all the words typed, with exactly the same results and order as before (about three times faster on a large site).
Fix: «Translate all missing with AI» and «Improve with AI» in Translation memory, and «Translate with AI» and the free Google translation in the page editor's TranslateRocket box, translated everything in one request and could end in «504 Gateway Timeout» on large sites. They now work in short steps: the memory offers «Continue translating», the editor box goes on by itself and shows how many sentences it has translated.

1.8.6.1

Fix: on large sites, the «AI» button of a page and «Translate N missing» on AI Translation could end in «504 Gateway Timeout»: they translated everything in one request. They now work in short steps of about 25 seconds, like «Translate all missing», with a progress bar and a «Continue translating» button, so no request reaches the server's time limit. What was already translated is kept.

1.8.6

Fix: a language kept offline while you translate it, and preview mode, sent visitors back to the same address over and over («too many redirects»; a redirect loop for search engines) instead of to the page in your default language. Present since 1.7.11.
New: one «Translate with» menu. The browser translator is in it (the default when you have no key), with every engine marked FREE (green), FREE with a daily limit, or paid — and under the menu, for the chosen engine: quality, limit, what it needs, where it runs and where your text goes. What is left of today's free limit is shown beside each engine.
New: visits per language, without cookies — how many visits each language gets, its most read pages, and the languages your visitors' browsers speak, with a hint when many of them read a language your site does not have yet. Off until you switch it on.
New: content per language — a «Languages» panel on every block and on every Elementor widget, section and container: show it only in some languages, or hide it in some.
New: a different menu per language, for classic and block themes.
New: other plugins doing the same job are detected. When a page cache is already active, TranslateRocket's own cache steps aside and says so; when two plugins optimize JavaScript, a warning says to keep that on in one only. More cache plugins are cleared when a translation changes (Hummingbird, FlyingPress, WP Engine, Kinsta, Varnish).
New: the Translations screen shows 50 pages at a time with «Show more», and searches, filters and sorts on the server — fast with thousands of pages.
Improved: the overview — every row opens its settings, with clearer green checks.
Improved: when DeepL refuses a key that has not used its allowance, the message says so with DeepL's own words and the code its support asks for; DeepL rests for an hour and the next engine carries on.
Fix: importing from TranslatePress skips its rows that are not real translations.

1.8.5

New: search in every language. On a translated page the site's search box finds pages by their translated text (title, excerpt, content, Elementor), never by menus, buttons, footers or cookie banners. The theme's search box, Elementor's search widget and the Search block work as they are. A switch with an info button turns it off.
New: the plugin's screens in six more languages: Turkish, Indonesian, Simplified Chinese, Korean, Arabic and Persian.
New: when a new version of TranslateRocket or Labs is out, a pill beside the version and a notice with «Update now» say it inside the plugin — red when it is a security release.
New: Next steps recommends automatic updates, with one click for TranslateRocket and Labs, and says so honestly when the host has turned them off.
Improved: an AI provider's error is said in plain words with its HTTP code (no credit, wrong model, text too long, safety filter, firewall or proxy page, timeout, DNS, SSL…), the provider's own answer under «Technical details»; «Load available models» and the provider test say the same.
Improved: a provider's daily limit (for example Groq's tokens per day) is said as a daily limit, not «wait a minute», and the notice shows only on TranslateRocket's screens, without the provider's account codes in sight.
Improved: simpler screens — Languages, Translations, Automatic, AI, Switcher, Memory, Next steps in front and the rest under «More»; the translation memory in pages; the list of 80 languages folded until you open it; the «pages changed» notice only on Translations; Labs marked FREE in green.
Fixed: «Scan site» stopped after 1,000 pages and posts: on a site with 5,600 pages the rest stayed at 0/0. It now visits every published page, post and product, a block at a time.
Security: the cache of translated pages no longer stores the page of a visitor who unlocked a password-protected post, has their name saved for comments or has a cart — no password-protected page is cached at all.
Security: the wording collected from WooCommerce emails leaves out the order number, the details under each item (gift card codes, licence keys) and the note written to the customer.
Security: in the editor's translation panel, a user who is not an administrator works only on the sentences of their own page, not on the header, menu and footer shared by the whole site.
Security: a tag left open in a translation is shown as text, never as markup; the site's requests to itself follow WordPress's own SSL setting (https_local_ssl_verify).
Labs 0.9.3: «Translate the whole site» goes on from where it was — pages already translated in every language are skipped, also in a job already running — with Pause and Resume; each page stops after 45 seconds and comes back, instead of being cut by the server's time limit.
Labs 0.9.3 (security): links for external collaborators are kept encrypted in the database, a whole-site link no longer shows private or password-protected pages nor e-mails, the history export is safe to open in a spreadsheet, the support access acts only through TranslateRocket's own code in wp-admin too, and the background reading of a page never follows a redirect to another site.

1.8.4

Security: the translation panel in the post editor works on published content only, and removing a page's translations or running the AI or Google from it is for administrators. A Contributor's draft could reach the home page's translations.
Security: only an administrator can send the visitors of a translated page to another site.
Fixed: «Save» and «Import» in the translation panel of the post editor saved nothing.
Labs 0.9.2 (security): the support access is limited to TranslateRocket's own tools on the site too, and the Labs page and the domains per language stay the owner's.

1.8.3

New: on Translations, small labels under each page say who translated it in this language and how many sentences each — an AI provider, a free Labs engine, this browser, the visual editor, by hand, an import or reuse. A page translated in several ways shows several labels.
New: choosing MyMemory under «Translate with» shows a box for the e-mail address that raises its free limit from about 5,000 to about 50,000 characters a day, with a button to use the site's address and a Save button that keeps it at once.
Fixed: «Plugin language» now also applies to the Labs texts shown in TranslateRocket's pages, such as the conditions of the Labs engines.
Fixed: the «Translate with» row stays in one line, the notes under it and the «Translate with your browser» box take the full width.

1.8.2

Fixed: a network problem, a gateway timeout (502, 504, 524), a firewall or a provider not available in your server's region no longer reads «The provider refused this API key». The HTTP code now decides the message, and is shown with it; the provider's own answer is under «Technical details».
Improved: «Translate all missing» runs in short steps of about 25 seconds with a progress bar, saving and continuing by itself. No single request comes near the 100-second limit of Cloudflare and of many hosts.
New: «Sentences per request» in AI Translation → Usage & limits (Automatic, 5, 10, 20, 50): fewer for a slow or distant provider, more on a quick connection.
Improved: requests that meet Cloudflare's 520, 522 and 524 errors are tried again, like 502, 503 and 504.

1.8.1

New: «Translate with» on the Translations screen: choose the engine — your priority order, one AI provider, a free engine from Labs, or this browser. The menu says which engines are official APIs and which are unofficial endpoints, and warns when a Labs engine is chosen. Engines that are not ready stay visible with what they still need; the choice is remembered and also used by the «AI» button of each page.
Improved: the language switcher is one switcher in one place. «Where to show the switcher» now offers Header and Footer: one profile for the header menu, another for the row at the bottom of every page, each with its own look. Sites that had both in the same profile keep them: the bottom row moves to a new «footer» profile with the same look.
Improved: «Your site, live» on a phone opens the theme's ☰ menu to show the languages, without scroll bars; a footer profile shows the bottom of the page.
Fixed: a page counted its images and the sentences deleted since, and stayed below 100% with nothing left to translate.
Fixed: the «AI» button of a single page no longer sends image addresses to the engine (a translated address made the image disappear).
New: a small ⓘ on every line of «Everything you can do — all free», with more detail on each feature, in TranslateRocket and in Labs.
Improved: the hourglass of a language shows only while its number of translated sentences is really going up; if the live numbers cannot be refreshed, it goes off instead of standing still.
Improved: the «AI» button of each page is there also without an AI key, when another engine of the menu works.

1.8.0

New: «Automatic translation», one page to switch it on and watch it work. A bar for each language moves by itself while the page is open, an hourglass marks the language being translated right now, the engines are one list in the order really used, and a language can go online by itself once it is fully translated (it waits until the whole site has been read).
New: «Everything you can do — all free» at the top of the plugin: what TranslateRocket does on your site, with its state and the page where it is set, and what the free add-on Labs adds.
New: «Test this text» in every AI provider: a short sentence of your choice, translated with the saved key (it costs almost nothing). A green «Tested» tick stays until the key or the model changes.
New: free setup on request — ask from inside the plugin and we configure TranslateRocket on your site.
Improved: the bar and percentage of each language open its translations; the Translations page shows a small progress bar under every flag; «Published, or still being translated?» and «Progress» are now one table.
Improved: the language in a block-theme header menu is one button, as in the preview — the arrow inside, no underline.
Improved: Cloudflare Workers AI finds the Account ID from the token, and says so plainly when the one typed is wrong; a free provider that used up today's requests says so, instead of «add the API key».
Improved: the loading indicator of the switcher's live previews, header and bottom of the page, with words; a note explains when the live preview is not shown, and where the row at the bottom of every page is set.
Improved: when the browser cannot translate a page, the help suggests a free Groq key (the free Gemini plan may not be offered to users in the EU and UK).
Improved: the question on deactivation offers one-click answers, an optional e-mail for a reply, and says that support is fast and free.
Fixed: a language with nothing collected yet showed «100%».
For developers: the filters trrocket_language_base and trrocket_language_from_host let an add-on give a language a domain of its own; trrocket_auto_engines, trrocket_auto_status and trrocket_auto_save connect it to «Automatic translation».

1.7.12

Fixed: a redirect set with Redirection (or by any plugin that uses WordPress' redirect) sent a visitor on /it/old-page/ to the new page in the source language. The language of the address the visitor started from is kept.
Fixed: in lists on a translated page, the titles of password-protected and private posts («Protected: …», «Private: …») stayed in the source language: WordPress localizes that prefix on every page. The prefix is now set aside and the title translated.
Tested with 25 more plugins (Essential Addons, Jetpack, Dokan, Ajax Load More, WPCode, Advanced Ads, SEOPress, The SEO Framework, CoBlocks, Essential Blocks, Genesis Blocks, Shortcodes Ultimate, Strong Testimonials, Easy Table of Contents, AddToAny, Everest Forms, Asgaros Forum, Restrict Content, WP Recipe Maker, Booking Calendar, Woo Variation Swatches, WP Show Posts, WP-PostRatings, Simple Lightbox, Instagram Feed…), with the language switcher in the menu of Astra, OceanWP and GeneratePress, with a right-to-left language, with a site whose source language is Spanish, and with WordPress' own Query Loop pagination, comments, password-protected posts and search on translated pages.

1.7.10

Fixed: the excerpts of the «Latest posts» block (and any sentence ending with a «Read more» link WordPress writes itself) stayed untranslated: WordPress localizes that link on every page, so on /it/ the sentence never read like the one collected. The link now keeps its place and its words, like a date, and the sentence around it is translated.
Improved: the «your site, live» card of the switcher customizer shows a loading indicator instead of a white box while the page is drawn.
Tested: a site whose source language is not English (Spanish at the root with /it/ and /en/), the language switcher in every placement × layout on a block theme and on a classic theme, and every button of the plugin's admin pages clicked in a real browser.

1.7.9

Security: a translation can never carry markup its original did not have — whatever brought it in (an AI answer, an import, a paste, another plugin). Scripts, event handlers and foreign tags are removed when the translation is saved, in one place for every channel; texts translated through gettext are escaped when their source had no markup; a translation placed inside a script is encoded so «» cannot end it.
Security: a visitor can no longer make the site collect texts from invented «AJAX» addresses, read the translations of a language that is offline, or fill the page cache with spellings of the same address; the editor side panel only saves the strings of its own page; the universal importer reads this site only.
Fixed: the «Import pasted translations» of the editor side panel now pairs lines like the strings page (a line without a number continues the one before it).
Improved: the switcher customizer tells you when the header menu shows another profile, with a one-click «Use this profile in the header menu».
Fixed: a sentence with a bold or italic part that has no letters («Price 25% off tonight», «€ 1.234,56») is now collected whole; it used to be cut in two and the second half stayed untranslated.

1.7.8

Fixed: importing translations by copy and paste (Google Translate, DeepL…) matched a line without a number to the sentence in the same position, so a long text that the translator split over two lines pushed its second half onto another sentence — a cookie banner could end up showing a blog post. A line without a number now continues the line before it, and a translation that cannot belong to its original is skipped.
Fixed: clicking a colour preset in the switcher customizer now redraws the «your site, live» preview at once, and the preset's colours are applied to the language item in your header menu too (not only to the dropdown under it).
Improved: the switcher customizer tells you when the header menu is showing another profile than the one you are editing.
Fixed: windows and pop-ups that a plugin loads after a click and then shows (LatePoint's booking window, product comparison tables, quick views…) are now collected while you browse your site, so they can be translated. Their text used to be skipped as «hidden» and never looked at again.
Tested with 39 more plugins, among them Relevanssi, Ivory Search, SearchWP Live Ajax Search, Advanced Woo Search, Kadence Blocks, Happy Addons, Modern Events Calendar, WP Event Manager, LatePoint, Amelia, Bookly, YITH and HUSKY product filters, WPC Smart Compare, TablePress, wpDataTables, Popup Maker, GiveWP, Charitable, Fluent Forms, WPForms, Mailchimp for WP, Easy Digital Downloads, Ultimate Member, Paid Memberships Pro, Tutor LMS, wpDiscuz and wpForo.

1.7.7

Fixed: content loaded after the page (AJAX) on a translated page kept its scripts and styles whole. A script holding HTML in a string — like SupportCandy's ticket form — came back cut in half, and its «Submit» button did nothing.
Fixed: links in content loaded by AJAX (a portfolio's next page, «load more») now stay in the visitor's language even when none of its texts is translated yet — «Read more» used to lead back to the default language.

1.7.6

New: Switcher → «Your site, live» — with the languages in your header menu (or in a spot you chose) the Switcher screen shows your real header, drawn with the settings on the page before you save, on desktop and phone.
New: put the languages right after any item of your header menu (Switcher → Where in the menu → «Right after:»), not only at its start or end. Classic menus and the Navigation block of block themes.
New: a profile such as «header» can be the one in the header menu: choose «In my header menu» in that profile and the menu shows its style. One profile at a time.
Fixed: the colours of the switcher (text, hover, dropdown background, border, corners) now apply to the languages in your header menu too — they used to be ignored there.
New: the row of languages at the bottom of the page can be aligned left, centre or right, and shown as a table of 2, 3 or 4 columns (2 on phones); it takes the switcher's text colours. «Your site, live» shows the bottom of the page too.
Fixed: «Your site, live» shows only the languages your visitors see (not the ones still offline).

1.7.5

Fixed: «Translate in this browser» (no API key) now saves sentences that have a link or bold words inside. They used to come back without their link marks and stayed untranslated; now the marks are kept, and where the browser's translator drops them the sentence is translated piece by piece around its links.
Fixed: a phrase the browser's translator refuses is tried once, not again and again — the run could go round without end and the counter passed the total («Translating 162 of 154»).
New: «Translate in this browser» also on the screen of a single page (Translations → a page), for that page's strings only.
Fixed: the same link-safe translation in the visual editor's «Translate in this browser».
Fixed: in block themes (Navigation block) the languages in your header menu now show their flags, and open on click when the switcher is set to open on click — the rest of your menu keeps opening as before.
Clearer: a switcher profile other than Default says that the header menu, the spot on your page, the floating switcher and the bottom row all use the Default profile.

1.7.4

New: the language switcher in your theme's header menu — Switcher → «In my header menu». The languages become a real item of the menu, drawn by your theme like its other items, with its submenu and its phone menu: classic themes (Astra, GeneratePress, Kadence, OceanWP…), Elementor's Nav Menu, and block themes through the Navigation block. At the start or at the end of the menu. Where a page has no such menu, the switcher floats in the corner, so it is never missing. The setup wizard offers it when the theme has a menu.
New: if your switcher floats in a corner, TranslateRocket offers once to move it into your header menu — one click, and you see it on your site.
New: put the switcher exactly where you want — Switcher → «In a spot I choose on my page» opens your home page with the header, menu, footer and sidebar outlined; click a spot, choose its start or its end, and the real switcher shows there at once. Where the spot is missing or hidden (another page, the desktop menu on a phone) the switcher floats instead.
New: a row of languages at the bottom of every page, in a line or as a table, and a «Grid» layout for the switcher block and shortcode: flags and names in as many columns as fit.
New: 40 more languages, 77 in all — among them Catalan, Serbian, Basque, Galician, Lithuanian, Latvian, Estonian, Albanian, Macedonian, Bosnian, Georgian, Armenian, Azerbaijani, Kazakh, Urdu, Tamil, Telugu, Marathi, Gujarati, Punjabi, Nepali, Sinhala, Swahili, Afrikaans, Filipino, Icelandic, Irish, Welsh, Maltese, Belarusian, Mongolian, Khmer, Burmese, Amharic, Uzbek, Luxembourgish, Esperanto, Mexican Spanish, Canadian French and Swiss German — each with its flag, its own address and the WordPress language pack for the interface. A site written in one of them can now pick it as its own language.
Fix: DeepL received Traditional Chinese as Simplified Chinese, and Norwegian with a code it does not know.
Fix: on some sites the translated pages lost the theme's design — fonts, colours, the fixed header, footer menus — because a plugin printed an element in the page head (reported with The7, Elementor and the Angie assistant). The attributes of the page body are kept now, whatever another plugin prints.
Fix: Diagnostics had «Test connection» only for DeepL, OpenAI, Claude, Gemini and Google Translate: Groq, Cloudflare Workers AI and OpenRouter — the free providers the setup wizard recommends — could not be tested there. Every provider with a key is listed now.
Improved: when a provider refuses a key or answers with an error, «Test connection» says so in a plain sentence in your language («The provider refused this API key…») instead of the provider's technical answer, which stays in the Diagnostics log.
Fix: saving the settings raised a PHP warning (a leftover from a limit removed long ago); on a site that shows PHP warnings it could break the page shown after saving.
Fix: plugins that answer on WooCommerce's own AJAX address — FiboSearch's suggestions while a visitor types — answered in the source language on a translated page, and their links led back to the source language. They are translated now and the links keep the page's language (what the visitor typed is never collected). Links to pages of the site inside any AJAX answer keep the page's language too.
Fix: sentences a plugin or theme writes by hand into the page for its scripts, in a block marked type="text/javascript" — Ultimate FAQ's list of questions suggested while a visitor types in the FAQ search, and many older themes' messages — were skipped and stayed in the source language. Script templates (text/template) are still left alone.
Fix: on large sites (over 20,000 sentences) the block cart and checkout showed product attributes in the source language («Colour» on an Italian page), and form messages could stay untranslated: both read a group of interface sentences no longer filled since June. They now use the translations of what the cart holds and of the page the form is on.
Fix: sentences a plugin hands to its scripts with blanks the script fills in — Shortcodes Ultimate's lightbox counter «%curr% of %total%», «Showing %1$s of %2$s» — stayed in the source language where the plugin has no language pack. They are translated now, and a translation is used only if it keeps exactly the same blanks: a counter can never come out broken.
Fix: Social Chat — the header and footer of the WhatsApp box stayed in the source language: they are a short piece of HTML inside the plugin's settings. Words between paragraphs and headings are now translated; the HTML stays as it is.
New: text a translated page loads through admin-ajax after it is shown — Ninja Tables rows, many themes' «load more» — becomes translatable, filed under the page that asked for it. Before, it was translated only if the same sentence had been met elsewhere: a table's rows never were. Only public answers are read (never a cart, an account, an order, a signed-in customer's request or anything a visitor sent), and codes a script passes around are left out.
New: WP Job Manager — the job list on a translated page arrives translated, with the plugin's words in the page's language. It is loaded after the page from an address of its own (/jm-ajax/), which used to answer in the source language whatever page asked. The same holds for LearnPress' and bbPress' own AJAX addresses.
New: Events Manager — «next month» in the calendar of a translated page shows the events translated. The month is fetched from the page itself and came back with the month name translated and the events in the source language.
New: structured data for Google — a job's title (JobPosting, read by Google for Jobs) and descriptions written in HTML are translated; the HTML stays as it is. A sentence that holds bold or a link is left whole, never cut into pieces.
Fix: words a plugin keeps in an attribute whose name runs together — the message Ultimate Blocks' countdown shows when the offer ends, the «This field cannot be blank» and «invalid» errors of Formidable Forms fields — stayed in the source language.
Fix: once everything was translated, the Translations page still read «14 strings still to translate — 89%» next to a button saying «Everything is translated»: the addresses of the page's images were counted as text to translate. They are not (an image can be swapped per language, if you want), and the count now agrees with the button.
Improved: a simpler dashboard. The side menu keeps six entries (the other screens are one click away in the buttons at the top), notices from other plugins fold into one line on TranslateRocket's screens, and the Labs box is a single line.
Improved: with 77 languages, a search box over the language lists (setup wizard and Languages): type a language's own name, its English name or its code. The English name now shows next to the native one — «Српски Serbian».
Improved: Translations — one main button per page, «Translate»; «Start over» and «Hide» are in a «⋯» menu and still ask before doing anything. A new «Only pages still to translate» filter.
Improved: AI Translation — the providers you do not use fold to one line; the active one and those in your fallback chain stay open, and choosing a provider opens its card.
Improved: Switcher — where the switcher goes comes first, then its layout; colours, sizes, font and the phone options are under «More style options».
Fix: on Windows, Chrome and Edge showed the dashboard's emoji flags as two letters («GB»): the plugin's own flags are used instead.
Fix: on PHP 7, searching languages or pages by a name in a non-Latin script (Cyrillic, Japanese, Greek…) found nothing.
Fix: in Dutch, Polish, Russian and Japanese three counters of the dashboard showed in English («3 pages updated.»): their plural forms are in place now.
Improved: the Translations screen explains <1>… in a visible line where they appear: they mark a link or formatted words, which stay as they are on the site (until now only a tooltip said so).
Fix: on the Translations and Memory screens, the «Translate with your browser» panel appeared a moment after the page and pushed it down; it is drawn in place now.
Fix: on the Plugins screen, after the short «why are you leaving?» question, the deactivation page could open twice (the answer and a 4-second safety net both ran it).

1.7.3

New: e-mails sent to the visitor by contact forms reach them in the language of the page they wrote from, with their name and answers in place; e-mails to you keep the site's language. Contact Form 7 (the «Mail (2)» automatic reply), WPForms, Fluent Forms, Ninja Forms, Formidable Forms, Everest Forms and SureForms. Their sentences appear in the translation screens under their own heading («Contact Form 7 e-mails», «WPForms e-mails»…); in an HTML message only the text is translated, and a translation that lost one of the [tags] or {tags} is not used for that line.
New: GiveWP's e-mails to the donor (donation receipt, offline donation instructions) follow the language of the page the donation was made from. Sentences under «GiveWP e-mails».
New: the message shown once a form is sent (WPForms, Fluent Forms, Ninja Forms, Everest Forms, SureForms, Contact Form 7, Otter Blocks) becomes translatable the first time a visitor sends the form, under «Forms: messages and e-mails», and is then shown in the page's language. Before, it never appeared on a page, so it was never collected. Only the form's own wording is read, never what the visitor typed.
New: text a translated page loads from the REST API after it is shown — WP Go Maps marker titles and descriptions, and any other content fetched the same way — becomes translatable, filed under the page that asked for it (or under «Content loaded by the page»). Only public answers are read: never a cart, an order, an account, a signed-in customer's request or anything a visitor sent.
Fix: sentences with a date inside — «Posted on », used by most themes — stayed in the source language on every translated post: WordPress writes the date in the page's language, so the sentence never matched the one collected. A date now keeps its place and only the words around it are translated.
Fix: GiveWP 3 donation forms (shown in a frame that GiveWP prints without ) stayed entirely in the source language on translated pages — title, amounts, labels, payment methods. The form and receipt views are now translated like any page; the trrocket_translate_frame_view filter covers similar frames.
Fix: MetaSlider's arrow labels (and other slider options written as JavaScript rather than JSON: FlexSlider's prevText/nextText, Swiper's accessibility messages) stayed in the source language.
Fix: sentences WordPress builds around a title — the «Continue reading …» label of the more link, a composed feed title — are translated with the title in them; a post's category in structured data (articleSection) is translated.
Fix: headings of texts that are not on a page («Forms: messages and e-mails», «WooCommerce emails», the form e-mails…) are shown in the administrator's language; collected while a visitor used a translated page, they could be stored in that page's language.
Compatibility: Kadence Blocks' icon tooltips and Fluent Forms' payment item labels are translated. Checked with more popular plugins and themes: Chaty, Popup Builder, Otter Blocks, Strong Testimonials, Modula, WP Simple Booking Calendar, and the themes Twenty Twenty-Five, Neve, Sydney, Zakra, Botiga and Hestia.

1.7.2

New: a «Plugin language» menu at the top of every TranslateRocket screen. Read the plugin in English, Italian, Spanish, French, German, Portuguese (Brazil), Dutch, Polish, Russian or Japanese whatever your WordPress profile says — each user chooses for themselves, and «Automatic» keeps following the profile. It changes only TranslateRocket's own texts; the tooltip says where to switch the whole dashboard.
Compatibility: rotating «Fancy Text» phrases are translated phrase by phrase — Essential Addons keeps them in one attribute separated by bars, Premium Addons in the widget's JSON settings — and so are ElementsKit's countdown labels (Days, Hours…) and its Before/After image comparison labels. On/off switches that some blocks keep in attributes named like text (data-show-label="true") are never taken for words to translate. Checked with ten more popular plugins: Easy Table of Contents, Breadcrumb NavXT, AddToAny, Click to Chat (the pre-filled WhatsApp message too), Ally, CookieAdmin, FiboSearch, MC4WP, Essential Addons and ElementsKit.
Compatibility: words inside the JSON settings that widgets and chat boxes keep in data-* attributes are translated, keys and options untouched — Social Chat's WhatsApp button, Premium Addons' typing text — and Variation Swatches' colour and size tooltips. Plural labels kept in attributes ending in «-plural» are translated too (Qi Addons' countdown shows «Days» from data-day-label-plural).
Compatibility: MetForm forms (600,000 sites) are translated — labels, placeholders, the button and the error messages. MetForm prints each form as a JavaScript template that the page translation never read; now only its words are replaced and the template works as before.
Fix: on phones, the language list under «Published, or still being translated?» no longer pushes the ONLINE label out of the table, and the AI provider cards keep their fields, guide and buttons inside the card.

1.7.1

New: invoices from PDF Invoices & Packing Slips in the language of the order. An invoice, credit note, proforma or receipt is built in the language the customer ordered in — from the download link, attached to the e-mail or resent from the order screen — and your own footer is translatable under «WooCommerce PDF documents». The customer's details, the invoice number and product codes stay as they are; packing slips stay in the site's language for the warehouse.
Privacy: the customer's own details — names, company, addresses, e-mail, phone, order note — are no longer collected from WooCommerce e-mails as sentences to translate, nor ever translated. Before, every order e-mail could add them to the list under «WooCommerce emails»: those already there are removed when you update — only details of real orders, seen nowhere but in e-mails, so your shop's own sentences and their translations stay.
New: a check after every import. The imported translations are reread without AI: broken markup, scripts, a translation identical to the original, changed links or numbers, an odd length or the wrong language are listed on the Import page, to keep or remove one by one or all together.
Compatibility: the «do not translate» marks of other translation tools are respected — Google's notranslate and skiptranslate classes (GTranslate and many themes), TranslatePress's data-no-translation, Weglot's data-wg-notranslate — so a site that moves here keeps what it had excluded on purpose. On the html or body tag they still only mean «no browser popup».
Compatibility: text inside open shadow DOMs (cookie banners and widgets built as web components) is read and translated in the browser.
Compatibility: the social image (og:image, twitter:image) can have a different file per language like any other image; Yoast's «Written by» / «Est. reading time» labels for X (Twitter) are translated; template placeholders such as {{{ data.name }}} or %s alone are never treated as sentences.
Fix: in the visual editor, its own labels stay in the administrator's language on a translated page.
For developers: actions trrocket_translation_changed and trrocket_translation_deleted, fired when a translation is saved or deliberately removed (TranslateRocket Labs uses them for its History).
Tested with: GDPR Cookie Compliance, Say What?, Getwid, Stackable, Visual Portfolio, PDF Invoices & Packing Slips.

1.7.0

New: free AI translation with your own free account. Cloudflare Workers AI (10,000 «neurons» a day: about 1,900 sentences with Llama 3.3 70B, or 11,000 with the plain translation model, with a Quality setting — Best, Volume or Automatic), Groq (about 1,000 requests a day with gpt-oss-120b) and OpenRouter's free models are providers like DeepL or OpenAI: in the fallback chain, in bulk translation, in the visual editor. Each has a two-minute guide to get the key, «Load available models» to check it, and today's counter; a little before the free share runs out, the next provider of your chain carries on. Official APIs, no card needed.
New: the setup wizard offers free AI first. «Free AI, with your own free account»: a Groq key in 2 minutes with a Google account, a «Try the key» button, and the site translates from the first minute — in any browser, phones and Firefox included, where the browser translator does not exist.
New: the universal importer, on Import. Coming from a translation plugin with no importer here, or one whose tables cannot be read? Keep it on: TranslateRocket reads each page as visitors see it, in every language, finds its translations from the hreflang links, and pairs each sentence with its translation only where the two pages have the same structure — leaving out what changes on every visit and copies, keeping links and bold words. A scan first (nothing saved), then the import, then a side-by-side preview of every page per language while the old plugin still serves your site. Tested on the bench with TranslatePress, Bogo, qTranslate-XT, WPGlobus, WP Multilang, Multilanguage and Polylang, and on pages of 20 real multilingual sites (8 systems): language switchers, cached copies with other content and sentences in the wrong language are left out. It waits while TranslateRocket itself serves the languages, so it never reads its own pages back. Translators that work only in the visitor's browser (GTranslate free, Weglot's JavaScript) cannot be read from the server: the scan says so.
New: translation style from the kind of site, on AI Translation. A free AI reads your site's name, tagline and main pages and proposes the tone, formal or informal address for each of your languages, and the names never to translate; nothing changes until you press «Use this style». The house style now reaches every AI provider.
New: a «Sponsor on GitHub» button next to the donation link.
Improved: German admin screens address you consistently; the Labs page lists what Labs adds for teams.
Fixed: translations whose source string no longer existed were counted but never shown or exported; they are removed on update. Versions 0.1.0 to 1.5.9 are listed in changelog.txt, shipped with the plugin and readable at https://plugins.svn.wordpress.org/translate-rocket/trunk/changelog.txt

TranslateRocket – Free Multilingual Translation, Unlimited Languages

标签

下载

详情介绍:

安装:

屏幕截图:

升级注意事项:

常见问题:

更新日志: