Title: TranslateSimple Author: translatesimple Published: August 23, 2026 Last modified: August 24, 2026 --- Search plugins ![](https://ps.w.org/translatesimple/assets/banner-772x250.png?rev=3662275) ![](https://ps.w.org/translatesimple/assets/icon-256x256.png?rev=3662275) # TranslateSimple By [translatesimple](https://profiles.wordpress.org/translatesimple/) [Download](https://downloads.wordpress.org/plugin/translatesimple.0.1.31.zip) * [Details](https://wordpress.org/plugins/translatesimple/#description) * [Reviews](https://wordpress.org/plugins/translatesimple/#reviews) * [Installation](https://wordpress.org/plugins/translatesimple/#installation) * [Development](https://wordpress.org/plugins/translatesimple/#developers) [Support](https://wordpress.org/support/plugin/translatesimple/) ## Description TranslateSimple scans supported public WordPress content, lets you translate it manually for free, and provides a fully managed translation service when you want to translate automatically. There is no separate service to configure. Final translations and manual edits remain in your WordPress database and continue rendering if the subscription or service is unavailable. External service disclosure: only source segments explicitly submitted by an administrator are sent to `api.translatesimple.com`, which routes them to the machine-translation provider selected by TranslateSimple: Microsoft Azure Translator or DeepL. Private pages, form submissions, orders, users, nonces and hidden fields are not sent. Acknowledged text is deleted from the service within 24 hours and unclaimed results within 30 days; raw translation payloads are excluded from service backups. Account, entitlement, usage counts and operational metadata are retained as described in the privacy policy. Service terms: https://translatesimple.com/terms/ Privacy policy: https://translatesimple. com/privacy/ Support: https://translatesimple.com/support/ DeepL privacy: https:// www.deepl.com/privacy Microsoft privacy: https://privacy.microsoft.com/privacystatement Microsoft Azure legal terms: https://azure.microsoft.com/support/legal/ ## Screenshots [⌊Complete the guided three-step setup: choose languages, scan the site and connect an existing TranslateSimple account.⌉⌊Complete the guided three-step setup: choose languages, scan the site and connect an existing TranslateSimple account.⌉[ Complete the guided three-step setup: choose languages, scan the site and connect an existing TranslateSimple account. [⌊Review every detected segment, edit a translation manually, protect it and retranslate or restore one block when needed.⌉⌊Review every detected segment, edit a translation manually, protect it and retranslate or restore one block when needed.⌉[ Review every detected segment, edit a translation manually, protect it and retranslate or restore one block when needed. [⌊Serve translated public pages with localized navigation and the integrated language selector.⌉⌊Serve translated public pages with localized navigation and the integrated language selector.⌉[ Serve translated public pages with localized navigation and the integrated language selector. ## Installation 1. Install and activate TranslateSimple. 2. Open TranslateSimple in WordPress admin. 3. Choose source and target languages and scan supported content. 4. Edit manually, or connect your TranslateSimple account to use machine translation. ## FAQ ### Where does the language switcher appear? By default, TranslateSimple adds a compact language selector to the site’s existing navigation. It works with block-theme navigation and classic menus, including their mobile menu. Site editors can place [translatesimple_switcher] manually when they need theme-specific positioning. The selector inherits the theme text colour. Its active colour, active text, background and border can be customized with the CSS variables prefixed by –translatesimple- switcher-. ### Which languages are supported? TranslateSimple supports 33 common source and target languages through its managed translation service. The picker highlights English, Spanish, French, German, Portuguese, Italian, Dutch, Japanese, Simplified Chinese, Arabic, Polish and Russian, with 21 additional European and Asian languages available under “More languages”. Standard sites can select up to three targets; Premium sites can use every supported target language. ### Do I need to configure a separate translation service? No. TranslateSimple is fully managed. Connect your TranslateSimple account, choose your languages and start the translation from WordPress. TranslateSimple runs and maintains the service for you. ### What happens if I stop paying? Existing translations, manual editing, export and security/compatibility updates continue. New hosted machine translations require an active entitlement or remaining trial quota. ### Does TranslateSimple translate private data? No. TranslateSimple scans published public content types, public taxonomy terms, configured widget text and supported form/builder display settings. It never scans form submissions, orders, users, cookies, nonces or hidden credentials. ### Does it translate every WordPress plugin automatically? No multilingual plugin can honestly guarantee 100% coverage on every WordPress site. TranslateSimple supports registered static blocks and safe Gutenberg content metadata automatically, plus explicit integrations for popular builders, commerce and forms. The scan reports unsupported stored blocks before translation. Compatibility support evolves with WordPress, and customers can request a theme, builder or form review through the support page. ## Reviews There are no reviews for this plugin. ## Contributors & Developers “TranslateSimple” is open source software. The following people have contributed to this plugin. Contributors * [ translatesimple ](https://profiles.wordpress.org/translatesimple/) [Translate “TranslateSimple” into your language.](https://translate.wordpress.org/projects/wp-plugins/translatesimple) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/translatesimple/), check out the [SVN repository](https://plugins.svn.wordpress.org/translatesimple/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/translatesimple/) by [RSS](https://plugins.trac.wordpress.org/log/translatesimple/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 0.1.31 * Make target-language selection follow Free, Standard and Premium plan entitlements. #### 0.1.30 * Let controlled showcase sites raise the target-language selector limit without changing the historical two-language default. #### 0.1.29 * Add server-side workspace pagination, translation status filters and a page-level content map. #### 0.1.28 * Close public language menus when clicking outside them or pressing Escape. #### 0.1.27 * Use the public stylesheet content hash for reliable cache invalidation. #### 0.1.26 * Reduce the public language selector to a balanced 52 by 36 pixel control. #### 0.1.25 * Match the public language selector to the clean TranslateSimple menu without duplicated locale codes or a text arrow. #### 0.1.24 * Keep the expanded six-language selector visible inside mobile block-navigation menus. #### 0.1.23 * Keep links authored inside translated content on the active localized route. * Preserve email addresses and URLs exactly instead of sending them for translation. * Estimate only pending content, enforce the available quota before bulk translation and avoid retranslating current or protected segments. * Refresh scan onboarding immediately and safely install WordPress language packs from REST requests. * Register localized routes immediately when languages are saved on a previously unconfigured site. #### 0.1.22 * Escape stored translations at every plain-text and HTML-attribute rendering boundary. * Add regression coverage for malicious translations imported or written directly to the database. #### 0.1.21 * Detect the visitor language and localize the landing page in English, French, Spanish, Italian, Portuguese and German. * Add a compact remembered language selector and serve localized accessibility metadata. * Show each non-English visitor an example from their local language into English; keep English to Spanish for English visitors. #### 0.1.20 * Put support for 33 languages in the primary landing-page promise without adding another hero row. * Refresh the portal asset version so the compact language badge renders correctly for returning visitors. #### 0.1.19 * Present automatic translation as a fully managed TranslateSimple service across the landing page, customer portal and WordPress onboarding. * Remove infrastructure and credential jargon from the customer journey while retaining required external-service disclosures. * Introduce the aligned-lines brand mark across the customer portal and WordPress workspace. #### 0.1.18 * Expand source and target selection from three to 33 common languages supported by the managed translation service. * Keep the twelve most-used choices visible and place 21 additional languages in a compact expandable picker. * Map canonical English, Portuguese and Chinese codes to service-specific and native WordPress locales. #### 0.1.17 * Cover fifteen representative WordPress site profiles with a browser crawler that scrolls every source and translated route. * Resolve translated static fronts, posts indexes and archives without dropping the locale during canonical redirects. * Keep the integrated selector available on translated home, blog, search and archive routes. * Prevent stale Elementor source markup and render WooCommerce product descriptions and excerpts from the local translation catalogue. * Install available official language packs for active plugins and themes when languages are saved. * Reject leaked source text, formatting markers, encoded HTML, missing selectors, 404 pages and browser errors in the compatibility matrix. #### 0.1.16 * Keep the integrated language selector on translated home, category, author and date archive routes. * Resolve localized author/date archives and preserve their corresponding URL when switching languages. * Discover and translate classic navigation-widget headings used in theme footers. * Exercise literal FR/ES home, category and author routes in the public browser smoke suite. #### 0.1.15 * Reload native WordPress interface strings in the selected public language and install missing official core language packs when languages are saved. * Keep the integrated language selector available on translated home, blog and archive routes. * Cover translated comment forms and localized home navigation in the public browser smoke suite. #### 0.1.14 * Normalize allow-listed encoded formatting on source-language and untranslated fallback routes. * Hide revoked WordPress connections from the customer portal while preserving account history. * Expand deterministic smoke and browser journeys across support, password devices, billing, exports, disconnect, deletion and outage paths. #### 0.1.13 * Translate document titles, media-library alt text, rendered image attributes and generated internal links. * Translate legacy Custom HTML widget attributes and SureForms default field labels and submit buttons. * Restore allow-listed Spectra encoded formatting as safe HTML without leaking encoded markup. * Expand the integration fixtures and realistic showcase audit for these rendering paths. #### 0.1.12 * Replace separate Gutenberg allowlists with one extensible declarative registry. * Auto-detect safe static content and display fields from registered block metadata. * Support nested wildcard attribute paths and safe rendered HTML attributes. * Report metadata-backed coverage while excluding raw code, URLs and secret-like settings. * Expand the customer landing page with product workflow, ownership and honest coverage guidance. #### 0.1.11 * Make target languages react to the selected source language and simplify the language picker. * Keep protected formatting markers invisible while editors change only the readable text. * Report unexpected service redirects clearly instead of showing a generic invalid- response error. #### 0.1.10 * Translate current Spectra content/button blocks and SureForms field labels, placeholders, help text and custom buttons. * Preserve encoded inline formatting in dynamic block attributes. * Use the proxy-compatible site-pairing collection endpoint without following sensitive API redirects. #### 0.1.9 * Add a three-step WordPress onboarding checklist with one clear next action. * Explain how existing paid customers connect and approve their site without an API key. * Add WordPress.org directory screenshots for setup, block editing and the translated visitor experience. #### 0.1.8 * Add guided post-payment WordPress connection and verified-device password sign- in to the hosted portal. #### 0.1.7 * Unify customer-facing, publisher and service branding under TranslateSimple. #### 0.1.6 * Publish the service terms, privacy notice and support route referenced by the WordPress.org listing. #### 0.1.5 * Discover public custom post types and taxonomies, including WooCommerce products, categories, tags and attributes. * Switch the native WordPress locale on translated routes so core and plugin language packs render system text. * Translate supported Elementor, ACF, legacy/block widget, Contact Form 7, WPForms and Gravity Forms display fields. * Preserve translated WooCommerce product names in cart, checkout and stored-language order items. * Show detected content types, taxonomies and compatibility adapters in the scan report. #### 0.1.4 * Translate page-list and navigation-link labels from block themes. * Keep internal menu, site-title and logo links inside the selected language. * Scan navigation labels stored in block templates, template parts and patterns. * Translate static text and image alternatives stored in active-theme templates and patterns. #### 0.1.3 * Integrate the automatic language selector into block-theme and classic navigation menus. * Add lightweight CSS variables for theme-specific styling. #### 0.1.2 * Place the automatic language switcher above the site header without overlaying theme controls. * Keep a footer fallback for themes that do not expose the standard body-open hook. #### 0.1.1 * Add Microsoft Azure Translator support to the hosted service. * Clarify the machine-translation provider disclosure. #### 0.1.0 * Initial private-pilot release. ## Meta * Version **0.1.31** * Last updated **1 hour ago** * Active installations **Fewer than 10** * WordPress version ** 6.9 or higher ** * Tested up to **7.1** * PHP version ** 8.1 or higher ** * Tags * [language](https://wordpress.org/plugins/tags/language/)[localization](https://wordpress.org/plugins/tags/localization/) [multilingual](https://wordpress.org/plugins/tags/multilingual/)[translation](https://wordpress.org/plugins/tags/translation/) * [Advanced View](https://wordpress.org/plugins/translatesimple/advanced/) ## Ratings No reviews have been submitted yet. [Your review](https://wordpress.org/support/plugin/translatesimple/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/translatesimple/reviews/) ## Contributors * [ translatesimple ](https://profiles.wordpress.org/translatesimple/) ## Support Got something to say? Need help? [View support forum](https://wordpress.org/support/plugin/translatesimple/)