Title: MisterTranslate – AI Translation for WordPress & WooCommerce Author: mistertranslate Published: February 18, 2026 Last modified: September 14, 2026 --- Search plugins ![](https://ps.w.org/mistertranslate/assets/banner-772x250.png?rev=3494267) ![](https://ps.w.org/mistertranslate/assets/icon-256x256.png?rev=3482173) # MisterTranslate – AI Translation for WordPress & WooCommerce By [mistertranslate](https://profiles.wordpress.org/mistertranslate/) [Download](https://downloads.wordpress.org/plugin/mistertranslate.5.3.0.zip) * [Details](https://co.wordpress.org/plugins/mistertranslate/#description) * [Reviews](https://co.wordpress.org/plugins/mistertranslate/#reviews) * [Installation](https://co.wordpress.org/plugins/mistertranslate/#installation) * [Development](https://co.wordpress.org/plugins/mistertranslate/#developers) [Support](https://wordpress.org/support/plugin/mistertranslate/) ## Description MisterTranslate translates your WordPress site with AI while keeping your pages exactly as you designed them — no rebuilding, no broken layouts, no wasted hours fixing what the translation broke. Most translation tools ignore how your content is structured and hand you broken pages. MisterTranslate works differently: it detects how each page is built and translates it segment by segment, preserving every widget, column and visual element. And instead of a yearly subscription, you simply pay for the words you translate— once. Your words never expire, and your translations live in your own WordPress, so you own them for good. **Pay per word, not per year** No subscription, no monthly fee, no per-language licence. You buy word packs (from 500 words for €1) and use them whenever you want. Words never expire. And when you stop, nothing disappears: your translated pages stay on your site because they are stored in your own database — not on someone else’s server. **Translate without breaking your design** MisterTranslate understands page builders. When you translate an Elementor page it keeps the layout, the widget structure and the visual hierarchy intact. The same applies to Avia/Enfold, Gutenberg blocks and the Classic Editor. **WooCommerce ready** Translate product titles, descriptions, short descriptions, categories and attributes. Launch your catalogue in new markets without rebuilding product pages one by one. **See the cost before you translate** The built-in estimator shows exactly how much a translation will cost before you launch it — no surprises. Your available balance is always visible inside the admin panel. **Review before you publish** You stay in control: check every translation before it goes live, and keep terminology consistent with the built-in glossary — protect brand names, keep technical terms unchanged, or define the exact translation for any phrase. **Works with your multilingual setup** MisterTranslate works alongside Polylang and WPML, linking your translated content correctly across languages. It also purges WP Rocket cache automatically after translation. #### Key Features * Translate pages, posts and custom post types from one panel * Preserve Elementor layouts with segment-based translation * Translate WooCommerce products, categories and attributes * Pay per word — no subscription, and your words never expire * Keep your translations in your own site, forever * See the exact cost before you translate * Review every translation before publishing * Keep terminology consistent with glossary rules * Process content in batches to save time * Connect translated content with Polylang and WPML * Purge WP Rocket cache after translation #### Supported Builders and Editors * Elementor * Avia / Enfold * WordPress Block Editor (Gutenberg) * Classic Editor #### Language Support 80+ languages including Spanish, English, French, German, Italian, Portuguese, Chinese, Japanese, Korean, Arabic, Russian and Hindi. #### Who Is MisterTranslate For? * **Store owners** who need to launch products in new languages fast * **Agencies** who manage multilingual client sites and need to scale without per- site subscriptions * **Site owners** who want to translate landing pages without losing their design * **Anyone** who wants professional AI translation they pay for once and own forever ### External services This plugin relies on the MisterTranslate translation service to translate your content. Translation is performed on our servers, so content and a small amount of technical data leave your site. Nothing is sent until you actively start a translation or start the free trial. Service endpoint: https://plugin.misterads.es/translate **When data is sent, and what is sent** * **Starting the free trial** (only after you tick the consent box and click the button): your site domain and URL, the email address you type, your WordPress and plugin versions, and a technical fingerprint of the site (a hash of the domain, site URL, versions and charset). Immediately afterwards our server makes a single public request back to your site to confirm the domain really is yours. * **Translating content** (only when you click Translate): the text to be translated— page or product titles, descriptions, excerpts, SEO title and meta description, and your glossary terms — plus your client ID, your site domain and a request signature. * **Checking your balance or validating credentials**: your client ID and site domain. We do not send your visitors’ personal data, and we do not track your site’s traffic. Terms of service: https://mistertranslate.com/terms-and-conditions/ Privacy policy: https://mistertranslate.com/privacy-policy/ ## Screenshots [⌊Main translation dashboard for pages, products and categories.⌉⌊Main translation dashboard for pages, products and categories.⌉[ Main translation dashboard for pages, products and categories. [⌊Select and translate content from one centralized workflow.⌉⌊Select and translate content from one centralized workflow.⌉[ Select and translate content from one centralized workflow. [⌊Elementor-aware translation designed to preserve structure and layout.⌉⌊Elementor- aware translation designed to preserve structure and layout.⌉[ Elementor-aware translation designed to preserve structure and layout. [⌊Translate WooCommerce products, categories and attributes faster.⌉⌊Translate WooCommerce products, categories and attributes faster.⌉[ Translate WooCommerce products, categories and attributes faster. [⌊Glossary controls help keep terminology and brand names consistent.⌉⌊Glossary controls help keep terminology and brand names consistent.⌉[ Glossary controls help keep terminology and brand names consistent. [⌊Estimate translation cost before processing content.⌉⌊Estimate translation cost before processing content.⌉[ Estimate translation cost before processing content. [⌊Batch translation helps save time on large multilingual projects.⌉⌊Batch translation helps save time on large multilingual projects.⌉[ Batch translation helps save time on large multilingual projects. [⌊Manage API credentials and plugin settings from the admin panel.⌉⌊Manage API credentials and plugin settings from the admin panel.⌉[ Manage API credentials and plugin settings from the admin panel. ## Installation 1. Upload the `mistertranslate` folder to `/wp-content/plugins/`, or install it from the Plugins screen in WordPress 2. Activate the plugin 3. Create your account at mistertranslate.com and copy your Client ID and Secret Key 4. Go to `MisterTranslate > Settings` and paste both keys (the connection is tested automatically) 5. Open the MisterTranslate panel, pick a page and translate ## FAQ ### How much does MisterTranslate cost? You pay per word: 500 words for €1 (plus VAT). There is no subscription and no monthly fee. You buy word packs once and your words never expire, so you only ever pay for what you actually translate. ### Do I need a subscription? No. MisterTranslate is not a subscription. You buy words when you need them and use them whenever you want — they do not expire. ### What happens to my translations if I stop paying? Nothing — they stay on your site. Your translations are saved in your own WordPress database, so you keep them permanently even if you never buy more words. You are not renting access to your own content. ### Is there a free version? Yes. When you install the plugin you can start a free trial that gives you 500 words— enough to translate a full page — without a credit card and without copying any keys by hand. After that, translating uses words, which you buy in packs starting at €1. You always see the exact cost before you translate, and your available balance is shown inside the admin panel. ### How does the free trial work? From the plugin screen you enter your email and give consent to register your site. We then check that your site is publicly reachable and grant 500 free words tied to your domain. One trial is available per domain and per email address. If you later buy a word pack using the same email, the words are added to the same account— nothing to copy or paste. ### What does MisterTranslate translate? Pages, posts, custom post types, WooCommerce products, categories and attributes. ### Does it work with Elementor? Yes. MisterTranslate detects Elementor content and translates it with a segment- based approach to preserve layout and widget structure. ### Does it support WooCommerce? Yes. It can translate product titles, descriptions, short descriptions, categories and attributes. ### Does it work with Polylang or WPML? Yes. MisterTranslate works alongside Polylang and WPML, adding AI translation to your multilingual setup and linking translations across languages. ### Can I control brand names or fixed terminology? Yes. The glossary lets you keep terms unchanged or define specific translations for any term. ### Can I estimate translation cost before starting? Yes. The plugin includes a cost estimator and shows your available balance inside the admin panel. ### Is it useful for agencies? Yes. MisterTranslate is especially useful for agencies and site managers who localise multiple pages or products, with no per-site subscription to manage or renew. ### Do I need technical knowledge to use it? No. The plugin works from a single panel inside WordPress. Select your content, choose the target language and translate. ### Does it break my page design? No. MisterTranslate is specifically built to preserve your layout. It translates content while keeping page-builder structures, widgets and visual elements intact. ### ¿Cómo traducir WordPress con IA? Instala MisterTranslate, elige el idioma de destino y selecciona las páginas o productos que quieras traducir. La IA los traduce respetando el diseño de Elementor, Gutenberg o el editor clásico, y puedes revisar cada traducción antes de publicarla. Pagas solo por las palabras que traduces, sin cuotas ni suscripción, y las palabras no caducan. ## Reviews ![](https://secure.gravatar.com/avatar/81541ba5905b8b89019da2423b1e459a926edb02931d73c63124a15ff50b914d? s=60&d=retro&r=g) ### 󠀁[Fantástico](https://wordpress.org/support/topic/fantastico-381/)󠁿 [clonica](https://profiles.wordpress.org/clonica/) March 19, 2026 Impresionante como funciona… fantástico para traducir rapidamente la web. [ Read all 2 reviews ](https://wordpress.org/support/plugin/mistertranslate/reviews/) ## Contributors & Developers “MisterTranslate – AI Translation for WordPress & WooCommerce” is open source software. The following people have contributed to this plugin. Contributors * [ mistertranslate ](https://profiles.wordpress.org/mistertranslate/) [Translate “MisterTranslate – AI Translation for WordPress & WooCommerce” into your language.](https://translate.wordpress.org/projects/wp-plugins/mistertranslate) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/mistertranslate/), check out the [SVN repository](https://plugins.svn.wordpress.org/mistertranslate/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/mistertranslate/) by [RSS](https://plugins.trac.wordpress.org/log/mistertranslate/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 5.3.0 * New: internal links inside a translated page now point at the translated pages. Link rewriting existed but only recognised absolute URLs, so a site written with links like “/contact/” — which is how most sites are written — had every internal link left pointing at the original language. Relative, protocol-relative and absolute links are all handled now, fragments are kept (“/programme/#agenda”), and the link keeps the shape the author wrote it in, so a root-relative site stays portable between environments * New: links whose target is not translated yet are left untouched and revisited automatically as the rest of the language gets translated. This is what made the old behaviour useless in practice — when you translate page by page, nothing exists to link to yet and nothing ever came back. A page waiting on a translation is re-examined only once its language has actually gained one, including when a translation left in draft is published. No page is ever given up on, and while nothing changes this costs one query and no work at all * New: sites translated with earlier versions are repaired the same way, a few pages at a time in the background, without re-translating anything * New: a setting to turn internal-link rewriting off (Settings Internal links), on by default. Turning it off and on again does not leave the pages translated in between unrepaired * Improved: links are also rewritten inside block attributes, so the block editor shows the translated target and not just the rendered page * Improved: a page translated by hand in Polylang or WPML now counts as a link target. Previously only translations this plugin had made itself were recognised * Improved: WooCommerce product descriptions get their internal links rewritten too * Only a link to a page a visitor can actually open is ever rewritten: a translation still in draft is left alone until it is published, and external links, anchors, mailto:, tel:, query strings, files, feeds and paginated URLs are never touched * Internal: the three near-identical copies of the link rewriter in the Gutenberg, Standard and Elementor builders were replaced by one shared implementation, so they cannot drift apart again. The link pass runs once, after the translated content is saved, and writes the one column it needs to — it does not touch the modified date, store a revision, or run published content through the editor’s HTML filter #### 5.2.4 * Fix (data loss): when the target language cannot be assigned in Polylang — which happens for a language added moments earlier, while Polylang’s language list is still cached — the translation is no longer linked at all, and the original’s existing translations are left untouched. Previously Polylang was handed a group containing an unusable entry and responded by clearing the group, silently unlinking every language already attached to that page. For pages a warning now appears in the results list telling you to set the language by hand on that one post; WooCommerce products and product categories and tags get the same protection, recorded in the debug log rather than on screen * Fix (data loss): linking a translation now merges both posts’ existing translation groups, so a language already attached to either side can never be dropped * Fix (data loss): re-translating with “replace” moves the previous translation to the trash instead of deleting it outright, so a translation edited by hand can be recovered. Trashed translations no longer appear in the Outdated list, and a trashed page is no longer offered as the parent of a new child translation * Fix: the hash used to decide whether a translation is out of date was computed over the extracted text when stored and over the raw source when compared, so the two could not match and every translation looked out of date from the moment it was made. Both now go through one shared function. This applies from 5.2.4 onward: translations created before this update keep their old hash and will keep showing as outdated until each has been re-translated once * Fix: “Re-translate” on an outdated translation works again — it called an API method that was removed in 5.0 and failed every time. It now updates the existing translation in place, so the post keeps its ID, slug, language, translation group and every link pointing at it, instead of being recreated. Its SEO fields are re-derived from the original rather than from the previous translation, and nothing at all is written unless the whole translation came back complete * Fix: a regional target language is only matched to a regional sibling when there is exactly one — with both es-MX and es-AR installed the page is left unlinked, with a warning, rather than filed under the wrong country * Internal: a dormant code path in the Elementor builder still called the API method removed in 5.0. It has been rewritten onto the current segment API. No Elementor site was affected, because nothing called it #### 5.2.3 * Fix: the requested language variant now reaches every translation. The European- Portuguese instruction only went out with page translations, so a product description or a category name sent to “pt” could still come back in Brazilian Portuguese. It is now attached to pages, products and taxonomy terms alike — taxonomy terms previously carried no glossary instructions at all * Fix: language codes are normalised, so pt_PT, pt-PT and PT resolve to the same instruction instead of silently falling back to none. An unknown regional code falls back to its base language, so pt-AO and pt-MZ get the European Portuguese instruction * New: regional language variants are selectable — Português (Brasil), Español ( España/Latinoamérica/México/Argentina), English (UK/US), Français (France/Canada), Deutsch (Deutschland/Österreich/Schweiz), Nederlands (Nederland/België) and 简体/ 繁體 Chinese. Picking one your multilingual plugin does not have falls back to the closest language it does have, instead of leaving the translation unassigned * Fix: a regional code now uses its base language’s word-count ratio in the cost estimate instead of the global average, which was under-estimating Chinese by about a fifth * Note on bare codes: “pt” continues to mean European Portuguese, as it has since 5.1.7. “zh” means Simplified Chinese, and “nb”/”nn” mean Bokmål/Nynorsk, because those codes each name one written standard. “es”, “fr”, “de”, “nl” and “ca” are left to the engine’s own judgement, because the same code is used by sites that want different standards — choose the regional variant when you want one enforced.“ en” only asks for internally consistent spelling #### 5.2.2 * Fix: Custom HTML blocks are now translated. Text inside a Custom HTML block (` core/html`) was skipped entirely, so any page built with them was only partly translated — on one real site that was 37% of the copy. The text is now translated while tags, attributes, scripts, styles and HTML comments are left untouched #### 5.2.1 * Fix: translated products now really get the translated categories. The language was assigned to the new product _after_ its categories were copied, and Polylang filters term assignment by the post language, so the translated terms were silently reverted to the source language. The language is now set first #### 5.2.0 * New: in-plugin free trial. New sites can get 500 free words — enough for a full page — without a credit card and without copying any credentials by hand. One trial per registrable domain (subdomains included) and per email address; your site is verified as publicly reachable before words are granted. **Disabled by default**: it shows nothing and calls nothing until it is switched on, so this update is safe to apply on every site * New: the readme now documents the external translation service — what data is sent, when, and links to the terms and privacy policy * Clearer WordPress.org listing: keyword-led title, rewritten description and a new FAQ making the model explicit (pay per word, no subscription, words never expire, translations stay in your own site, works with Polylang/WPML) #### 5.1.9 * Fix: translated products are now assigned the translated product categories, tags and attribute terms instead of the source-language ones. Previously a translated product stayed in the original categories, so its permalink and breadcrumbs kept the source language (e.g. /tienda/personalizados/alfombrilla/ on a German product). Terms that have no translation yet are kept, so products are never left uncategorised #### 5.1.8 * Fix: translating WooCommerce products no longer fails. The product handler called get_button_text() on every product, but that method only exists on external/affiliate products, so any simple or variable product raised “Call to undefined method” and the translation aborted before any words were consumed. Affected every 5.1. x release #### 5.1.7 * Fix: Elementor HTML widgets that mix a block (or heavy CSS) with real text — such as styled specification tables — are now translated. Previously any HTML widget containing a block or more than 2 CSS declarations was skipped entirely, leaving those tables untranslated. The / blocks are now shielded with placeholders so the surrounding text is translated without corrupting the code * Fix: translated child pages are now placed under the translated parent page, keeping a matching-language URL hierarchy (e.g. /pt/produtos/… instead of /pt/ productos/…). Falls back to the source parent when it has no translation yet * Portuguese (pt): a European-Portuguese instruction is added to the translation prompt * Fix: button icons on the settings screens now always follow their button color( orange/red), even when another plugin or theme styles WordPress dashicons directly * New: “Translate SEO metadata” setting (enabled by default) controls whether SEO title and meta description (Yoast, Rank Math, AIOSEO, SEOPress) are translated * New: automatic SEO-meta repair. If translating the SEO metas fails (e.g. rate limit during bulk translation) the page is marked and retried automatically; pages translated with old plugin versions whose SEO metas are verbatim copies of the source are detected and re-translated in the background (max 3 pages every 10 minutes) * New: automatic collective healing. When an original page with translations is trashed or deleted, one of its live translations (preferring the default language) is automatically promoted to original and the remaining translations are re-linked to it * New: automatic orphan sweep. On each admin visit (throttled), any translation whose original is missing or trashed gets its collective healed automatically * New: base pages follow the default language. When Polylang is active, the front page, posts page and WooCommerce base pages (shop, cart, checkout, my account, terms) are automatically switched to their default-language version when a published translation exists (WooCommerce pages are only switched if the target actually contains WooCommerce content) * Settings: after saving your Client ID and Secret Key, the connection is now tested automatically and the result is shown, without having to click “Test Connection” * Low balance alerts are now measured in WORDS instead of tokens: you set the threshold in words (default: 500) and are alerted when your minimum available words drop below it. Existing token thresholds are migrated automatically * Settings: the credential-management and refresh buttons now use the brand orange color and their icons are properly centered * Fix: the language suffix on translated slugs is now preserved by all builders( Standard, Gutenberg and Avia were overwriting it when saving the translated title; only Elementor kept it) * Fix: legacy SEO-meta translation path now consumes the API response correctly * Minor admin UI polish for a more consistent look #### 5.1.5 * Inline HTML protection: bold, italic and other inline tags are now shielded from the AI with placeholders and restored afterwards, so formatting like **500 words** is preserved exactly instead of leaking across the whole sentence * Internal link rewriting: links inside translated pages (Elementor, Gutenberg and Classic content) now point to the translated version of the target page in the same language, instead of sending visitors back to the original-language page * SEO metadata is now translated (not just copied): SEO title and meta description for Yoast SEO, Rank Math, All in One SEO and SEOPress are sent for translation on the translated page * Automatic retry: transient API failures and rate-limit responses are now retried automatically instead of failing the translation * Empty-body pages: pages with no translatable body (such as the WooCommerce Shop page or index pages) now translate the title and are created correctly instead of being skipped * Duplicate protection: translating a page that already has a translation now detects the existing one and offers Duplicate / Replace / Cancel, preventing accidental duplicated translations * Slug collisions: translated pages append the language code to the slug to avoid clashes between languages * Elementor: raw HTML widgets (containing , or < iframe> code) are detected and left untouched to avoid corrupting embedded code * Progress bar: the translation modal now shows an animated progress indicator while work is in progress #### 5.1.4 * Fix Standard (Classic Editor) builder: apply wpautop() before regex extraction so plain-text paragraphs separated by blank lines get a < p> wrapper the extractor can capture. Without this fix, every Classic Editor page with non-tagged paragraphs (typical for legal pages, privacy policy, etc.) was being copied verbatim untranslated. #### 5.1.3 * Enfold: extend the fullsize-container CSS patch to also reset the inner .container padding-left and padding-right to 0. Without this, the hero content kept a residual 20-50px lateral padding on the translated front page that the original home does not have #### 5.1.2 * Fix front page resolver: Polylang Free filters option_page_on_front and returns the translated post ID directly. The previous check compared the result against the option value and aborted when they matched, leaving the translated front- page handler inactive. Now trusts pll_get_post() unconditionally * Without this fix v5.1.0 / v5.1.1 worked only when site_url was visited but the front-page template overrides did not apply on the translated URL #### 5.1.1 * Suppress WordPress canonical redirect on /xx/ when serving the translated front page (was rewriting /xx/ to /xx/{slug}/ and bypassing front-page template) * Rewrite the permalink of the translated front page back to /xx/ so canonical links, menus and schema stay consistent * Fixes Polylang Free home rendering on themes with permalink-based canonicalization #### 5.1.0 * Added Polylang Free compatibility for the translated front page: visiting /xx/ now serves the translated page through the active theme’s front-page template * Universal page-resolution layer (parse_query + template_include + body_class) works on any theme * Optional CSS patches for recognised themes (Astra, Enfold, Avada, Divi, GeneratePress) to hide breadcrumbs/title bars that are not present on the homepage template * Unknown themes keep their default rendering untouched: no breaking changes * Module activates only when Polylang is detected, current language is not the site default, and a translation of the front page exists #### 5.0.1 * Improved plugin listing: updated description, tags and FAQ for WordPress.org * Enhanced admin UX: dynamic version display, clearer empty-state messages * Added review prompt after successful translations * Updated plugin header description #### 5.0.0 * New extensible builder architecture: all content extraction now happens in the plugin * Added Builder Registry with priority-based detection (Elementor, Avia, Gutenberg, Standard) * Avia/Enfold builder: full shortcode-aware translation preserving layout, timeline, iconlist and all visual elements * Gutenberg block parser: translates block content while preserving block structure * Standard builder: template-based extraction with placeholder system * Server simplified to pure translation endpoint (receives text segments, returns translations) * Adding a new builder requires only 1 PHP file with no changes to existing code * Improved segment numbering to prevent merging of short text segments * Fixed shortcode attribute protection to prevent translating technical values #### 4.2.1 * Improved Elementor translation with segment-based approach * Added smart detection for third-party Elementor addon fields * Added FontAwesome icon filtering to reduce unnecessary token usage * Added CSS value protection for gradients, transforms and other visual values * Added Elementor meta safety checks for edit mode, template type and version * Added WP Rocket cache purge integration * Improved WordPress coding standards compliance #### 4.2.0 * Added batch translation support * Added translation cost estimator * Added glossary management * Added Polylang and WPML integration * Added low balance notifications ## Meta * Version **5.3.0** * Last updated **2 weeks ago** * Active installations **Fewer than 10** * WordPress version ** 5.0 or higher ** * Tested up to **6.9.9** * PHP version ** 7.0 or higher ** * Language * [English (US)](https://wordpress.org/plugins/mistertranslate/) * Tags * [elementor](https://co.wordpress.org/plugins/tags/elementor/)[multilingual](https://co.wordpress.org/plugins/tags/multilingual/) [translate](https://co.wordpress.org/plugins/tags/translate/)[translation](https://co.wordpress.org/plugins/tags/translation/) [woocommerce](https://co.wordpress.org/plugins/tags/woocommerce/) * [Advanced View](https://co.wordpress.org/plugins/mistertranslate/advanced/) ## Ratings 5 out of 5 stars. * [ 1 5-star review ](https://wordpress.org/support/plugin/mistertranslate/reviews/?filter=5) * [ 0 4-star reviews ](https://wordpress.org/support/plugin/mistertranslate/reviews/?filter=4) * [ 0 3-star reviews ](https://wordpress.org/support/plugin/mistertranslate/reviews/?filter=3) * [ 0 2-star reviews ](https://wordpress.org/support/plugin/mistertranslate/reviews/?filter=2) * [ 0 1-star reviews ](https://wordpress.org/support/plugin/mistertranslate/reviews/?filter=1) [Your review](https://wordpress.org/support/plugin/mistertranslate/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/mistertranslate/reviews/) ## Contributors * [ mistertranslate ](https://profiles.wordpress.org/mistertranslate/) ## Support Got something to say? Need help? [View support forum](https://wordpress.org/support/plugin/mistertranslate/)