simogol

<p>Polyglot helps administrators run controlled translation jobs from Tools > Polyglot for:</p>
<ul>
<li>Polylang String Translations</li>
<li>Pages, Posts, and public Custom Post Types (CPTs)</li>
</ul>
<p>The plugin is designed for safe, incremental translation workflows and does not create missing translated posts.</p>
<p>Polyglot is built for projects that use WordPress as a CMS with a clear separation between content and presentation (for example, headless WordPress setups). It is not recommended for page-builder-heavy workflows (such as Elementor) where content and presentation are tightly coupled.</p>
<h4>Configuration</h4>
<ul>
<li>Save Google API key in WordPress admin</li>
<li>API key is stored encrypted in WordPress options</li>
<li>Tabs are locked until an API key is configured</li>
</ul>
<h4>Translation Strings tab</h4>
<ul>
<li>Select Polylang string group</li>
<li>Select source and target languages</li>
<li>Translate only missing target-language string values</li>
<li>Background queue processing with live progress</li>
</ul>
<h4>Pages, Posts and CPT tab</h4>
<ul>
<li>Select one content type (page, post, or one public CPT)</li>
<li>Select source and target languages</li>
<li>Choose translation scope:
<ul>
<li>default content only (title, content, excerpt)</li>
<li>default content + custom fields</li>
</ul>
</li>
<li>Custom field mode includes:
<ul>
<li>inline preview of custom field names that Polyglot will attempt to translate</li>
<li>explicit risk acknowledgment checkbox before job start</li>
</ul>
</li>
</ul>
<h4>Translation rules</h4>
<p>For each eligible source/target pair, a field is translated only when:</p>
<ul>
<li>target value equals source value, or</li>
<li>source value is non-empty and target value is empty.</li>
</ul>
<p>If target has different non-empty content, it is treated as edited and skipped.</p>
<h4>Custom field safety</h4>
<p>When custom-field translation is enabled, Polyglot auto-detects non-protected meta keys and applies safeguards:</p>
<ul>
<li>skips protected/internal keys</li>
<li>skips technical key patterns (for example id, slug, token, url, hash)</li>
<li>skips values that look serialized/JSON/URL/numeric/token-like</li>
<li>supports exclusion hook: <code>polyglot_excluded_meta_keys</code></li>
</ul>
<p>Default excluded keys currently include:</p>
<ul>
<li>item_author</li>
</ul>
<h4>Job processing and progress</h4>
<ul>
<li>Jobs run in background batches using WP-Cron</li>
<li>Progress view includes status, remaining, scanned, translatable, translated, skipped, failed, and last error</li>
<li>If no eligible fields are found, Polyglot shows a success notice and does not start a queue</li>
</ul>
<h4>Troubleshooting failed jobs</h4>
<p>If a job ends with done_with_errors, open the Job Progress panel and review the Failure details list.<br />
Each row includes:</p>
<ul>
<li>Error category ([API], [SAVE], [OTHER])</li>
<li>Error message</li>
<li>Related identifiers (field key, language, post IDs, or string name)</li>
</ul>
<p>To inspect raw job data directly:</p>
<ul>
<li>wp option get polyglot_translation_job –format=json</li>
</ul>
<p>Key fields:</p>
<ul>
<li>status</li>
<li>last_error</li>
<li>totals.failed</li>
<li>errors[]</li>
</ul>
<p>If errors are API-related, verify:</p>
<ul>
<li>Cloud Translation API is enabled in the same Google Cloud project used by the key</li>
<li>Billing is enabled for that project</li>
<li>API key restrictions allow this WordPress instance (referrer/IP restrictions and API restriction to Cloud Translation API)</li>
</ul>
<h4>Important billing notice</h4>
<p>Google Cloud Translation API is a paid service with usage-based pricing.</p>
<ul>
<li>Large translation jobs can generate significant costs</li>
<li>Review quotas, billing settings, and pricing before running bulk jobs</li>
</ul>
<h4>Disclaimer</h4>
<p>Polyglot is provided as is, without any warranty of any kind.</p>
<ul>
<li>Use this plugin at your own risk.</li>
<li>Always create a full database and files backup before running translation jobs.</li>
<li>Translation jobs can modify content and custom fields; review your settings and previews carefully before starting.</li>
<li>The plugin author is not liable for data loss, site issues, translation quality issues, or other damages resulting from use.</li>
</ul>
<h3>External services</h3>
<p>This plugin relies on Google Cloud Translation API (Basic v2) to perform automated translations. The service is the only third-party endpoint contacted by the plugin.</p>
<p>What it is used for:</p>
<ul>
<li>Translating Polylang String Translation entries on demand.</li>
<li>Translating post/page/CPT title, content, excerpt, and (when explicitly enabled) selected custom field values on demand.</li>
<li>Validating the saved API key by calling the languages list endpoint when the administrator clicks “Test Saved API Key”.</li>
</ul>
<p>What data is sent and when:</p>
<ul>
<li>Each translation request sends the source text, the source language code, and the target language code to https://translation.googleapis.com/language/translate/v2 along with the configured API key in the request URL. Requests are made only while a translation job is processing or when the administrator clicks “Test Saved API Key”.</li>
<li>The validation request sends only the API key to https://translation.googleapis.com/language/translate/v2/languages.</li>
<li>No personal data, user identifiers, IP addresses, or site visitor data are sent by the plugin. Standard HTTP request metadata (such as referrer set to the site URL) is included so the API key can be restricted by HTTP referrer in Google Cloud.</li>
</ul>
<p>Service provider: Google LLC. By using this plugin you agree to Google Cloud’s terms.</p>
<ul>
<li>Google Cloud Terms of Service: https://cloud.google.com/terms</li>
<li>Google Privacy Policy: https://policies.google.com/privacy</li>
<li>Google Cloud Translation documentation: https://cloud.google.com/translate/docs</li>
</ul>


