Title: TranslateSimple Author: translatesimple Published: 23 de agosto de 2026 Last modified: 1 de septiembre de 2026 --- Buscar plugins ![](https://ps.w.org/translatesimple/assets/banner-772x250.png?rev=3662275) ![](https://ps.w.org/translatesimple/assets/icon-256x256.png?rev=3662275) # TranslateSimple Por [translatesimple](https://profiles.wordpress.org/translatesimple/) [Descargar](https://downloads.wordpress.org/plugin/translatesimple.0.1.36.zip) * [Detalles](https://es.wordpress.org/plugins/translatesimple/#description) * [Valoraciones](https://es.wordpress.org/plugins/translatesimple/#reviews) * [Instalación](https://es.wordpress.org/plugins/translatesimple/#installation) * [Desarrollo](https://es.wordpress.org/plugins/translatesimple/#developers) [Soporte](https://wordpress.org/support/plugin/translatesimple/) ## Descripción 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: for machine translation, 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/ ## Capturas [⌊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. ## Bloques Este plugin proporciona 1 bloque. * Language switcher ## Instalación 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. 5. Review each language, then publish it when it is ready for visitors. ## 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. Open TranslateSimple > Language switcher to choose placement, native or custom appearance, language labels and separate desktop/mobile layouts. Preview changes privately before applying them, and restore a previous design from the history. You can also insert the Language switcher block. Theme-specific menus may require manual placement; support for every theme or builder is not guaranteed. Optional visual review is disabled on the hosted service until separately enabled. Where available, it requires explicit administrator consent before public header/ menu screenshots and layout measurements are sent through TranslateSimple to OpenAI. It proposes appearance settings only; changes are never applied automatically. Manual design does not require this service. OpenAI privacy: https://openai.com/policies/ privacy-policy/ ### Can I review translations before visitors see them? Yes. New sites keep translated languages in draft by default. Each complete language must be selected explicitly before it can go live. The global publication control can also hide every translated route, selector, sitemap entry and hreflang link without deleting translations or protected manual edits. Re-enable publication whenever the review is complete. ### 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; Agency 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. ### Does it work with Elementor, WooCommerce, Yoast and Rank Math? TranslateSimple has pinned real-plugin coverage for Elementor core and WooCommerce. It translates supported product, variation, taxonomy, attribute and common Elementor display fields while leaving prices, stock, IDs, URLs and layout configuration untouched. Common Elementor Pro display fields use the same structural adapter, but a clone with the site’s licensed Pro widgets must be tested before production. Literal Yoast and Rank Math SEO titles, descriptions and social title/description copy for posts and products are independently translatable. Rank Math taxonomy SEO copy is also supported. Replace-variable templates remain untouched. Canonical URLs, robots directives, schema settings and social image URLs remain configuration and are not sent for translation. ### Can translated slugs be edited? Not currently. TranslateSimple keeps the source path and adds a language prefix, for example `/es/source-page/`. It localizes generated and internal links, canonical metadata, hreflang and its sitemap around that stable path. ### Can I migrate directly from another multilingual plugin? There is no automatic importer yet. TranslateSimple prevents competing public routing while WPML, Polylang, Weglot or TranslatePress is active. Existing sites should be assessed on a clone, retain an export and database backup, and prepare redirects from old translated URLs before any cutover. ## Reseñas No hay valoraciones para este plugin. ## Colaboradores y desarrolladores «TranslateSimple» es un software de código abierto. Las siguientes personas han colaborado con este plugin. Colaboradores * [ translatesimple ](https://profiles.wordpress.org/translatesimple/) [Traduce «TranslateSimple» a tu idioma.](https://translate.wordpress.org/projects/wp-plugins/translatesimple) ### ¿Interesado en el desarrollo? [Revisa el código](https://plugins.trac.wordpress.org/browser/translatesimple/) , echa un vistazo al [repositorio SVN](https://plugins.svn.wordpress.org/translatesimple/) o suscríbete al [registro de desarrollo](https://plugins.trac.wordpress.org/log/translatesimple/) por [RSS](https://plugins.trac.wordpress.org/log/translatesimple/?limit=100&mode=stop_on_copy&format=rss). ## Registro de cambios #### 0.1.36 * Preserve paired link and inline-formatting structure when sending scanned content to the translation service. Original HTML attributes and link destinations stay in WordPress. * Reject altered provider markup and show a manual-review warning without replacing original content. * Retain compatibility with existing translations and older clients. Scan again after updating to enable the improved structure for future translations. #### 0.1.35 * Fix fallback WordPress REST URLs, including query parameters on subdirectory installations. * Use WordPress’s supported POST method for manual saves on hosts that block PATCH. Keep the same authorization checks. * Keep unsaved edits and show a readable error when a server returns HTML or invalid JSON. * Disable restore when no previous translation exists and show language-publication progress. * Explain active versus archived diagnostic counts without deleting translations or history. #### 0.1.34 * Keep earlier visual reviews readable after applying or restoring another design, without allowing stale proposals to overwrite it. * Refresh the saved design preview after restoration and explain theme-inherited appearance controls. * Add clear review and translation progress states and improve mobile language- menu keyboard handling. * Harden optional visual-review capture and admission limits; hosted AI review still requires separate activation. #### 0.1.33 * Add native-theme language switcher styling and bounded per-site appearance settings. * Add private desktop/mobile previews, explicit apply, revision history and rollback. * Support selected menu, block and shortcode placement with theme-change protection. * Prepare an optional consented visual review service; disabled by default. #### 0.1.32 * Add reversible site-wide and per-language publication controls so translations can be reviewed privately. * Replace the post-connection marketing redirect with clear WordPress and account actions. * Improve agency invitation emails, confirmation states and cross-client isolation coverage. * Translate Yoast and Rank Math SEO/social copy as independent post, product and Rank Math taxonomy segments. * Purge common WordPress page caches after translation and publication changes, with a CDN integration action. * Document exact Elementor Pro, translated-slug and multilingual migration boundaries. * Refresh language setup and scan results without requiring a page reload. * Localize the WordPress administration interface in six languages. * Show translation progress, plan limits and publish the language selector only after translated content is ready. * Send account links through sign-in before opening the protected account page. #### 0.1.31 * Make target-language selection follow Free, Standard and Agency 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 * Versión **0.1.36** * Última actualización **hace 2 días** * Instalaciones activas **Menos de 10** * Versión de WordPress ** 6.9 o superior ** * Probado hasta **7.1** * Versión de PHP ** 8.1 o superior ** * Idioma * [English (US)](https://wordpress.org/plugins/translatesimple/) * Etiquetas: * [language](https://es.wordpress.org/plugins/tags/language/)[localization](https://es.wordpress.org/plugins/tags/localization/) [multilingual](https://es.wordpress.org/plugins/tags/multilingual/)[translation](https://es.wordpress.org/plugins/tags/translation/) * [Vista avanzada](https://es.wordpress.org/plugins/translatesimple/advanced/) ## Valoraciones Aún no se han enviado valoraciones. [Tu valoración](https://wordpress.org/support/plugin/translatesimple/reviews/#new-post) [Ver todas las reseñas](https://wordpress.org/support/plugin/translatesimple/reviews/) ## Colaboradores * [ translatesimple ](https://profiles.wordpress.org/translatesimple/) ## Soporte ¿Tienes algo que decir? ¿Necesitas ayuda? [Ver el foro de soporte](https://wordpress.org/support/plugin/translatesimple/)