proxylang

<p><strong>Instant website translation and SEO to grow your global traffic. Get lang prefixes, hreflang tags, and automated sitemaps for Google. No complex DNS setup needed. Launch your multilingual store or site in 60 seconds.</strong></p>
<h4>Why Proxylang</h4>
<p>WordPress translation generally takes one of three approaches:</p>
<ul>
<li><strong>Database plugins</strong>: store duplicated translated content in your database and often involve manual translation work.</li>
<li><strong>DNS proxies</strong>: require CNAME or nameserver changes that some managed hosts don’t allow.</li>
<li><strong>Browser translate widgets</strong>: translate in the visitor’s browser but aren’t indexed by search engines.</li>
</ul>
<p>Proxylang gives you real indexed per-language URLs, server-rendered SEO for search crawlers, and instant in-browser translation for visitors — with no DNS changes:</p>
<ul>
<li>Real per-language URLs (<code>yoursite.com/es-MX/about</code>) indexed by Google</li>
<li>AI translation in 68 languages with context-aware quality</li>
<li>Server-rendered translated HTML for search-engine bots (Googlebot, Bingbot, ChatGPT, Claude, Perplexity)</li>
<li>Instant client-side translation for human visitors. No page re-render</li>
<li>Auto-generated hreflang tags, per-language XML sitemaps, robots.txt</li>
<li>WooCommerce Product JSON-LD localized for Google Shopping rich results</li>
<li>Translation glossary so brand terms always render the way you want</li>
<li>Full analytics dashboard with anonymous visitor tracking, languages, countries, top pages</li>
<li>Zero DNS setup. Install plugin, paste keys, you’re live</li>
</ul>
<h4>Account required</h4>
<p>This plugin connects WordPress to the Proxylang translation network. <strong>You’ll need a free Proxylang account at <a href="https://proxylang.dev" rel="nofollow ugc">proxylang.dev</a> to use the plugin.</strong> Sign-up takes 30 seconds. The free tier translates 2,000 words/month at no cost. Enough for most small business sites. Higher tiers scale with traffic. See <a href="https://proxylang.dev/pricing" rel="nofollow ugc">proxylang.dev/pricing</a>.</p>
<h4>Who is this for?</h4>
<ul>
<li><strong>WordPress sites going international</strong>: blogs, agencies, SaaS marketing sites, portfolios.</li>
<li><strong>WooCommerce stores selling cross-border</strong>: products, variations, cart, checkout, and Product schema all translate automatically.</li>
<li><strong>Sites on managed hosts</strong> that don’t allow DNS changes: Kinsta, WP Engine, WordPress.com Business+, Pressable, and similar.</li>
<li><strong>Agencies managing multilingual clients</strong>: install once, manage translations from one dashboard.</li>
</ul>
<h4>How it works under the hood</h4>
<p>When a visitor lands on <code>/es-MX/about</code>, the plugin inspects the request:</p>
<ul>
<li><strong>Search-engine bot</strong> (Googlebot, ChatGPT, Claude, etc.): plugin fetches a fully translated HTML page from Proxylang’s edge network and serves it directly. Indexable, hreflang-annotated, no JavaScript required.</li>
<li><strong>Human visitor</strong>: plugin redirects to your source URL (<code>/about</code>) and sets a language cookie. Your page then loads with a tiny script that translates visible content client-side. No full re-render, no flicker, and your address bar stays clean.</li>
</ul>
<p>Translations are cached at 300+ edge locations and inside your WordPress install, so repeat visitors see instant translated pages.</p>
<h3>Features</h3>
<ul>
<li>AI translation in 68 languages with brand-context awareness</li>
<li>Translates both search engines and visitors. Bots see pre-rendered translated HTML, real visitors see live in-browser translation</li>
<li>Per-language <code>sitemap.xml</code>, <code>robots.txt</code>, hreflang, og:locale, content-language headers</li>
<li><strong>Translation glossary</strong>: override AI translations for brand terms or any specific phrase</li>
<li><strong>Full analytics dashboard</strong>: visitors, languages, countries, top pages, growth over time. All anonymous and aggregated</li>
<li>WooCommerce Product JSON-LD localization for Google Shopping</li>
<li>Compatible with W3 Total Cache, WP Super Cache, LiteSpeed Cache, and other page caches</li>
<li>Translation cache invalidation via signed HMAC webhooks. No manual purge</li>
<li>GDPR-friendly. No visitor PII, cookies, or form submissions sent to Proxylang</li>
<li>Works with any theme, page builder, or block editor (Elementor, Divi, Gutenberg, Bricks, etc.)</li>
<li>WordPress 6.5+ and PHP 7.4+ supported</li>
</ul>
<h3>External services</h3>
<p>This plugin connects to the Proxylang translation service. <strong>The plugin will not function without contacting these services.</strong> Translation cannot happen entirely on your server. Proxylang runs the AI translation pipeline, edge cache, and dashboard.</p>
<p>What data is sent and when:</p>
<ol>
<li>
<p><strong>proxylang.dev</strong>: configuration, plugin registration, daily heartbeat.</p>
<ul>
<li><code>POST https://proxylang.dev/api/proxylang/plugin/register</code>: sent on plugin activation. Transmits: your public key (Authorization header), plugin version, your site’s home URL, REST webhook URL, requested mode.</li>
<li><code>POST https://proxylang.dev/api/proxylang/plugin/heartbeat</code>: sent once per day. Transmits: your public key, plugin version, mode, home URL.</li>
<li><code>POST https://proxylang.dev/api/proxylang/plugin/config</code>: sent on settings save and twice daily. Transmits: your public key. Returns: enabled languages, source language, registered domain.</li>
</ul>
</li>
<li>
<p><strong>proxy.proxylang.dev</strong> (server-to-server, from your WordPress server): translated HTML and sitemap delivery.</p>
<ul>
<li><code>GET https://proxy.proxylang.dev/v1/render?domain=…&path=…&lang=…</code>: sent when a search-engine bot requests a <code>/{lang}/*</code> URL. Transmits: your public key (X-Proxylang-Key header), the requesting visitor’s User-Agent (X-Proxylang-Visitor-UA header), requested path, language.</li>
<li><code>GET https://proxy.proxylang.dev/v1/sitemap?domain=…&lang=…</code>: sent when WordPress requests a per-language sitemap. Transmits: your public key, language code.</li>
</ul>
</li>
<li>
<p><strong>proxy.proxylang.dev</strong> (loaded in each site visitor’s browser): live in-page translation for human visitors. The plugin adds the following to your front-end pages when enabled:</p>
<ul>
<li><code><script src="https://proxy.proxylang.dev/script.js"></code>: enqueued into every enabled front-end page. The visitor’s browser downloads and runs this script to translate the page client-side. Your public key is passed to it via a <code>data-key</code> attribute.</li>
<li><code>GET https://proxy.proxylang.dev/v1/script-bundle?key=…&lang=…&path=…</code>: fetched (and <code><link rel="preload"></code>-hinted) by that script to retrieve cached translations for the current page and language. Transmits: your public key, target language, page path. No visitor personal data is sent.</li>
</ul>
</li>
</ol>
<p>Proxylang’s privacy policy: https://proxylang.dev/privacy<br />
Proxylang’s terms of service: https://proxylang.dev/terms</p>
<h3>Privacy</h3>
<p>This plugin does NOT send visitor personal data, cookies, form submissions, IP addresses, or session content to Proxylang. Only the request URL path and the visitor’s User-Agent string are transmitted (the User-Agent is required so that bot translations can be metered per crawler). Logged-in administrator previews skip Proxylang entirely and serve the origin page directly.</p>
<p>Translation caches live entirely on your WordPress install (in object cache or transients) and on Proxylang’s edge network. No per-visitor records are stored. Analytics are collected anonymously and aggregated (country, language, page path) for the dashboard.</p>
<p>For European customers: Proxylang is GDPR-compliant. See the privacy policy linked above for the full data-processing agreement.</p>


Proxylang: AI Translation & Multilingual SEO

Instant website translation and SEO to grow your global traffic. Lang prefixes, hreflang, sitemaps for Google. No DNS. Live in 60 seconds.

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.

Proxylang: AI Translation & Multilingual SEO vs BPC AI Translator