=== TranslateRocket – Free Multilingual Translation, Unlimited Languages ===
Contributors: federicodev
Donate link: https://translaterocket.com/donate/
Tags: translate, translation, multilingual, language, woocommerce
Requires at least: 5.6
Tested up to: 7.1
Requires PHP: 7.4
Stable tag: 1.8.28
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

Translate your whole site with no API key — Chrome and Edge do it on your own computer. Unlimited languages, free, no paid tier.

== Description ==

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.
* 🆓 **Free AI on your own free account** — Groq, Cloudflare Workers AI or OpenRouter’s free models, with a two-minute guide to the key and no card; and, with the free Labs add-on, MyMemory with no key at all (about 5,000 characters a day, about 50,000 with 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/ .

== External services ==

This plugin can connect to third-party services, but only with your involvement:

* **AI translation providers (optional).** If you add an API key and ask to translate, the relevant text is sent to the provider you selected so it can return a translation. No text is sent until you configure a provider and trigger a translation. Providers and policies:
  * DeepL — service: https://www.deepl.com/en/pro , privacy: https://www.deepl.com/en/privacy
  * OpenAI — service: https://platform.openai.com , privacy: https://openai.com/policies/privacy-policy/
  * Google Cloud Translation / Gemini — service: https://cloud.google.com/translate , privacy: https://policies.google.com/privacy
  * Anthropic (Claude) — service: https://www.anthropic.com , privacy: https://www.anthropic.com/legal/privacy
  * Cloudflare Workers AI — service: https://developers.cloudflare.com/workers-ai/ , privacy: https://www.cloudflare.com/privacypolicy/
  * Groq — service: https://console.groq.com , privacy: https://groq.com/privacy-policy/
  * OpenRouter (and the provider of the model you pick there) — service: https://openrouter.ai , privacy: https://openrouter.ai/privacy
* **Google Translate (manual, always available).** Every editor offers a per-phrase link and a copy-paste box that open Google Translate (translate.google.com) prefilled, so you translate on Google's own site and paste the result back. This is just a convenience link — your browser, not the plugin, contacts Google. Service: https://translate.google.com , terms: https://policies.google.com/terms , privacy: https://policies.google.com/privacy
* **Optional one-click Google auto-fill (off by default).** A site owner can opt in (the `TRROCKET_AUTO_GOOGLE` constant / the `trrocket_auto_google` filter) to let the server fetch a translation from Google's free endpoint with one click. This uses an undocumented endpoint and is best-effort, so it is disabled out of the box and the plugin never calls it on its own. For dependable automatic translation use the official AI providers below.
* **translaterocket.com support ticket (optional, on request).** The Diagnostics screen has a form that opens a support ticket for you. It sends nothing until you fill it in and press Send, and what it sends is exactly what the page shows you: your name, your email address (so the answer can reach you), your subject and message, your site address and the plugin version, plus the technical report if you leave that box ticked. The report never contains API keys. To prove the request really comes from your site and not from a spam robot, the support site then makes one request back to your site's home URL with a one-time token. Nothing else is transmitted, nothing is stored on your site, and if you would rather not use it the same page still offers the copy-and-paste route. Service: https://translaterocket.com , privacy: https://translaterocket.com/privacy-policy/
* **translaterocket.com deactivation feedback (optional, only if you press Send).** When you deactivate the plugin, a box asks why. The answer is saved on your own site. Only if you press «Send and deactivate» is it sent to https://translaterocket.com/wp-json/translaterocket/v1/farewell : the reason and the quick answers you picked, what you typed, your e-mail only if you typed it to get a reply, your browser type, and the details shown in the box (plugin, WordPress and PHP versions, number of languages and of detected and translated sentences, the translation provider in use and which providers have a key — never the keys themselves —, where the language switcher is placed, whether the setup wizard was completed, minutes and days since install, your admin language, the active theme and the folder names of the other active plugins). No site address, no name, no page or translation content; the IP address is not stored. «Skip and deactivate» sends nothing, and the `trrocket_farewell_send` filter turns sending off entirely. Service: https://translaterocket.com , privacy: https://translaterocket.com/privacy-policy/
* **translaterocket.com (optional).** The "Help & Feedback", "Request customization", "Send feedback" and "Get tips & updates" links open translaterocket.com in your browser with your site's domain in the URL. Nothing is sent automatically — these are links you choose to click. Service: https://translaterocket.com , privacy: https://translaterocket.com/privacy-policy/

== Installation ==

1. Install TranslateRocket from **Plugins → Add New** (search for "TranslateRocket") and activate it.
2. Open **TranslateRocket**: the Simple view shows three steps. Tick the languages you want and save.
3. Press **Translate** next to a language: Chrome or Edge translate it on your computer, free and with no key — or add a free AI account, or your own key, whenever you like.
4. Flip the language's switch to **Online** when you are happy with it. Until then only you see it.
5. Add the language switcher and the search box where you want them — block, shortcode or menu — from the **Switcher** and **Search** screens.

First steps, filmed from installation to the first translated page:

https://www.youtube.com/watch?v=FgrO7Fqun4U

== Frequently Asked Questions ==

= Is it really free? =

Yes. All translation features and unlimited languages are free, with no paid tier inside the plugin. You only ever pay your own AI provider, directly, if you choose to use AI.

= How do you keep it free with no income from it? =

I build websites for a living, and I use TranslateRocket on every multilingual site I make. Every fix reaches those sites the day I release it, so the plugin gets maintained because I need it maintained — publishing it for everyone costs me nothing on top of that. What comes back is worth more to me than a licence fee would be: bug reports from setups I could never reproduce on my own, which end up improving my own clients' sites too. Donations are welcome and change nothing about what the plugin does.

**And if you want that work done on your own site, you can hire me.** Building and fixing WordPress sites is the day job: a site built from scratch, a design put right, a multilingual setup done properly, custom development, a migration off a plugin that charges you every month. That is where the money comes from — not from crippling this plugin. Ask me from the "Help & Feedback" screen inside the plugin, or at https://translaterocket.com/support/ .

= Do I need an AI key? =

No — and without one you are not limited to typing by hand. **Chrome and Edge on a computer carry a translator that runs on the device itself, and one button puts it to work on your whole site.** It costs nothing, needs no account and no signup, and the text never leaves your machine. Quality sits below DeepL and the AI models, so it is the quickest way to a translated site rather than the finest one — but everything it translates is kept, so adding a provider later never repeats the work.

It needs Chrome, or Edge 148 or later, on a computer that can run the built-in model: Windows 10 or 11, macOS 13 or later, Linux or ChromeOS (not Windows Server), 16 GB of RAM or a graphics card with more than 4 GB, and 22 GB of free disk space, with the admin on https. Anywhere else, the copy-and-paste route works in any browser and still needs no key.

Beyond that you can click any text on the live page and type its translation, edit it again later, and publish it. Every field also offers a free Google Translate link you can paste back from. AI keys are optional and only used at the moment you ask for one.

Two minutes, filmed on a real site: translating a page with no key at all.

https://www.youtube.com/watch?v=J0TxlZBKaWc

= Do my translations stay on my site? =

Yes. Translations are stored in your own WordPress database. Text is only sent to the AI provider you configure, at the moment you ask for a translation.

= Does it work with caching plugins? =

Yes. Each language lives under its own URL (e.g. `/it/`), so page caches store each language separately and automatically.

= Does it work with WooCommerce? =

Yes. Product pages, categories and attributes are translated like any other content, and slugs are translated per language. It also covers the parts WooCommerce renders outside the page HTML, which a page-only engine misses: the AJAX mini-cart fragments, strings passed to JavaScript (such as the "View cart" link), and transactional emails — the order's language is recorded at checkout (classic and block/Store API) and the customer email is rendered in that language. Wording that only ever appears inside an email (WooCommerce's own "Thank you for your order", "Quantity", "Price") is picked up automatically the first time such an email is sent and filed under "WooCommerce emails" in the translation screens, so you can translate it like anything else. Multi-currency is out of scope: TranslateRocket translates, it does not convert prices.

