BlogPasCher

<p>BPC AI Translator helps WordPress administrators manage multilingual content from inside WordPress. It stores language settings, translation records, review status, URL mapping and language switcher configuration locally in the site database.</p>
<p>The plugin can work as a local multilingual management layer, and it can also request AI translations when an administrator deliberately configures a supported provider API key. Provider keys are stored in the WordPress installation and are used only for the selected provider actions.</p>
<h4>Main features</h4>
<ul>
<li>Manage source and target languages, including locale, URL slug, active status, source language, default language and indexable status.</li>
<li>Store translations locally with source text, translated text, source locale, target locale, origin and review status.</li>
<li>Review, publish, lock, import, export and filter translation records from the WordPress admin.</li>
<li>Configure translated URLs with prefix, subdomain or mapped-domain strategies, depending on your hosting setup.</li>
<li>Add language switchers with shortcode, widget, block, menu integration or floating frontend switcher.</li>
<li>Generate hreflang metadata for active, indexable languages.</li>
<li>Configure optional AI providers with your own API keys: OpenAI, Anthropic, xAI, Google Gemini and DeepL.</li>
<li>Distinguish a saved provider key from a connection that has actually been tested.</li>
<li>Cache translation results and keep translation logs with configurable retention.</li>
<li>Exclude known bots from browser-language redirection to protect indexing behavior.</li>
</ul>
<p>Important operating facts:</p>
<ul>
<li>A saved API key is stored encrypted locally when the server supports the required encryption setup.</li>
<li>A provider connection is described as verified only after a real connection test succeeds.</li>
<li>Translation requests can incur charges billed directly by the selected provider.</li>
<li>The plugin does not provide a managed credit wallet.</li>
<li>PHP extensions <code>mbstring</code> and <code>openssl</code> are required.</li>
</ul>
<h4>Privacy and data handling</h4>
<p>The plugin stores translation data in the local WordPress database. External translation requests are not sent until an administrator configures a provider key and runs a provider test or translation action.</p>
<p>When an AI translation action is used, the selected provider can receive the source text, target language, optional context and model settings needed to perform the translation. Review the terms and privacy policy of each provider before enabling it.</p>
<h4>Review-first workflow</h4>
<p>BPC AI Translator is designed for reviewed publishing. Generated or imported translations can be kept as drafts, marked as needing review, reviewed, published, locked or marked obsolete depending on the site workflow and user permissions.</p>
<h3>External services</h3>
<p>This plugin can send content to third-party API services only after an administrator configures a provider key and performs a test or translation action. Depending on the action, submitted data can include source text, target language, optional translation context, and the selected model. The administrator is responsible for reviewing provider terms and privacy policies before enabling a provider.</p>
<ul>
<li>OpenAI API: translation requests may be sent to <code>https://api.openai.com/</code>. Terms: https://openai.com/policies/terms-of-use/ Privacy: https://openai.com/policies/privacy-policy/</li>
<li>Anthropic API: translation requests may be sent to <code>https://api.anthropic.com/</code>. Terms: https://www.anthropic.com/legal/commercial-terms Privacy: https://www.anthropic.com/legal/privacy</li>
<li>xAI API: translation requests may be sent to <code>https://api.x.ai/</code>. Terms: https://x.ai/legal/terms-of-service Privacy: https://x.ai/legal/privacy-policy</li>
<li>Google Gemini API: translation requests may be sent to <code>https://generativelanguage.googleapis.com/</code>. Terms: https://ai.google.dev/gemini-api/terms Privacy: https://policies.google.com/privacy</li>
<li>DeepL API: translation requests may be sent to <code>https://api-free.deepl.com/</code> or <code>https://api.deepl.com/</code>, according to the configured plan. Terms: https://www.deepl.com/en/pro-license Privacy: https://www.deepl.com/en/privacy</li>
</ul>
<p>API keys remain in the local WordPress installation and are transmitted only to the configured provider as required for authenticated requests.</p>


BPC AI Translator

Manage multilingual WordPress content with local translations, provider API keys, reviewed publishing, translated URLs, and language switchers.

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.

BPC AI Translator vs Translera – Automatic Google Translate for Multilingual Websites