Proxylang: AI Translation & Multilingual SEO

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.

Set up your multilingual store or site in a few minutes.

Why Proxylang

WordPress translation generally takes one of three approaches:

• Database plugins: store duplicated translated content in your database and often involve manual translation work.

• DNS proxies: require CNAME or nameserver changes that some managed hosts don’t allow.

• Browser translate widgets: translate in the visitor’s browser but aren’t indexed by search engines.

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:

• Real per-language URLs ( yoursite.com/es-MX/about ) indexed by Google. Search-indexed language pages come with paid plans

• AI translation in 77 languages with context-aware quality

• Server-rendered translated HTML for search-engine bots (Googlebot, Bingbot, ChatGPT, Claude, Perplexity)

• Instant client-side translation for human visitors. No page re-render

• Auto-generated hreflang tags, per-language XML sitemaps, robots.txt

• WooCommerce Product JSON-LD localized for Google Shopping rich results

• Translation glossary so brand terms always render the way you want

• Full analytics dashboard with anonymous visitor tracking, languages, countries, top pages

• Zero DNS setup. Install plugin, paste keys, you’re live

Account required

This plugin connects WordPress to the Proxylang translation network. dev to use the plugin. Sign-up takes 30 seconds.

The free plan has 2,000 words in total for one language, with no end date. Paid plans add more words, more languages, and search-indexed language pages. dev/pricing.

Who is this for?

• WordPress sites going international: blogs, agencies, SaaS marketing sites, portfolios.

• WooCommerce stores selling cross-border: products, variations, cart, checkout, and Product schema all translate automatically.

• Sites on managed hosts that don’t allow DNS changes: Kinsta, WP Engine, WordPress.com Business+, Pressable, and similar.

• Agencies managing multilingual clients: install once, manage translations from one dashboard.

How it works under the hood

When a visitor lands on /es-MX/about, the plugin inspects the request:

• Search-engine bot (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.

• Human visitor: plugin redirects to your source URL ( /about ) 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.

Translations are cached at 300+ edge locations and inside your WordPress install, so repeat visitors see instant translated pages.

Features

• AI translation in 77 languages with brand-context awareness

• Translates both search engines and visitors. Bots see pre-rendered translated HTML, real visitors see live in-browser translation

• Per-language sitemap.xml, robots.txt, hreflang, og:locale, content-language headers

• Translation glossary: override AI translations for brand terms or any specific phrase

• Full analytics dashboard: visitors, languages, countries, top pages, growth over time. All anonymous and aggregated

• WooCommerce Product JSON-LD localization for Google Shopping

• Compatible with W3 Total Cache, WP Super Cache, LiteSpeed Cache, and other page caches

• Translation cache invalidation via signed HMAC webhooks. No manual purge

• GDPR-friendly. No visitor PII, cookies, or form submissions sent to Proxylang

• Works with any theme, page builder, or block editor (Elementor, Divi, Gutenberg, Bricks, etc.)

• WordPress 6.5+ and PHP 7.4+ supported

External services

This plugin connects to the Proxylang translation service. The plugin will not function without contacting these services. Translation cannot happen entirely on your server.

Proxylang runs the AI translation pipeline, edge cache, and dashboard.

What data is sent and when:

-

dev: configuration, plugin registration, daily heartbeat.

• POST https://proxylang.dev/api/proxylang/plugin/register: sent on plugin activation. Transmits: your public key (Authorization header), plugin version, your site’s home URL, REST webhook URL, requested mode.

• POST https://proxylang.dev/api/proxylang/plugin/heartbeat: sent once per day. Transmits: your public key, plugin version, mode, home URL.

• POST https://proxylang.dev/api/proxylang/plugin/config: sent on settings save and twice daily. Transmits: your public key. Returns: enabled languages, source language, registered domain.

-

dev (server-to-server, from your WordPress server): translated HTML and sitemap delivery.

• GET https://proxy.proxylang.dev/v1/render?domain=…&path=…&lang=…: sent when a search-engine bot requests a /{lang}/* URL. Transmits: your public key (X-Proxylang-Key header), the requesting visitor’s User-Agent (X-Proxylang-Visitor-UA header), requested path, language.

• GET https://proxy.proxylang.dev/v1/sitemap?domain=…&lang=…: sent when WordPress requests a per-language sitemap. Transmits: your public key, language code.

-

dev (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:

• <script src="https://proxy.proxylang.dev/script.js">: 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 data-key attribute.

• GET https://proxy.proxylang.dev/v1/script-bundle?key=…&lang=…&path=…: fetched (and <link rel="preload"> -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.

-

dev (loaded in each site visitor’s browser): Proxylang LiveChat. ) call into your front-end pages carrying the signed-in WordPress user’s name and email, and their WooCommerce billing phone and company when WooCommerce is active. dev so an agent can see who they are talking to.

Nothing is written for logged-out visitors, and the setting is off unless you turn it on. See Privacy below.

dev/privacy

dev/terms

Privacy

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

LiveChat identity is the one exception, and it is off by default. ) call. With WooCommerce active it also adds their billing phone, company, country and city.

Nothing at all is added for logged-out visitors, and nothing is added inside wp-admin.

Those values are read by the Proxylang chat widget and sent to Proxylang so a support agent can see who they are talking to. Because they sit in the page, any other script running on your pages can also read them. Leave the setting off if that is not acceptable on your site.

If you also set a LiveChat verification key, the plugin computes an HMAC-SHA256 signature of the email on your server. The key itself is stored in your WordPress options and is never added to a page; only the signature is.

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.

For European customers: Proxylang is GDPR-compliant. See the privacy policy linked above for the full data-processing agreement.