Quick disclosure first: I work at Cool Plugins, the team behind both Linguator and the TranslateXYZ AI translation addons. Linguator is our newer multilingual plugin and this post explains what it is, how it relates to Polylang and when each one is the right fit. I will keep that honest as we go through both options.
What Linguator actually is
Linguator is our complete multilingual WordPress plugin with AI translation built in. It is an advanced fork of Polylang that we rebuilt with a modern admin dashboard, built-in AI translation (no separate addon required) and a cleaner setup flow. Each translated post is still a real WordPress post linked to its source through a translation group, so the underlying data model is familiar to anyone who has worked with Polylang or other separate-post multilingual plugins.
The key thing to understand: Linguator is not an addon. It is a full multilingual plugin in its own right. You do not need WPML, Polylang or TranslatePress underneath. Install Linguator and you have everything: languages, language switcher, hreflang, SEO-friendly URLs, manual translation, AI translation, bulk translation, all in one plugin.
What is built into Linguator out of the box
The free version on WordPress.org is genuinely usable on its own, not a feature-stripped demo. The full feature set across free and Pro:
- Built-in AI translation. Translate pages and posts using Google AI and Chrome built-in AI directly in the browser. No separate addon, no extra plugin to install.
- Free in-browser translation. Chrome built-in AI runs locally on the visitor's machine. No API key, no quota, no translation cost.
- Bulk translation. Translate multiple posts, pages and custom post types at once instead of clicking through each one.
- Custom post type support. Translate Pages, Posts, plus custom types like Events, Products, Portfolios and Testimonials.
- Unlimited languages. Add and manage as many languages as you want from a single panel.
- Multimedia translation. Image titles, captions, alt text and descriptions all translate per language, which is useful for image SEO across multilingual sites.
- RTL language support. Automatically handles text direction, alignment and layout for languages like Arabic and Hebrew.
- SEO-friendly multilingual URLs. Per-language slugs and hreflang annotations handled out of the box.
- Elementor and Gutenberg compatibility. Translated content keeps the original page builder layout intact.
- Manual translation alongside AI. Edit any AI translation in place or write translations entirely by hand.
- Language switcher widget and block. Drop into any sidebar, header, footer or page builder layout.
Why we built Linguator as a Polylang fork
Polylang is a great plugin. We have worked with it for years. AutoPoly, our AI translation addon for Polylang, has more than 4,500 active installs at this point. So why fork it?
Two reasons. First, the admin UI was due for an update. Polylang's dashboard works, but it has not changed much in years and it shows. We wanted to ship a fresher admin experience designed around the way teams actually translate sites in 2026: bulk-first, AI-first, with less hunting through settings panels. Second, we wanted AI translation built in rather than layered through an addon. Linguator is what you get when those two ideas ship as one plugin instead of two.
Polylang's separate-post data model is the right foundation, so we kept it. The bones of Linguator are familiar to anyone who has worked with Polylang. The surface is rebuilt.
Install Linguator, add your languages, translate your site. No separate AI addon, no monthly translation credits, no proxy SaaS lock-in.
Linguator vs Polylang: side by side
| Feature | Linguator | Polylang |
|---|---|---|
| Free version on WordPress.org | Yes (with built-in AI translation) | Yes (multilingual only, no AI) |
| Data model | Separate post per language (Polylang-compatible) | Separate post per language |
| Admin dashboard | Modern, rebuilt for 2026 workflows | Stable, less recent UI updates |
| AI translation | Built in (Google AI, Chrome built-in AI) | Not built in (use AutoPoly addon) |
| Bulk translation | Built in | Pro DeepL bulk or AutoPoly addon |
| Free unlimited AI provider | Yes (Chrome built-in AI, no API key) | Via AutoPoly addon (Yandex, Chrome AI) |
| Custom post types | Built in | Pro feature |
| Multimedia translation (alt text, captions) | Built in | Pro / manual setup |
| RTL language support | Automatic | Theme-dependent |
| Elementor + Gutenberg | Supported | Supported (Elementor needs an extra plugin for full integration) |
| WooCommerce | Custom post type support covers products | Polylang for WooCommerce (separate paid add-on) |
| Addon and ecosystem maturity | Newer, growing | Established, deeper third-party ecosystem |
| Best for | New multilingual sites that want one plugin to do everything | Existing Polylang sites and projects that need the wider addon ecosystem |
If you want to stick with Polylang
Polylang is still a great pick, especially if you already run it on a production site or you need the deeper third-party ecosystem. The Polylang for WooCommerce add-on, niche page builder integrations and ten-plus years of edge-case fixes are real advantages on complex sites. There is no good reason to migrate a working Polylang install just to chase a newer UI.
For AI translation on a Polylang site, the matching addon from us is AutoPoly. It supports six AI providers (OpenAI, Gemini, DeepL, Google Translate, Yandex, Chrome AI) including three completely free options with no API key required. AutoPoly works with both Polylang free and Polylang Pro. Full walkthrough in the Polylang AI translation guide.
Free Linguator vs Pro Linguator
The free version on WordPress.org ships with the core multilingual features plus built-in AI translation through Google AI and Chrome built-in AI. That alone covers a surprising amount of real-world use, especially for content sites and small marketing sites. You can translate the whole site at zero ongoing cost using Chrome built-in AI.
The premium version on linguator.com unlocks additional AI providers, advanced bulk translation features and the full custom post type workflow for larger projects. Worth the upgrade once you outgrow the free build.
When Linguator is the right pick
- Brand new multilingual site. No migration pain, you get the modern UI and built-in AI from day one.
- You want one plugin to do everything. Languages, AI translation and bulk translation in a single install instead of base plugin plus AI addon.
- Zero translation budget. Chrome built-in AI inside Linguator translates entirely in the browser. No API key, no monthly cost, no usage cap.
- Privacy-sensitive content. Chrome AI runs locally on the visitor's machine, so nothing leaves the browser during translation.
- Multilingual content site with images. The multimedia translation (alt text, captions, descriptions) is built in, useful for image SEO across language versions.
- RTL languages on the roadmap. Arabic, Hebrew, Persian. Linguator handles text direction automatically.
When Polylang is still the better pick
- Existing Polylang site that is working. The migration cost rarely justifies the swap. Install AutoPoly for AI translation and stay where you are.
- Complex WooCommerce store. Polylang plus Polylang for WooCommerce has more years of compatibility work. Linguator covers WooCommerce through its custom post type support but the ecosystem is younger.
- You need a specific Polylang addon or integration. Custom REST endpoints, niche page builder compatibility, third-party plugin integrations. Polylang's ecosystem is deeper.
- Mission-critical site with unusual requirements. Polylang has more years of edge-case fixes behind it.
Migration from Polylang to Linguator
Linguator includes a migration tool that imports your existing Polylang languages, post translations and basic taxonomies. On a content site or marketing site without heavy custom work, the migration is straightforward and takes minutes. On sites with significant ACF custom fields, third-party integrations or custom code that references Polylang-specific functions, plan for additional cleanup time. The general rule of thumb: small sites migrate cleanly, large complex sites need a careful sandbox pass first.
Honestly, if Polylang is already working for you, the better move is usually to stay on Polylang and add AutoPoly for AI translation. Linguator is the stronger pick when you are starting fresh.
AutoPoly for Polylang, AutoMLP for WPML, AutoTP for TranslatePress and LocoAI for theme and plugin strings. One license for all four.
Wrapping up
Linguator is what we wish a modern multilingual WordPress plugin looked like in 2026: clean admin, AI translation built in, free in-browser translation through Chrome built-in AI, no monthly credits or SaaS lock-in. The free version on WordPress.org is real and useful, the Pro version on linguator.com covers larger projects.
Polylang is still a great plugin and a fair pick, especially when you already run it. If you want to stay on Polylang and add AI translation, our AutoPoly addon covers six providers including three completely free options. For more on the Polylang side, the Polylang AI translation guide walks through the setup. For broader context, the three-way comparison with WPML and TranslatePress covers the wider multilingual landscape.
