Polylang is a solid multilingual framework for WordPress, but it does not include an AI translation engine. If you want to add automatic AI translation to a Polylang-based site, you have two real options: connect Polylang Pro to a limited set of third-party services (currently mainly DeepL), or move the translation layer to a plugin built around AI from the start, such as GPTranslate. This guide explains both paths and helps you decide which one fits your site.
Does Polylang Support AI Translation?
Polylang itself has no built-in AI translation engine. Its free version creates the multilingual URL and content structure, but the actual translated text has to come from somewhere else: a human translator, copy-pasted machine translation, or a connected third-party service.
Polylang Pro adds integrations with external translation services, most notably DeepL, which gives you a one-click first-pass translation of existing content. This is useful, but it has a few limitations worth knowing before you rely on it:
- DeepL only. Polylang Pro’s automatic translation uses DeepL. There is no option to switch to ChatGPT, Claude, Gemini, Grok, or DeepSeek.
- Still a manual trigger. The bulk translation job runs when you ask it to. It does not continuously pick up new posts or content changes the way a native AI agent plugin would.
- SEO metadata is not covered automatically. Meta titles, meta descriptions, Open Graph tags, and URL slugs still need to be handled separately.
- The Polylang structure stays. Each translated page is a separate post you manage individually. There is no single-source content model where translations update automatically when the original changes.
If those limitations are fine for your workflow, Polylang Pro plus DeepL is a workable setup. If you need more AI providers, continuous updates, or full SEO metadata coverage, a dedicated AI translation plugin is the practical path.
Adding ChatGPT, Claude and Gemini Translation to WordPress
GPTranslate is a WordPress plugin built specifically around AI-model translation. It connects directly to ChatGPT, Claude, Gemini, Grok, DeepSeek, DeepL, Google AI, and Google Cloud Translation, and it works independently of Polylang — you do not need Polylang installed for GPTranslate to make a site multilingual.
The plugin translates content through an AI Agent Crawler that scans your site, detects every piece of visible and hidden text (including metadata, attributes, and URL slugs), and sends it to the AI model of your choice. Once the initial crawl is done, new and updated content is picked up and translated automatically, without a separate manual job to remember.
Featured by WPTuts, GPTranslate was covered in detail by Paul Charlton in a hands-on deep dive and in an official video review. You can also try GPTranslate live on WordPress Playground without installing anything.
Polylang with DeepL vs GPTranslate with Multiple AI Providers
| Feature | Polylang Pro + DeepL | GPTranslate |
|---|---|---|
| AI providers | DeepL only | ChatGPT, Claude, Gemini, Grok, DeepSeek, DeepL, Google AI, Google Cloud Translation |
| Automatic updates | Manual trigger required | Automatic incremental translation of new and changed content |
| SEO metadata | Manual per language | Automatically translated: titles, descriptions, OG tags, hreflang |
| URL slugs | Manual translation of each slug | Automatic AI translation of URL slugs with transliteration support |
| WooCommerce | Separate Polylang for WooCommerce add-on required | Included, translates product pages, checkout and cart |
| GDPR / no third-party cloud | Sends content to DeepL servers | Translations stored on your own server; provider API calls via your own key |
| Pricing model | Annual subscription | One-time license (Full version) |
Which Approach to Choose
Stay with Polylang + DeepL if you already have a mature Polylang site with custom templates or developer customizations built around its content structure, your team is comfortable with a manual translation workflow, and DeepL quality is good enough for your language pairs.
Use GPTranslate instead if you are starting a new multilingual project, you need more than one AI provider (or want to compare ChatGPT versus Claude quality for your specific content), you want SEO metadata and URL slugs translated automatically, or you find the recurring Polylang subscription cost unfavorable for long-running projects.
GPTranslate does not require Polylang. It creates its own multilingual URL structure with language prefixes, hreflang tags, and an XML sitemap, so it can replace Polylang’s role entirely for sites that are starting fresh or willing to migrate off the existing structure.
Migrating from Polylang to GPTranslate
Migrating is a real undertaking and should be planned carefully: Polylang stores each language version as a separate post, while GPTranslate stores translations in its own database tables and serves them as overlays on the original content. There is no automatic import path between the two systems.
A practical migration sequence: export and note all existing translated URLs and their redirects before deactivating Polylang, then install GPTranslate and run the AI crawl to produce translations for all languages in one pass, then set up 301 redirects from any old language URLs that changed structure. For smaller sites this is manageable in a day; for larger sites with hundreds of translated posts it warrants a staging-environment test first.
Step-by-Step: Setting Up GPTranslate on a WordPress Site
GPTranslate installs and activates like any standard WordPress plugin. Here is the full setup sequence for a site that is either starting fresh or moving away from Polylang.
- Install GPTranslate. Download the free version from WordPress.org or install it directly from the plugin search in your WP admin panel. Activate it.
- Choose your AI provider. In GPTranslate settings, select the AI model you want to use. The free version includes Google AI at no cost and with no API key required. For ChatGPT, Claude, Gemini or DeepSeek you connect your own provider API key. The plugin saves the key server-side and never exposes it to visitors.
- Enable your target languages. Select the languages you want the site to support. GPTranslate immediately creates language-prefixed URL routes (for example
/fr/,/de/,/es/) and adds a language switcher widget you can place anywhere with a block or shortcode. - Run the AI Agent Crawler. Launch the crawler from the GPTranslate dashboard. It scans your entire site — posts, pages, WooCommerce products, menus, widgets, SEO metadata and URL slugs — and sends each piece to the AI model. Translation happens in the background; you can close the browser and come back when it is done.
- Review and publish. Once the crawl finishes, every language version of your site is live. You can open the Translation Editor to review, correct, or lock any specific string from being auto-updated in future crawls.
- Set up redirects if migrating from Polylang. If you had Polylang active, deactivate it after GPTranslate is running and redirect any old Polylang-style URLs (for example
/?lang=fr) to the new GPTranslate prefix format (/fr/) using a redirect plugin or your.htaccessfile.
The total time from install to a fully translated site is typically under 30 minutes for a site with fewer than 100 pages, and a few hours for larger catalogs. No developer is needed for a standard setup.
Translation Quality: Which AI Provider to Choose for Your Language Pair
The right AI model depends on which language pair you are translating and what type of content you have. Here is a practical summary based on real use across GPTranslate users:
- ChatGPT (GPT-4o / GPT-4.1): Strongest for nuanced, long-form editorial content. Handles idioms, marketing copy, and brand voice well. Best for English into Western European languages.
- Claude (Claude Sonnet): Particularly strong for formal, legal, and technical text. Consistent register across long documents. Excellent for professional services content.
- DeepL: Best raw accuracy for European language pairs (especially German, French, Spanish, Dutch, Polish). Slightly narrower language coverage than the GPT/Claude models but precision is high for supported pairs.
- Gemini: Good general-purpose option, especially for Asian and Middle Eastern languages. Works well for e-commerce product descriptions.
- Google AI (free tier): Covers 100+ languages. Quality is good for informational content. Ideal for sites starting out or testing multilingual before committing to a paid AI provider.
GPTranslate lets you assign different AI models to different languages, so you can use DeepL for German while running ChatGPT for Japanese, all from the same plugin settings screen.
Frequently Asked Questions
Can I use Polylang and GPTranslate at the same time?
It is not recommended. Both plugins modify URL routing and multilingual structure, and running them simultaneously on the same site is likely to produce conflicts in URL handling and hreflang output. Choose one as the primary multilingual layer.
Is there a free version of GPTranslate?
Yes. The free version on WordPress.org is fully functional with Google AI (unlimited and free), limited to 2,500 words per page and 10 pages in the crawler. The Full version removes those limits and adds premium support.
Does GPTranslate translate WooCommerce products automatically?
Yes, WooCommerce product pages, cart, checkout, and category pages are all translated as part of the same AI crawl, without a separate add-on.
What if I want to use ChatGPT instead of DeepL for Polylang?
Polylang Pro does not support ChatGPT natively. To translate a Polylang site with ChatGPT, Claude, or Gemini, you would need to use GPTranslate as the translation layer, which replaces Polylang’s own translation workflow entirely (though not necessarily its content structure, if you want to keep that).
See also: Full comparison: GPTranslate vs Polylang | GPTranslate vs WPML