Polylang Pro
The Simplest Way to Build a Multilingual WordPress Site!
The more you get, the less you pay:
Polylang Pro is subject to a yearly license with a 50% renewal discount due to continuous improvements, updates, and professional support.

Rating
4.7/5 (2 827votes)
Current version
3.7.3
Last update
June 16, 2025
Active installations
+800.000
Expand your online presence globally with Polylang Pro. Translate every part of your site and switch between machine and manual translation.
Add a language switcher, optimize SEO, translate URLs, and enjoy dedicated professional support!
Polylang Pro is integrated into the WordPress interface for top-notch performance.
fits perfectly for:
Polylang Pro is suitable for beginners and experienced WordPress agencies. It offers user-friendly features and advanced customization options for designers and developers.
Are you building a multilingual WooCommerce site? Check out our Polylang for WooCommerce add-on.
Machine and Manual Translation
Polylang Pro significantly improves the way you translate your WordPress content.
- Machine translation (Integration with DeepL).
- Manual translation (Duplicate content across languages).
Translate Effortlessly
Manage the translations of your WordPress site in a few clicks.
- Pages, posts, categories and tags, custom post types.
- Translate menus and widgets.
- Full compatibility with the WordPress Site Editor and the blocks.
Multilingual SEO Support
Optimize your multilingual content to improve your global SEO presence.
- Hreflang tags.
- Choose between subdirectories, subdomains, or separate domains.
- Translate slugs in URLs.
- Language-dependent meta tags.
Key Features
Machine Translation with DeepL
Use the DeepL integration to translate for posts, pages, media, categories, tags, custom post types and custom taxonomies.
Manual Translation
Duplicate posts and pages across languages and translate everything manually, including media, widgets, and menus.
Flexible Language Switcher
You can easily switch between languages, add flags, and display your switcher anywhere on your site, such as menus, footers, and widgets.
Multilingual SEO
Polylang Pro automatically implements Hreflang and open graph tags to improve SEO.
Detect Browser Language
Detect and display content based on the user’s browser language preference.
Flexible Language URL configuration
Choose from subdirectories, subdomains, or separate domains for each language: “example.com/en/”, “en.example.com”, “example.fr”.
WooCommerce
You’ll need the power of Polylang Pro and our dedicated add-on “Polylang for WooCommerce” to translate your WooCommerce shop.
URLs Translation
Allow translations to share the same slug in the URL or translate slugs. And that’s great for SEO.
Block Editor and Site Editing Support
Full integration with the WordPress block editor and site editing functionalities.
XLIFF Import/Export
Streamline translation tasks with easy importing and exporting capabilities, ideal for translators.
Developer-Friendly
Compatibility with WPML API and REST API support, perfect for developers willing to expand Polylang.
Professional Support
Get professional assistance in English and French, from Monday to Friday. We’ve got you covered.
Compare Polylang Pro with other versions
|
Compare with From / yr |
From / yr |
||
---|---|---|---|---|
DeepL Machine Translation integration (Doesn't Work with Elementor and some builders) | ||||
Translate your content automatically in the post or page interface (in edition mode) |
Loading…
|
|
||
30 languages available with DeepL. Check your language’s availability |
Loading…
|
|
||
User-friendliness | ||||
Benefit from our intuitive interface |
Loading…
|
|
||
Easy start with our installation wizard |
Loading…
|
|
||
Translate your content | ||||
Translate posts, pages, media, categories, tags |
Loading…
|
|
||
Translate custom post types and custom taxonomies |
Loading…
|
|
||
Translate menus and widgets |
Loading…
|
|
||
Translations can share the same slug in the URL |
Loading…
|
|
||
Translate slugs in URLs (custom post types, taxonomies and more) |
Loading…
|
|
||
Duplicate the content when creating a translation |
Loading…
|
|
||
Synchronized posts to get the same content across translated posts, pages |
Loading…
|
|
||
Setup a multilingual website | ||||
Enable or disable languages |
Loading…
|
|
||
Add a language switcher |
Loading…
|
|
||
Use subdirectories, subdomains or separate domains |
Loading…
|
|
||
XLIFF Import/Export for pages, posts, media |
Loading…
|
|
||
Import/Export of strings translations in PO or XLIFF format |
Loading…
|
|
||
Other features and compatibilities | ||||
WPML API compatibility |
Loading…
|
|
||
Additional integration with ACF Pro |
Loading…
|
|
||
REST API Support |
Loading…
|
|
||
Site Editing support |
Loading…
|
|
||
Help and support | ||||
Access to the documentation and guides |
Loading…
|
|
||
Premium professional support |
Loading…
|
|
||
Standard support on wordpress.org |
Loading…
|
|||
Specific WooCommerce features | ||||
Translate products, categories, tags, global attributes |
Loading…
|
|||
Duplicate a product and its translations in 1 click |
Loading…
|
|||
HPOS ready |
Loading…
|
|||
Synchronisation of the cart across languages |
Loading…
|
|||
Synchronization of taxonomies, attributes, metadata across product translations |
Loading…
|
|||
Translate WooCommerce emails |
Loading…
|
|||
Translate WooCommerce pages (Shop, Cart, Checkout, My Account) |
Loading…
|
Do you have any questions?
-
Is Polylang GDPR compliant?
Since the version 4.9.6, WordPress allows to export personal data. This includes the biographical info. As Polylang and Polylang Pro allow the users to translate their biographical info, the translations are added to the exported data since the version 2.3.6.
None of our plugins collect other personal data.
-
Is Polylang compatible with the EU cookie law?
Polylang uses a cookie to remember the language selected by the user when he comes back to visit again the website. This cookie is also used to get the language information when not available in another way. Examples are ajax requests or the login page.
According to the section 3.6 of the Opinion 04/2012 on Cookie Consent Exemption, this cookie is part of the user interface customization and may be considered as requested by the user. Whether it requires the explicit consent of the user seems to depend on the expiration time or the information provided on your website. Moreover European countries have all their own law and do not apply the European directive the same way. Please check if this cookie requires an explicit user consent in your own country.
Here are the information about the cookie used by Polylang:
- Default name:
pll_language
, can be changed by setting the constantPLL_COOKIE
- Value: the language code of the last browsed page
- Default expiration time: 1 year, can be changed with the filter
pll_cookie_expiration
It is possible not to use the cookie (be aware however that in this case and as stated above, not everything will work correctly) by putting the code below for example in your wp-config.php file:
define( 'PLL_COOKIE', false);
- Default name:
-
Is Polylang compatible with multisite?
Yes it is. Polylang is fully tested in a multisite environment, activated at site level. It should also work when network activated but is not so well tested in this configuration. In most cases, it shouldn’t be useful to network activate Polylang. -
Do I need another license key for staging sites and localhost?
No. You can buy only one license key per public site and use it for localhost and your staging site. Your test site url has however to match:
- localhost
- localhost.localdomain
- 10.0.0.0/8
- 172.16.0.0/12
- 192.168.0.0/16
- *.dev
- *.local
- *.test
- dev.*
- staging.*
- sandbox.*
- *.wpserveur.net
- *.wpengine.com
- *.wptiger.fr
- *.myraidbox.de
- *.lndo.site
- *.go-vip.net
- *.kinsta.cloud
All URLs matching the rules above will not be counted against your limit of sites. If you have any problem, please contact our support.
-
What is the duration of a license key?
A license key is necessary to obtain the automatic updates and to access to the helpdesk support.
A license key is valid for one year as from the date of purchase. It may be renewed after one year at a preferential rate (currently 50% of the new license price). If a key is not renewed prior to its expiration, the plugin will continue to operate but you will no longer have access to automatic updates and helpdesk support.
It is recommended to run the latest version of WordPress, your theme and your plugins.
-
What is covered by the support?
Per our general terms and conditions of sale, the support includes the assistance with the installation and use of our plugins. It of course includes the correction of bugs. It does not include the resolution of conflicts with theme or third party plugins. It does not include writing personalized code to fix a problem. It does not include reviewing or fixing personalized code written by the client. No support will be due in the event of a modification of the plugin by the client.