Polyglot for Polylang

Automatically translate Polylang strings and content using Google Cloud Translation API (Basic v2).

GoogleTranslate

Pampa Dev

<p><a href="https://auto-translate.pampa.dev/" rel="nofollow ugc">Automatic Translator with Google Translate</a> by <a href="https://pampa.dev" rel="nofollow ugc">Pampa Dev</a> helps you translate WordPress content for visitors with a lightweight Google Translate language switcher. Add a floating selector, place it in a menu, publish it in a widget area, insert it with a shortcode, or use the selector block.</p>
<p>Version 2 makes the language switcher easier to use, easier to place, and easier to style. Visitors get a cleaner translation experience, and site owners get better controls for where the selector appears, which languages are shown, and what content should stay untranslated.</p>
<p>Automatic Translator is a free visitor translation plugin. It changes what visitors see in their browser after they choose a language. It does not create translated URLs, translated posts, hreflang tags, sitemap entries, translated metadata, or SEO-indexable translated pages.</p>
<p>Plugin interface translations are included for Spanish, German, French, Italian, Portuguese (Brazil), Japanese and English (UK).</p>
<h4>Features</h4>
<ul>
<li>Free client-side translation powered by the Google Translate website widget</li>
<li>Custom language switcher for a polished visitor-facing selector</li>
<li>Translate posts, pages, menus, widgets, theme text, plugin text, and WooCommerce storefront text that appears in the page HTML</li>
<li>Floating language selector with configurable corner and offset controls</li>
<li>Menu, widget, shortcode, and selector block placement options</li>
<li>Language search, selection, ordering, and optional all-languages mode</li>
<li>Country flags with broad regional flag choices for languages spoken in multiple places</li>
<li>Styling controls for colors, borders, typography, shadows, icons, and dropdown appearance</li>
<li>Auto-detect option based on the visitor browser language</li>
<li>Multiple selectors on the same page with shared translation state</li>
<li>Advanced exclusion selectors for brand names, code samples, checkout fragments, or other content that should not be translated</li>
<li>Dedicated shadow-scoped CSS for the isolated minimalist selector and detached dropdown overlay</li>
<li>Loads translation tools only when visitors need them</li>
<li>Hardens translated content and selector styling against aggressive theme CSS</li>
<li>Uses a more isolated custom selector shell so theme CSS is less likely to break translated labels or icon alignment</li>
<li>Renders the open language list in a detached shadow-isolated overlay layer so theme stacking, local containers, and theme CSS are less likely to break or block it</li>
<li>No paid SaaS account or translation API key required</li>
</ul>
<h4>Free mode and multilingual SEO</h4>
<p>Automatic Translator is built for instant visitor translation, not multilingual SEO indexing.</p>
<p>Free client-side translation is useful when visitors need to read your existing site in another language without creating and maintaining translated content. Search engines generally see the original page, because translated versions are not stored on separate URLs.</p>
<p>If you need multilingual SEO, you need a server-rendered translation system with stable language URLs, canonical handling, hreflang, sitemap integration, translated metadata, and translated slugs. Automatic Translator does not claim those features in free mode.</p>
<h4>Placement options</h4>
<p>You can place the language switcher in several ways:</p>
<ol>
<li>Floating selector in the Placement tab (enabled by default).</li>
<li>Add the selector block in the block editor.</li>
<li>Add the selector to a classic menu or Navigation block menu.</li>
<li>Add the Automatic Translator widget to a widget area.</li>
<li>Insert a shortcode in content or a template.</li>
</ol>
<h4>Supported languages</h4>
<p>Automatic Translator supports the languages available through the Google Translate website widget:</p>
<ul>
<li>Afrikaans</li>
<li>Albanian</li>
<li>Amharic</li>
<li>Arabic</li>
<li>Armenian</li>
<li>Azerbaijani</li>
<li>Basque</li>
<li>Belarusian</li>
<li>Bengali</li>
<li>Bosnian</li>
<li>Bulgarian</li>
<li>Catalan</li>
<li>Cebuano</li>
<li>Chichewa</li>
<li>Chinese (Simplified)</li>
<li>Chinese (Traditional)</li>
<li>Corsican</li>
<li>Croatian</li>
<li>Czech</li>
<li>Danish</li>
<li>Dutch</li>
<li>English</li>
<li>Esperanto</li>
<li>Estonian</li>
<li>Filipino</li>
<li>Finnish</li>
<li>French</li>
<li>Frisian</li>
<li>Galician</li>
<li>Georgian</li>
<li>German</li>
<li>Greek</li>
<li>Gujarati</li>
<li>Haitian Creole</li>
<li>Hausa</li>
<li>Hawaiian</li>
<li>Hebrew</li>
<li>Hindi</li>
<li>Hmong</li>
<li>Hungarian</li>
<li>Icelandic</li>
<li>Igbo</li>
<li>Indonesian</li>
<li>Irish</li>
<li>Italian</li>
<li>Japanese</li>
<li>Javanese</li>
<li>Kannada</li>
<li>Kazakh</li>
<li>Khmer</li>
<li>Korean</li>
<li>Kurdish (Kurmanji)</li>
<li>Kyrgyz</li>
<li>Lao</li>
<li>Latin</li>
<li>Latvian</li>
<li>Lithuanian</li>
<li>Luxembourgish</li>
<li>Macedonian</li>
<li>Malagasy</li>
<li>Malay</li>
<li>Malayalam</li>
<li>Maltese</li>
<li>Maori</li>
<li>Marathi</li>
<li>Mongolian</li>
<li>Myanmar (Burmese)</li>
<li>Nepali</li>
<li>Norwegian</li>
<li>Pashto</li>
<li>Persian</li>
<li>Polish</li>
<li>Portuguese</li>
<li>Punjabi</li>
<li>Romanian</li>
<li>Russian</li>
<li>Samoan</li>
<li>Scots Gaelic</li>
<li>Serbian</li>
<li>Sesotho</li>
<li>Shona</li>
<li>Sindhi</li>
<li>Sinhala</li>
<li>Slovak</li>
<li>Slovenian</li>
<li>Somali</li>
<li>Spanish</li>
<li>Sundanese</li>
<li>Swahili</li>
<li>Swedish</li>
<li>Tajik</li>
<li>Tamil</li>
<li>Telugu</li>
<li>Thai</li>
<li>Turkish</li>
<li>Ukrainian</li>
<li>Urdu</li>
<li>Uzbek</li>
<li>Vietnamese</li>
<li>Welsh</li>
<li>Xhosa</li>
<li>Yiddish</li>
<li>Yoruba</li>
<li>Zulu</li>
</ul>
<h3>Privacy Policy</h3>
<p>Automatic Translator with Google Translate uses <a href="https://appsero.com" rel="nofollow ugc">Appsero</a> SDK to collect some telemetry data upon user’s confirmation. This helps us troubleshoot problems faster and make product improvements.</p>
<p>Appsero SDK does not gather any data by default. The SDK only starts gathering basic telemetry data when a user allows it via the admin notice.</p>
<p>Integrating Appsero SDK does not immediately start gathering data without confirmation from users in any case.</p>
<p>Learn more about how <a href="https://appsero.com/privacy-policy/" rel="nofollow ugc">Appsero collects and uses this data</a>.</p>


Automatic Translator with Google Translate

We use this plugin in several of our clients' websites, it has a simple interface to make it match the designs.
They also offer good email support which is much appreciated. Thanks!

Flexible and easy to use

Translate your WordPress site with a polished Google Translate language switcher for instant visitor translation.

Polyglot for Polylang vs Automatic Translator with Google Translate