TranslateRocket translates the page your site actually sends to the browser, after your theme, your page builder and your other plugins have done their work. That is why it is not tied to a particular theme or builder: if it ends up in the HTML, it can be translated.
“Tested” on this page means something precise: the plugin was installed on a real WordPress site next to TranslateRocket, configured the way people use it, and checked from the visitor’s side — the translated page, the form that was sent, the e-mail that arrived. Every row has a date. What the code is prepared for but I have not seen running yet is listed separately, and says so.
Page builders and editors
| Plugin | What was checked | Last tested |
|---|---|---|
| Elementor | Pages built with Elementor are translated with the markup intact. While you work in the Elementor editor, TranslateRocket stays out of it: nothing is collected, nothing is translated, no language switcher on the canvas. | Sep 2026 · v1.4.3 |
| Elementor Pro | Theme Builder headers and footers translated on the front end; the “Edit Header” and “Edit Section” handles of the editor are never picked up as text to translate. Checked on a copy of a production site. | Sep 2026 · v1.4.3 |
| Block editor (Gutenberg) | Block themes and classic themes, including the language switcher block. | Sep 2026 · v1.4.3 |
| Astra + Spectra | A complete production site: more than 3,500 strings, right-to-left included. | In production since Jul 2026 |
WooCommerce
| Plugin | What was checked | Last tested |
|---|---|---|
| WooCommerce | Product pages, categories and attributes; the AJAX mini-cart; cart and checkout, both classic and block-based; the “Order received” page; order e-mails sent in the language the customer ordered in. | Sep 2026 · v1.3.0 |
Forms
| Plugin | What was checked | Last tested |
|---|---|---|
| Forminator | Labels, placeholders and buttons; validation and “thank you” messages; forms loaded with AJAX; notification e-mails in the language of the page; one form for every language, so all submissions stay in one place. 88 automated checks. | Sep 2026 · v1.4.3 |
| Contact Form 7 | Fields and the messages the plugin adds with JavaScript after sending. | Sep 2026 · v1.4.1 |
| WPForms | Fields and the messages added with JavaScript. | Sep 2026 · v1.4.1 |
The message patterns of Gravity Forms, SureForms, Formidable and Ninja Forms are built in as well; I have not run them through the full battery yet, so tell me if one of their messages stays in the original language.
Cookie and consent banners
Most consent banners are added to the page by JavaScript, after it has loaded — which is exactly where translation plugins that only read the server’s HTML lose them. TranslateRocket collects their text when an administrator opens the page, lets you click and translate it in the visual editor, and shows it translated to visitors.
| Plugin | What was checked | Last tested |
|---|---|---|
| Complianz | Banner text collected, clickable in the visual editor, shown translated to visitors. | Sep 2026 · v1.4.3 |
| CookieYes | Same three checks. The banner builds itself the instant the page is ready; it is collected anyway. | Sep 2026 · v1.4.3 |
| GDPR Cookie Compliance (Moove) | Same three checks. | Sep 2026 · v1.4.3 |
| Cookie Notice | Same three checks. | Sep 2026 · v1.4.3 |
SEO
| Plugin | What was checked | Last tested |
|---|---|---|
| Yoast SEO | Translated titles, descriptions and social tags; no duplicate hreflang; the language sitemap appears in Yoast’s sitemap index. | Jul 2026 · v0.5 |
| Rank Math (free and Pro) | Translated titles, descriptions and social tags on a production site; no duplicate og:locale. | In production |
Caching and optimisation
Every language lives at its own address (/fr/, /de/), so a page cache keeps the languages apart by itself: a French page can never be served to a German visitor.
| Plugin | What was checked | Last tested |
|---|---|---|
| Cache Enabler | Cached translated pages always served in the right language; the original never polluted by a translated copy. | Sep 2026 · v1.4.3 |
| Autoptimize | HTML, CSS and JavaScript aggregation on: the translation is applied to the optimised page. | Sep 2026 · v1.4.3 |
| Breeze + Varnish (Cloudways) | In production on this very site, in 21 languages. | In production |
| WP Fastest Cache | In production on a client site with 10 languages. | In production |
| Redis Object Cache | In production on a client site. | In production |
Other translation plugins: side by side, and import
You can activate TranslateRocket next to the translation plugin you already use: visitors keep seeing exactly the same site while you import your translations and preview them privately. Two-minute demo.
| Plugin | What was checked | Last tested |
|---|---|---|
| Polylang | Side-by-side mode, import of translations and slugs, the pages left behind are labelled and can be tidied up. 34 automated checks plus a complete switch-over scenario with Elementor and Forminator. | Sep 2026 · v1.4.3 |
| WPML | Import of translations, read from WPML’s own tables. Side-by-side mode recognises it; the complete switch-over has been run with Polylang. | Sep 2026 · v1.3.0 |
| TranslatePress | Import of the dictionary, the interface strings and the slugs, filmed start to finish on a real site. Side-by-side mode recognises it. | Sep 2026 · v1.3.0 |
| Weglot, Bogo, qTranslate X/XT, WPGlobus, WP Multilang, Multilanguage, Loco Translate | Import. Most are read straight from their tables or files, so it works even after the other plugin has been removed. CSV and TMX cover everything else. | Sep 2026 · v1.3.0 |
Built to stay out of their way (not run here yet)
When one of these builders loads a page to edit or preview it, TranslateRocket recognises the request and leaves the page exactly as the builder expects it: Beaver Builder, Divi, Bricks, Oxygen, Breakdance, Brizy, WPBakery, Visual Composer, Thrive Architect, SiteOrigin, Zion, Themify, Avada and the WordPress Customizer. The pages they produce are ordinary HTML, so they translate like any other page. I have read their code, not run them: if something is off, write to me and it becomes a test.
Not tested yet: LiteSpeed Cache, WP Rocket, W3 Total Cache (they should behave like the page caches above, for the same reason), and WordPress multisite.
Known limits
- Languages live in subdirectories (
/fr/,/de/). A separate domain or subdomain per language is not supported. - Multi-currency is out of scope: TranslateRocket translates, it does not convert prices.
- The translator built into Chrome and Edge needs a desktop computer (Windows 10 or 11, macOS 13+, Linux or ChromeOS). On a phone you can still do everything else, or use your own AI key.
- New text is discovered when an administrator opens the page, or with the Scan button — not while anonymous visitors browse.
Your plugin is not on the list?
It probably works: the list only shows what I have seen with my own eyes. If something does not behave, tell me which plugin and what you see — a screenshot is perfect. Reports like that are how the cookie banners and the Elementor editor ended up on this page.