The whole shop translated, from the product page to the order e-mail:

https://www.youtube.com/watch?v=kU0TConiT20

= Does it translate forms (Forminator, Contact Form 7, WPForms…)? =

Yes. Labels, placeholders, options and buttons are translated with the rest of the page, whether the form is added with a shortcode, a block, a widget or a page builder such as Elementor. The messages the form plugin adds with JavaScript — validation errors, "message sent" — are translated too, on Forminator, Contact Form 7, WPForms, Gravity Forms, SureForms, Formidable and Ninja Forms. With Forminator, the thank-you message, forms loaded with "Load form using AJAX" and the e-mail notifications follow the language of the page the form was sent from; the wording of the form settings and e-mails appears under "Forms: messages and e-mails" in the translation screens once an administrator has viewed the form or a notification has been sent. To keep a notification (for example the copy for the site owner) in the source language, return false from the `trrocket_forminator_translate_notification` filter.

= Is there a PHP function that returns the current language? =

Yes, for theme and plugin code that needs it (the equivalent of Polylang's `pll_current_language()`): `trrocket_current_language()` returns the code of the language of the current request, such as `en`, `fr` or `pt-br` — also in AJAX requests sent from a translated page — and `trrocket_default_language()` returns the site's source language. Wrap calls in `function_exists()` so your code keeps working if the plugin is deactivated.

= Which plugins can I import my translations from? =

Yes — use **TranslateRocket → Import** to bring over your existing translations. The WPML import covers both its string translations and its post-based translations (titles, slugs and matching body text), and reads directly from WPML's tables, so it works even when WPML is already deactivated. Coming from Weglot (a hosted service)? Export your translations from the Weglot dashboard as a CSV and upload the file on the same Import screen — the columns are detected automatically and mapped to your target languages.

To review the result safely, turn on **Preview mode** ("Who sees the translations" in Settings): you browse the fully translated site while visitors keep seeing the default language, and one click publishes it when you are happy.

Safer still: run TranslateRocket next to your current plugin, import, and switch only when you are happy. Two minutes:

https://www.youtube.com/watch?v=K5qmxn3_4po

= Can visitors search my site in their own language? =

Yes, for free. The search box of TranslateRocket always searches in the language of the page: on `/de/` a visitor types in German and finds your pages, posts and WooCommerce products by their translated title, excerpt and content, with suggestions while typing, and the results open on the German pages. You can let it look in every language at once, choose which content types it shows and add filters. The search box WordPress already has on your site, Ajax Search Lite and FiboSearch understand the translated words too.

= What if a page shouldn't exist in another language? =

Open the page and use the "Language visibility" box to redirect it, show a custom message, or return a 404 — per language.

= Can I show something in one language only? =

Yes. Wrap it in `[translaterocket_language lang="it"]…[/translaterocket_language]` — several languages work too, as `lang="it,de"` — or use `not="it"` to show it everywhere except Italian. In the block editor you do not need the shortcode: add the class `trrocket-only-it` or `trrocket-hide-it` in "Advanced → Additional CSS class(es)" of any block, navigation links included. Content limited with `lang=` or `trrocket-only-` is taken to be written in that language, and is shown exactly as you wrote it.

= Can a menu item appear only in some languages? =

Yes. In Appearance → Menus every item has a "Show in" row with one checkbox per language; nothing ticked means every language. Hiding an item hides its sub-items too. Block themes build menus with the Navigation block instead: there, give a link the class `trrocket-only-it` or `trrocket-hide-it`.

= Can I translate with ChatGPT or Gemini without an API key? =

Yes. Open a page in the visual editor, click "Translate page" and use "Copy with a translation prompt" — or the ChatGPT and Gemini links, which copy the same thing. The prompt carries your languages, the words you never translate, your glossary and your house style, and asks for the reply in a code block with the line numbers intact. Paste the reply in box 2 and apply it.

And when a machine translation gets a word wrong, fixing it takes ten seconds:

https://www.youtube.com/watch?v=Bc83GXh1NvI

= My browser isn't Chrome or Edge, or I work from a phone. Can I still translate without a key? =

The translator built into the browser exists only in Chrome and Edge on a computer. TranslateRocket Labs, a separate free add-on you can ask for at https://translaterocket.com/labs/, adds free translation engines that work from any browser, phones included — each one is switched on only after you read and accept its conditions. Labs is not needed: everything described on this page works without it.

Both, in one minute — a page translated in the browser with no key, then Labs translating a new page the moment it is published:

https://www.youtube.com/watch?v=Zsf1PXWFhVI

== Screenshots ==

1. Your whole site in every language: each language on its own address (/it/, /de/, /fr/), ready for Google, with a language switcher for your visitors.
2. Free translation in three steps: choose your languages, press Translate, put them online. Your own browser (Chrome or Edge) translates for free, with no API key and no account; free AI accounts or your own keys are there when you want more.
3. A free search box that speaks every language: visitors type in their own language and find your pages, posts and products, with suggestions as they type. Add it to your menu, as a block or with a shortcode.
4. Click any sentence on your page to fix it: type it yourself, or ask the browser translator, Google Translate or your AI.
5. Coming from another plugin? WPML, Polylang, TranslatePress and ten more have their own importer; the universal importer reads your pages as visitors see them, with a preview before you switch.
6. Design the language switcher — dropdown or list, flags, colours — with a live preview.

== Changelog ==

= 1.8.28 =
* Improved: on the «Automatic» page an engine you tick but that cannot work yet says so right under its name — conditions not accepted, «where it runs» set to the server only, or paused by the service — with a link to the one thing to do. Ticking an unofficial engine opens its conditions and lights up the box to tick, instead of saving an engine that then comes back grey.
* Improved: without Labs, the locked engines explain in one line how to switch them on (get Labs, come back, tick them).
* New: with Labs 0.9.13, under Advanced you choose how hard the background translation works on your server: Light (1 page every 2 minutes), Normal (3 pages a minute) or Fast (6 pages every 30 seconds).

= 1.8.27 =
* Fixed: on a big site (hundreds of thousands of translations) the check that decides whether the progress numbers must be counted again was itself a scan of the translations table, run up to 26 times on every admin screen. It is now one index-only query per screen.
* Improved: TranslateRocket Labs 0.9.12 no longer counts the sentences still to translate in every language on every wp-admin screen: only when a browser engine (Chrome's translator, Google unofficial) may work there, and keeping the last count for a while on a site that is translating.

= 1.8.26 =
* Fixed: with Themify's page cache on (Themify Ultra and the other Themify themes, Themify Builder), the first language a page was shown in was served to every visitor afterwards: a Polish site showed its Polish home page on /de/ and /en/, and the language seemed to change at random from one page to the next. Themify now keeps one copy per language, and its cache is emptied together with TranslateRocket's.

= 1.8.25 =
* Fixed: on a big site translating in the background with every language still offline, the site's whole page cache (LiteSpeed, WP Rocket, Breeze…) was emptied every ten minutes and rebuilt, for pages no visitor could see yet: CPU at 65% with spikes on a 4.000-page site in 13 languages. While every language is offline, the background work now leaves the site's caches alone; they are emptied the moment a language goes online.
* Improved: TranslateRocket Labs 0.9.11 no longer clears a language's maps on every page when nothing was translated into it (17 writes per page saved).

= 1.8.24 =
* Fixed: «Translate all» could stop with a couple of sentences left and no word about them, when its time ran out while asking the engine again for single sentences. It now goes on until they are done.
* Fixed: a long name the engine rightly gives back unchanged (a region such as «Aisén del General Carlos Ibañez del Campo» in WooCommerce's list) stayed «to translate» for ever. It is now saved as it is.
* New: the «Automatic» page shows what is being translated right now — the engine, the page and the language — with an hourglass on that engine. It is rebuilt every 30 seconds and disappears by itself when the work stops, even if a step is cut short.
* New: «Pause» and «Resume» on the «Automatic» page, «Just finished» with the last pages completed (each opens in its translated language), and «Every engine is resting until…» when the free engines are taking a break.
* Improved: the pages line is always there: how many pages the site has, and once started how many are read and how many are left.
* Improved: ticking an engine on the «Automatic» page saves it at once, with no «Save» button to look for at the bottom.
* New: in the visual editor, the image window lists the texts of the image (alt text, title) with what visitors read now; a tap translates them.
* Fixed: with another translation plugin active (GTranslate, Weglot…), the visual editor said «visitors now see» your language although visitors still see the other plugin. It now says so, with a link to Plugins.
* Fixed: in the visual editor, clicking a link or button of the page before the editor had finished loading followed the link and left the page.
* Fixed: the image window of the visual editor could not be closed with ✕ or Esc, and on phones its address box ran past the edge.
* Fixed: WooCommerce products with more than 30 variations: the description, stock line and image texts of the chosen variation came back in the original language.
* Fixed: oEmbed of translated pages: a translated address pasted into another WordPress site (or read through the discovery link) answered «not found». It is now recognised, with the title in its language; languages still offline stay private.
* Fixed: Brizy and Brizy Pro: on translated pages the photos disappeared and links pointed to «/it//page/», because Brizy builds them from the site address. Photos and links now work in every language and in the preview.
* Fixed: addresses of files built by other plugins (images, styles, scripts under wp-content) no longer get the language in them, which made them «not found» on translated pages.
* Improved: big sites while they translate: the «Automatic» page and the admin screens no longer count every language again each time a sentence is saved — on a site of 60,000 sentences and 14 languages, from about 10 seconds of database work every 30 seconds to under half a second. The numbers may be a minute or two behind while the work runs.

= 1.8.23 =
* Fixed: on servers with a newer libxml (the HTML reader PHP uses), pages in non-Latin scripts — Arabic, Russian, Greek, Chinese… — could come out garbled («Ø / Ù») in the translated pages and in the visual editor, because libxml ignored the UTF-8 hint it was given. Pages are now read in a way that does not depend on that hint, on every version.
* Fixed: on child pages, the hreflang tags and the language switcher now use the translated address of every parent in the chain, as the sitemap already did, instead of a mix of translated and original ones.
* Fixed: hyphenated words such as «Wi-Fi», «On-line», «on-site» or «pre-sale» were taken for language codes and left untranslated.
* Fixed: in block-theme menus, a menu item with sub-pages was read as one sentence with its sub-menu hidden inside, and could stay in English; the language names in the switcher are no longer translated («English» stays «English»), as in classic menus.
* Fixed: a long sentence that an engine sends back unchanged is no longer saved as translated: the next engine is tried, or it stays to be translated.
* Fixed: «Translate all» stopped when a step answered with an HTML page instead of data (for example while the server's object cache was restarting). It now waits and tries again by itself.
* Improved: the TranslatePress importer works in steps of 20 seconds that continue by themselves, so large sites (tens of thousands of translations) import on hosts that cut requests at 30–60 seconds.
* Improved: the «Automatic» page says «Paused» when the reading of the site is paused, with a link to resume it in Labs, and estimates the days left from when it was resumed.

= 1.8.22 =
* Fixed: a child page whose parent has a translated address but which has none of its own in a language (/ja/特長/block-theme-menus/) answered 404, and so did its old address after the redirect. It opens now.
* Fixed: on a page that does not exist, the language switcher led to the same missing address in every other language; it now leads to each language's home page, so visitors and search engines no longer walk from one 404 to the next.
* Fixed: with a Groq (or other) key saved but no engine marked as active, «Translate page» in the visual editor tried the browser's own translator — absent in Firefox, Safari and on phones — and reported «could not be translated». The first ready engine is used, as «Translate all» already did. The setup wizard also makes Groq the engine when «Free AI» is chosen with a key already saved.
* Fixed: right after «Translate page», a sentence with a link or bold words showed its marks («<1>our story</1>») in the editor until the page was reloaded. The links and bold words are put back at once.
* Fixed: after the setup wizard, the Translations screen said «0 strings detected» and «Everything is translated» although the home page had just been translated. When you open a translated page, the site now reads the original page once in the background so its sentences are counted; with nothing found yet the button says «scan the site first».
* Fixed: «Translate all» with Groq's free plan could stop halfway without a word when Groq asked for a pause of a second or two (its limit per minute), because Groq's message about its per-minute limit mentions «billing» and was taken for an empty account. A rate limit is never taken for a spent quota any more; the pause the provider asks for is waited out, and the screen says the translation goes on by itself.
* Fixed: the background cache warm-up kept asking the site for its own pages even when the server could not answer itself (every request waiting 15 seconds), keeping PHP busy on small hosts. After the first time-out it now waits 30 minutes.
* Fixed: a sentence the engine translated but whose link marks it lost was kept in the original language and counted as translated. It now stays to be translated, and is tried again.
* Fixed: links your theme writes with the language already in them (/it/support/) now get the page's translated address too, instead of going through a redirect on every click.
* Improved: the welcome notice no longer asks you to pick your languages after you have finished the setup wizard; the plugin's description in the Plugins list says that no API key is needed.

= 1.8.21.1 =
* Improved: translated page addresses come first from the menu label of the page (short: «How it works» → /it/come-funziona/), then from its title only when the title is short (six words at most). A page whose title is a whole slogan keeps its original address instead of getting a very long one.
* Fixed: punctuation of every script is left out of translated addresses (Japanese and Chinese «、» and «。», Spanish «¿», «!»…).
* Fixed: accented letters follow the address's own language (German «Über» → «ueber», «Datenschutzerklärung» → «datenschutzerklaerung»), and a menu label or title left the same in a language (a brand, a name) makes no address.
* Fixed: switching «Translate the addresses of pages and posts» off now stops the work already running in the background at once.

= 1.8.21 =
* New: translate your site with the chat AI you already have — ChatGPT, Gemini, Claude… — with no API key (Import screen). Download the sentences of a language in files small enough for a chat (only the missing ones, to complete it, or all of them, to have it checked), give each file to the AI with the ready-made instructions, and import the file it gives back, or paste its answer. Every row is checked on import (tags, placeholders, rows moved, sentences left untranslated, code added) and the report says what was skipped and why; one link undoes the whole import. Works in steps on large sites.
* New: translated page addresses. Settings → «Translate the addresses of pages and posts»: each page, post and product gets in every language the address made from its translated title (/it/chi-siamo/), the links of the site follow, and the original address answers with a 301. Addresses typed by hand are never changed, and an address never changes once made. On for new sites; sites updating keep their addresses until they switch it on.
* New: «Language switcher» in Appearance → Menus. Add it to any menu, anywhere — top level or inside a submenu, in several menus at once — and it becomes your languages, in the style of the Switcher screen. Thanks to the shop owner who suggested it.
* Fixed: in the visual editor, «Restore original» on a theme or shop label (like «Add to cart») put back the label as WordPress had already translated it, so nothing changed for visitors. The editor now shows and restores the real original.
* Fixed: child pages with a translated address (typed by hand or made from the title) answered 404; the whole address is now translated, parent pages included, in the links and in the sitemap.
* Improved: «Translate again» and its «Undo» work in shorter steps (about five seconds).

= 1.8.20.3 =
* Fixed: on large sites, «Undo» after «Translate again the sentences that contain them» stopped after its first step, leaving part of the translations aside (they were kept, and a second click put them back). It now goes to the end by itself. Each step is also shorter (about five seconds).

= 1.8.20.2 =
* New: «Also in these menus» on the Switcher screen. Sites with one menu on the computer and a different one on tablets and phones can now have the languages in both: tick the other menu — a place of your theme, or any menu by name, which also covers the phone panel of Blocksy, Elementor's Nav Menu and other headers that call the menu itself. Before, the languages went into one menu only. Thanks to the shop owner who asked.

= 1.8.20.1 =
* Fixed: «Translate again the sentences that contain them» ended in «Request Timeout» on large sites (many languages, a long glossary). The sentences are now read once, a block at a time, and the work goes in steps of a few seconds, with a progress page that carries on by itself; «Undo» works the same way. On a test site with 60,000 sentences, 14 languages and 150 glossary terms, finding them went from 180 seconds in one request to under 7. Thanks to the shop owner who reported it.

= 1.8.20 =
* Improved: when an AI engine refuses a request, the visual editor now says why in plain words and stops — a key that is wrong or out of credit, the daily limit reached — with a link to fix it, instead of leaving the page half translated with a row of warnings. A busy service (429, 5xx, timeouts) is tried again by itself up to three times.
* Improved: the setup wizard tries your Groq key with one word as you finish. If Groq refuses it, the last screen says so at once, with the link to copy it again — or the way to translate in your browser without a key — instead of «You're all set».
* New: at the end of the first translation, if the language is still visible only to you, the editor offers «Show it to visitors» — one click and visitors see it, with the language switcher.
* New: «Translate again the sentences that contain them» on the Exclusions screen. After adding names or glossary terms, only the translated sentences that do not respect them go back to «missing», in every language, and are translated again with the new rules. One link undoes it. The glossary is now also passed to AI engines with each request.
* Fixed: the site scan now visits category, tag and shop archive pages too, so their texts — SEO titles and descriptions included — are collected and translated even if nobody has opened them yet. Thanks to the shop owner who reported it.
* New: «Also in the phone menu of your theme» on the Switcher screen. Themes like Blocksy have a «mobile» menu place; when it holds another menu (categories, for example), untick it and the languages stop appearing twice. Phones without the main menu still get the floating switcher.
* Fixed: on Apache servers, if the site's rewrite rules were saved while a translated page was being served (by WP-CLI or by a plugin that refreshes them during a visit), .htaccess could get «RewriteBase /it/» and every page answered with an error. The rules are now always written with the site's own address.
* Fixed: Cloudflare Workers AI with an e-mail or a wrong value in the «Account ID» field: the right account is now found from the token and saved, instead of failing every request.

= 1.8.19 =
* Improved: right after the setup wizard, «Translate my homepage now» translates your homepage by itself with the engine you just chose — you watch it turn into your language. Before, the page opened still in the original language and the translation was behind two buttons, so some of you thought nothing worked.
* Faster: «Auto-translate everything with AI» in the visual editor sends ten sentences per request and saves them together, instead of two requests for every sentence. A homepage takes seconds instead of minutes.
* Fixed: the page counter in the editor bar now moves while the page is being translated, instead of staying at 0% until the end.

= 1.8.18 =
* New: cache warm-up. Each time TranslateRocket clears the caches, a minute later the home and the most visited pages of every language are visited again in the background, a few at a time, so the next visitor finds them ready instead of waiting for the page to be built. The pages come from the visit statistics, or from your menu. It runs only with a page cache (ours, WP Rocket, LiteSpeed, Breeze…), waits when the server is busy, and can be switched off in Settings.
* Fixed: with Complianz, consent given on a translated page was stored for that language only (/it/), so the cookie banner came back at every change of language. Consent now covers the whole site, as with the other multilingual plugins Complianz knows.
* Fixed: with LiteSpeed Cache, REST answers loaded by a page (maps, sliders, «load more») could be cached in one language and served to all of them. Answers asked by a page of the site now stay out of the page cache; calls from apps and other servers are cached as before.
* Fixed: «link on the whole box» of page builders now leads to the page in the visitor's language: Essential Addons' Wrapper Link, Premium Addons' element link, Divi Supreme's lightbox, clickable columns and Divi 4's module, row and section links. Developers can add more attributes with the trrocket_url_attributes filter.

= 1.8.17 =
* New: «Translate the addresses of categories and tags» (Settings, next to SEO meta). On, as before, each language uses the translated name: /de/product-category/drucker/. Off, every language keeps your own slug: /de/product-category/printers/ — the links, the hreflang tags and the language switcher all follow, and translated addresses that search engines already know move to the plain address with a 301. For shops whose category addresses are already indexed. Developers can choose per taxonomy with the trrocket_translate_term_slugs filter.

= 1.8.16 =
* Fixed: on WooCommerce shops, translated product category and product tag addresses answered 404 (for example /de/product-category/drucker/). The links used the translated name, but the address was not recognised when a visitor opened it. Custom category bases, subcategories and any public taxonomy are covered. Thanks to the shop owner who sent the details.
* New: when a category or tag is renamed, or its translation is corrected, its translated address follows, and the old address sends visitors and search engines to the new one with a 301. Slugs imported from other plugins are left as they are.
* New: every AI engine card shows the recommended model, with a «Use it» button; in the model lists the recommended one comes first and is marked. Groq and OpenRouter lists updated after a translation test of their free models.
* New: «Use this engine» on every engine card. Switch an engine off and it is never used, not even as a fallback, while its key stays saved (for example when the account has no credit left).
* Improved: «Test this text» lets you choose the language to translate into, refreshes the «free requests today» counter at once, and warns when the result mixes in letters of another alphabet, a sign that the model does not suit that language.
* Improved: search across all languages runs one database query instead of one per language: on sites with many languages each suggestion is several times faster.
* Fixed: text added by JavaScript inside an area listed in «Exclude selectors» was still collected when an administrator viewed the page (for example a help-desk plugin showing tickets). It is now skipped, like the rest of the area.
* Fixed: OpenRouter's «no endpoints found» on a free model now says that the model's free provider is not answering, instead of «the model does not exist».

= 1.8.15 =
* Faster pages for your visitors while translations run in the background: Labs, WP-Cron and WP-CLI now clear the site's caches (page cache, Breeze, LiteSpeed, Varnish, object cache) at most once every ten minutes, instead of after every page. The last change is still shown within ten minutes; what you edit by hand is shown at once, as before.
* An engine that is only resting (DeepL paused after refusals, a free engine that has used its share for the hour) is no longer logged as «AI translation failed» for every language and step: one «Translation is waiting» line, with the time it goes on. Real failures are still logged as before.
* The «i» buttons of the overview link to the page of translaterocket.com that explains each feature, in your language when the site has it.

= 1.8.14 =
* Faster and lighter «Translate all» on small servers: each step writes to the options table about 80% less (the maps were flushed after every sentence, with a scan of the whole table each time) and runs about half the database queries; the settings are read once per request. Thanks to Isis for the PHP slow log that pointed straight at it.
* «Translate all» goes on by itself after a 502, 504 or Cloudflare 524 from your server, waiting a little longer each time, instead of asking you to press the button again.
* One translation at a time on the site: a second tab, or Labs in the background, waits for the one running instead of loading the server with several PHP processes at once.
* New WP-CLI command: wp translaterocket translate --lang=zh (or --all), with --engine, --batch and --pause. Translate the backlog in one low-priority process, away from your visitors.
* DeepL that keeps refusing a key rests an hour, then a day, then a week, instead of being asked again every hour; «Test» on the AI screen tries it at once.
* The daily character cap for paid AI and DeepL's rest are kept in the database: a cache purge (object cache, Breeze, WP Rocket, LiteSpeed) no longer resets them.
* When Chrome's built-in translator does not start (its model stays at 0%, or it stops with an error), the Translations screen offers a free Groq key at once.
* Block themes: a different Navigation menu per language now works with Twenty Twenty-Five as installed (WordPress showed the newest menu in every language), and the menu chosen for a language is left as written.
* Fixed: automatic updates could be rolled back on slow hosts. Right after an update WordPress loads the home page once to check for errors, and that request ran the database upgrade of the new version; on a shared host it could pass the 50 seconds WordPress waits, and the update was undone. The upgrade now runs on the next request, one request at a time.
* Fixed: the safety net that removes key-like strings from the diagnostics report did not match anything since August; keys you had configured were always removed.

= 1.8.13 =
* New: The SEO Framework. Its sitemap is a single list, so the translated pages were in no sitemap: now every translated address is inside it. Its og:locale was printed twice on translated pages; now once, and a repeated og:locale from any other SEO plugin is removed too.
* New: «Read more» in the ⓘ buttons of engines, limits, bots and search opens the page that explains the feature on translaterocket.com, in your admin language when the site has it.
* New: a «Step-by-step setup guide» link in the setup wizard and on the Start screen.
* Improved: the box that describes the chosen engine on the Translations screen is easier to read — one tile per fact, the quality with its bars. «All free» in the overview is now a green label.
* Fixed: the «Crawlers» checkbox on the AI screen was saved but did nothing, because a visit never starts an AI translation. The row now says so instead of offering a switch with no effect.
* Fixed: the help of «Fallback priority» said that providers left on «—» stay out of the chain; they are used after the numbered ones, and the text now says so.

= 1.8.12 =
* Fixed: links inside translated pages now use the translated slug of the page they point to — a button to «/start-here/» leads an Italian visitor to «/it/inizia-da-qui/», not «/it/start-here/». The source-slug address, if someone still reaches it, moves there with a 301, so canonical, hreflang, the switcher and the sitemap all name the same page. Thanks to Tommaso for reporting it.
* Fixed: in the Simple view, «Translate» next to a language only opened the Translations screen, and nothing seemed to happen. It now starts the translation with the engine in the menu.
* Fixed: the percentages count only sentences that are on a page of the site. Sentences of pages rewritten or deleted, and pieces of pages read directly through the REST API by crawlers, kept a fully translated site below 100%. «Translate all missing» skips them too, so no engine time goes to text nobody sees.
* Fixed: a code example made only of tags (an hreflang snippet in a tutorial) is not a sentence any more; ones already collected go with the update.

= 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/», «<head>», «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 «</script>» 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 <strong>25%</strong> off tonight», «<em>€</em> 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>…</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 <date>», 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 <html>) 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

== Upgrade Notice ==

= 1.8.28 =
Clearer engines on the Automatic page (why one is not working, what to do) and a Light / Normal / Fast server-load setting with Labs 0.9.13.

= 1.8.27 =
Big sites: far fewer database scans on every admin screen. Pair with Labs 0.9.12.

= 1.8.26 =
Themify themes with page cache on: translated pages were served in the wrong language. Fixed.

= 1.8.25 =
Big sites translating in the background with languages offline: no more page-cache purge every ten minutes (CPU). Pair with Labs 0.9.11.

= 1.8.24 =
See what is being translated right now (engine, page), pause and resume from the «Automatic» page, image alt and title in the visual editor, WooCommerce variations, oEmbed of translated pages, Brizy photos, and much lighter counting on big sites.

= 1.8.23 =
Non-Latin sites (Arabic, Russian, Chinese…) no longer come out garbled on newer servers, correct hreflang on child pages, «Wi-Fi» and similar words translated, and large TranslatePress imports in steps.

= 1.8.22 =
Child pages under a translated parent no longer answer 404, «Translate page» works with a saved key in every browser, correct counts after the setup wizard, and «Translate all» no longer stops at Groq's per-minute pause.

= 1.8.21.1 =
Shorter translated page addresses (from the menu label), no punctuation in them, and switching the option off stops at once.

= 1.8.21 =
Translate with ChatGPT, Gemini or Claude through a file, translated page addresses, the language switcher in Appearance → Menus, «Restore original» for theme and shop labels.

= 1.8.20.3 =
«Undo» of «Translate again» goes to the end on large sites.

= 1.8.20.2 =
The language switcher can go in more than one menu: one for the computer, another for tablets and phones.

= 1.8.20.1 =
«Translate again the sentences that contain them» no longer times out on large sites: it works in short steps with a progress page.

= 1.8.20 =
AI engine errors explained and handled, Groq key checked in the setup wizard, «Show it to visitors» after the first translation, category and tag pages included in the site scan.

= 1.8.19 =
Your homepage translates by itself right after the setup wizard, and AI translation in the visual editor is several times faster.

= 1.8.18 =
Cache warm-up after every flush, Complianz consent kept across languages, LiteSpeed REST cache fix, page-builder box links in the visitor's language.

= 1.8.17 =
New option to keep your own category and tag slugs in every language, with 301 redirects from the translated addresses already indexed.

= 1.8.16 =
WooCommerce: translated product category and tag addresses no longer answer 404. Recommended model on every AI engine card, «Use this engine» switch, faster search in all languages.

= 1.8.15 =
Faster pages while Labs or WP-Cron translate in the background (caches cleared at most every ten minutes), no more false «AI translation failed» lines for resting engines.

= 1.8.14 =
Lighter and steadier «Translate all» on small servers (fewer database writes, retries after 502/504/524, one process at a time), new WP-CLI command, DeepL rest that survives cache purges.

= 1.8.13 =
The SEO Framework: translated pages in its sitemap, one og:locale. «Read more» links to feature pages, setup guide link, clearer engine box.

= 1.8.12 =
Internal links follow translated slugs; «Translate» in the Simple view starts translating; percentages reach 100% when everything visible is translated.

= 1.8.11 =
Only what visitors see counts: no more admin-only or stale sentences in the percentages.

= 1.8.10 =
Search suggestions answer in a fraction of the time (light endpoint, REST fallback).

= 1.8.10 =
Search suggestions answer in a fraction of the time (light endpoint, REST fallback).

= 1.8.9 =
Editor and imports now save on SQLite and in the wordpress.org Live Preview; the search box in block-theme menus; language names readable in the phone menu; search and Save-bar fixes.

= 1.8.8 =
Simple/Advanced view, the Search screen with profiles and looks, sentences an engine cannot translate kept (pages reach 100%), cookie-banner and cache compatibility.

= 1.8.7 =
Faster admin screens and search on large sites; no more 504 from the bulk AI buttons in Translation memory and in the page editor.

= 1.8.6.1 =
Fix: no more «504 Gateway Timeout» when translating a page or a whole language on large sites.

= 1.8.6 =
Fix: offline languages and preview mode no longer send visitors into a redirect loop — please update. Also: one «Translate with» menu with free engines in green, visits per language, content and menus per language.

= 1.8.5 =
Security fixes (page cache, WooCommerce emails, editor panel) — please update. Also: search in every language, six new languages for the plugin, plain-words provider errors, «Scan site» beyond 1,000 pages.

= 1.8.4 =
Security update: please update. The editor's translation panel is limited to published content and administrators for removals and AI; its Save works again.

= 1.8.3 =
Labels showing who translated each page, the MyMemory e-mail box, Labs texts in the plugin's language, a tidier «Translate with» row.

= 1.8.2 =
Clear error messages with the HTTP code (no more «key refused» for timeouts), «Translate all missing» in short steps with a progress bar, a «Sentences per request» option.

= 1.8.1 =
Choose the engine (official or not) on Translations, one switcher profile for the header and one for the footer, an ⓘ on every feature, fixes to page progress.

= 1.8.0 =
New «Automatic translation» page with live progress, a free/Labs overview, a test button for every AI provider, free setup on request; many fixes found on a large real site. Recommended.

= 1.7.12 =
Redirects keep the visitor's language (Redirection and others); titles of protected posts translated in lists; 25 more plugins and 3 classic themes tested. Recommended.

= 1.7.10 =
«Latest posts» excerpts and sentences ending with a «Read more» link are now translated on every site; loading indicator in the switcher's live preview. Recommended.

= 1.7.9 =
Security hardening (translations can never carry scripts or handlers, whatever their source), pasted translations in the editor panel, sentences with a bold/italic number kept whole, clearer switcher profiles. Recommended.

= 1.7.8 =
Fixes pasted translations landing on the wrong sentence (cookie banner showing a blog post), presets in the switcher customizer and the colours of the language item in your header menu. Recommended.

= 1.7.7 =
Fixes content loaded by AJAX on translated pages: scripts stay whole (forms like SupportCandy's send again) and its links keep the visitor's language. Recommended.

= 1.7.6 =
The languages in your header menu take the colours you choose, can sit right after any menu item, and the Switcher screen shows your real header live before you save. Recommended.

= 1.7.5 =
Fixes translating in your browser without an API key (sentences with links are saved, a run always ends), and flags plus open-on-click for the languages in block themes' header menu. Recommended.

= 1.7.4 =
The language switcher in your theme's header menu, or in a spot you click on your own page; a row of languages at the bottom of pages; 40 more languages (77 in all); many popular plugins translated (WP Job Manager, Events Manager, Ninja Tables, FiboSearch, Social Chat…); a simpler dashboard. Recommended.

= 1.7.3 =
E-mails from seven contact form plugins and GiveWP in the visitor's language; form confirmation messages, map markers and GiveWP donation forms translated; dates inside sentences fixed on most themes. Recommended.

= 1.7.2 =
MetForm forms, rotating «Fancy Text», countdown labels and chat buttons of popular Elementor add-ons now translated; a «Plugin language» menu; better on phones. Recommended.

= 1.7.1 =
Invoices from PDF Invoices & Packing Slips in the customer's language; customers' names and addresses no longer collected from order e-mails; a check after every import; more plugins and markup understood. Recommended.

= 1.7.0 =
Free AI translation with your own free Cloudflare, Groq or OpenRouter account; a universal importer for plugins with no importer here, with side-by-side preview; a translation style proposed from your site. Recommended.

= 1.5.9 =
Content loaded after the page («Load more», filters), REST responses, feeds and script strings are now translated; Ninja/Fluent Forms; SEO og:locale and sitemaps; RTL; sign-up language. Recommended for every site.

= 1.5.8 =
Recommended for WooCommerce shops: e-mails sent from the dashboard are translated, variations and product names in the cart and e-mails too, search works in every language. New WP Rocket integration. Imports from Polylang and WPML bring categories, variations and ACF fields.

= 1.5.7 =
Wording of the Labs page only. Nothing else changes.

= 1.5.6 =
Imports keep your hand corrections and skip drafts and trash; pages with translate="no" on <html> are translated; better caching (Google Shopping links, NitroPack, Cloudflare). New Labs page; optional anonymous reason on deactivation.

= 1.5.5 =
Recommended if you translated your site with an older version: sentences with links or bold words show up translated in the visual editor again. Without an API key, a browser that cannot translate now explains why and offers free alternatives. The switcher preview is now the real switcher, and admin screens no longer jump.

= 1.5.4 =
TranslateRocket now works on a phone: every admin screen fits, and the translation panel under the editor is readable. The language switcher no longer covers cookie banner buttons. New: choose what the AI reuses from memory, and improve browser translations with AI.

= 1.5.3 =
Import from Falang and Sublanguage; pages no longer end up on the home page after a translation plugin is switched off; OpenAI reasoning models work; composed page titles are translated.

= 1.5.2 =
Submit buttons, pictures inside <picture>, video posters and retina images are translated; an edited translation shows immediately; visitors arriving with tracking parameters read from the cache.

= 1.5.1 =
Switching from qTranslate, WPGlobus or WP Multilang no longer leaves every language on every page, and imported sentences with links are used everywhere. Recommended if you are moving from another translation plugin.

= 1.5.0 =
Sentences broken by a link or a bold word are now translated whole, so the words can move where your language needs them. Your existing translations stay, but the count of phrases to translate will go up: the whole sentences are new. A new panel tells you where your site is and what is left to do.

= 1.4.6 =
Brand and product names in "Words & phrases" now stay as they are inside sentences too, with DeepL, Google Cloud and the AI models.

= 1.4.5 =
A page edited in the block editor, a product renamed through the store API or a footer edited in the Site Editor now reaches visitors at once, instead of up to six hours later.

= 1.4.4 =
The two links at the bottom of a Complianz banner can be translated at last, plus two things the screens never explained: what to do with the header and footer Polylang or WPML duplicated per language, and where the text of pop-ups comes from.

= 1.4.3 =
Cookie and consent banners (Complianz, CookieYes and others) are now collected and can be clicked in the visual editor; page builders are left alone while you edit; "Translate again" for a single page, with undo; pages left behind by Polylang, WPML or Bogo are labelled.

= 1.4.2 =
Side by side, the preview is now one click away: a Preview panel on the Languages page, a Preview menu in the admin bar and a Preview link in Pages and Posts.

= 1.4.1 =
Forms in the visitor’s language wherever they are placed, Forminator e-mails in the language of the page, and side-by-side fixes: the mode no longer switches itself on over a site TranslateRocket is already serving.

= 1.4.0 =
Side-by-side mode: activate TranslateRocket next to WPML, Polylang, TranslatePress or another translation plugin without changing your public site, preview the translations as an administrator and go online when you are ready.

= 1.2.0 =
Content and menu items for some languages only, and whole-page translation in ChatGPT or Gemini with a prompt made for your site. Existing pages and menus are unchanged until you use the new options.
