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).

ilmosys

<p>Translera is a lightweight automatic WordPress translation plugin for creating multilingual websites with clean language URLs, Google Translate support, and flexible language switchers.</p>
<p>Use Translera to add a multilingual experience to blogs, business websites, landing pages, WooCommerce-style storefronts, documentation sites, and Elementor pages. The plugin supports language prefixes such as <code>/es/</code>, <code>/fr/</code>, and <code>/ar/</code>, query parameter language URLs, automatic hreflang tags, RTL language handling, and more than 30 languages.</p>
<h4>Key Features</h4>
<ul>
<li><strong>Google Translate integration</strong> – translate content with Google Translate using the free endpoint or your own Google API key.</li>
<li><strong>SEO-friendly language URLs</strong> – use clean subdirectory URLs like <code>example.com/es/page/</code> or query URLs like <code>example.com/page/?lang=es</code>.</li>
<li><strong>Automatic hreflang tags</strong> – help search engines understand alternate language versions of each page.</li>
<li><strong>Language switcher shortcode</strong> – add <code>[translera_switcher]</code> to pages, posts, widgets, or templates.</li>
<li><strong>Gutenberg block</strong> – insert a language switcher directly in the WordPress block editor.</li>
<li><strong>Elementor widget</strong> – add a native Translera Language Switcher widget to Elementor layouts.</li>
<li><strong>Integration controls</strong> – Elementor widget and Gutenberg block integrations are enabled by default and can be managed from Translera settings.</li>
<li><strong>Multiple switcher styles</strong> – choose dropdown, flags-only, or list layouts.</li>
<li><strong>30+ supported languages</strong> – including English, Spanish, French, German, Arabic, Chinese, Japanese, Portuguese, Hindi, Hebrew, Persian, Urdu, and more.</li>
<li><strong>RTL support</strong> – automatically handles right-to-left languages such as Arabic, Hebrew, Persian, and Urdu.</li>
<li><strong>Browser language detection</strong> – optionally detect the visitor’s preferred language.</li>
<li><strong>Translation caching support</strong> – reduce repeated translation requests with transient and browser-side caching.</li>
<li><strong>Lightweight frontend assets</strong> – designed to add multilingual tools without heavy page-builder dependencies.</li>
</ul>
<h4>Why Use Translera?</h4>
<p>Translera helps make your WordPress site easier to read for international visitors while keeping your URLs structured for multilingual SEO. It is built around standard WordPress APIs, so it works with most themes and can be used through shortcode, block editor, Elementor, or PHP template code.</p>
<h3>Configuration</h3>
<h4>General Settings</h4>
<ul>
<li>Choose the default site language.</li>
<li>Enable the languages you want to show in the switcher.</li>
<li>Select Google Translate as the translation method.</li>
<li>Choose subdirectory URLs or query parameter URLs.</li>
<li>Enable or disable browser language detection.</li>
<li>Enable or disable the Elementor widget and Gutenberg block integrations. Both are enabled by default.</li>
</ul>
<h4>URL Structures</h4>
<p>Translera supports two multilingual URL formats:</p>
<ul>
<li><strong>Subdirectory URLs:</strong> <code>example.com/es/privacy-policy/</code></li>
<li><strong>Query parameter URLs:</strong> <code>example.com/privacy-policy/?lang=es</code></li>
</ul>
<p>Subdirectory URLs are recommended for clean, SEO-friendly multilingual site structure.</p>
<h4>Google Translate</h4>
<p>Translera can translate using Google Translate. You can leave the Google API key field empty to use the free translation endpoint, or add your own API key for Google Cloud Translation API requests.</p>
<h4>Language Switcher</h4>
<p>The language switcher can show flags, native language names, translated language names, or a compact flags-only layout. Available styles include:</p>
<ul>
<li>Dropdown</li>
<li>Flags only</li>
<li>List</li>
</ul>
<h3>Usage</h3>
<h4>Shortcode</h4>
<p>Add the language switcher anywhere shortcodes are supported:</p>
<pre><code>[translera_switcher]
</code></pre>
<p>Use shortcode options to customize the output:</p>
<pre><code>[translera_switcher style="flags" show_flags="true" show_names="false"]
</code></pre>
<h4>Gutenberg Block</h4>
<p>The Gutenberg block integration is enabled by default from <strong>Translera > Settings > General > Integrations</strong>.</p>
<ol>
<li>Edit a page or post with the block editor.</li>
<li>Search for <strong>Translera Language Switcher</strong>.</li>
<li>Insert the block.</li>
<li>Choose the switcher style and display options in the block sidebar.</li>
</ol>
<h4>Elementor Widget</h4>
<p>The Elementor widget integration is enabled by default from <strong>Translera > Settings > General > Integrations</strong>.</p>
<ol>
<li>Edit a page with Elementor.</li>
<li>Search for <strong>Translera Language Switcher</strong>.</li>
<li>Drag the widget into your layout.</li>
<li>Configure style, flags, native names, and alignment.</li>
</ol>
<h4>PHP Template Usage</h4>
<p>Theme developers can render the switcher in template files:</p>
<pre><code><?php
echo wp_kses_post(
    Translera_Language_Switcher::render_block(
        array(
            'style'       => 'dropdown',
            'show_flags'  => true,
            'show_native' => true,
            'show_names'  => true,
        )
    )
);
?>
</code></pre>
<h3>Supported Languages</h3>
<p>Translera includes support for English, Spanish, French, German, Arabic, Chinese, Japanese, Portuguese, Russian, Italian, Korean, Dutch, Polish, Turkish, Vietnamese, Thai, Indonesian, Hindi, Swedish, Danish, Finnish, Norwegian, Greek, Hebrew, Ukrainian, Czech, Romanian, Hungarian, Bengali, Malay, Persian, Urdu, and more.</p>
<h3>SEO Features</h3>
<p>Translera is built for multilingual SEO workflows:</p>
<ul>
<li>Clean language-specific URLs.</li>
<li>Automatic <code>hreflang</code> alternate links.</li>
<li><code>x-default</code> hreflang output.</li>
<li>Language-aware page, post, home, and term links.</li>
<li>RTL-aware HTML attributes for supported languages.</li>
</ul>
<h3>External services</h3>
<p>This plugin uses Google translation services to translate page content and language-switcher labels. Translation requests are sent only when a visitor views a non-default language version of your site (or when an administrator runs a translation test from the settings screen).</p>
<h4>Google Cloud Translation API</h4>
<p>When you enter a Google Cloud API key in <strong>Translera > Settings</strong>, the plugin sends translation requests to the official Google Cloud Translation API (<code>https://translation.googleapis.com/language/translate/v2</code>).</p>
<p><strong>What is sent:</strong> The text to translate, source language code, target language code, and your API key.</p>
<p><strong>When it is sent:</strong> During server-side translation (when enabled via the <code>translera_auto_translate</code> filter), REST API translation tests from the admin, and any server-side caching of translations.</p>
<p><strong>Service provider:</strong> Google LLC — <a href="https://cloud.google.com/terms/service-terms" rel="nofollow ugc">Terms of Service</a>, <a href="https://policies.google.com/privacy" rel="nofollow ugc">Privacy Policy</a>.</p>
<h4>Google Translate (free endpoint)</h4>
<p>When no API key is configured, the plugin may use Google’s public translate endpoint (<code>https://translate.googleapis.com/translate_a/single</code>) for server-side and browser-side translation.</p>
<p><strong>What is sent:</strong> The text to translate, source language code, target language code, and a client identifier (<code>gtx</code>). No API key is sent.</p>
<p><strong>When it is sent:</strong> When a visitor loads a page in a non-default language (browser-side translation in <code>frontend.js</code>), during server-side translation when enabled, and during admin translation tests.</p>
<p><strong>Service provider:</strong> Google LLC — <a href="https://policies.google.com/terms" rel="nofollow ugc">Google Terms of Service</a>, <a href="https://policies.google.com/privacy" rel="nofollow ugc">Privacy Policy</a>.</p>
<p><strong>Note:</strong> The free endpoint is not part of the official Google Cloud Translation API and may be subject to usage limits or changes by Google. For production sites, Google recommends using the Cloud Translation API with your own API key.</p>


Translera – Automatic Google Translate for Multilingual Websites

Add multilingual WordPress translation with Google Translate, SEO hreflang URLs, Elementor, Gutenberg, and a language switcher.

Polyglot for Polylang vs Translera – Automatic Google Translate for Multilingual Websites