Get the ultimate WordPress multilingual solution
Unlock the power of Polylang with our flexible pricing options designed to cater to your specific needs. Whether you’re an advanced user, an e-commerce
4.7/5 on wordpress.org (2890 votes)
Polylang Pro
from
/ year
(ex VAT)
- 1 year of updates and premium support
- Multisite license option available
- 50% renewal discount
addon Polylang for WooCommerce
from
/ year
(ex VAT)
- 1 year of updates and premium support
- Multisite license option available
- 50% renewal discount
Polylang Business Pack
from
/ year
(ex VAT)
- 1 year of updates and premium support
- Multisite license option available
- 50% renewal discount
Or get the free Polylang plugin on wordpress.org
Which Polylang version do you need?
|
|
From / yr |
From / yr |
From / yr |
|
|---|---|---|---|---|
| DeepL Machine Translation integration | ||||
| Translate your content automatically in the post or page interface (in edition mode) ⚠️ Not compatible with Elementor |
|
|
||
| 30 languages available with DeepL. ⚠️ Check your language’s availability on DeepL’s website |
|
|
||
| User-friendliness | ||||
| Easy start with our installation wizard |
|
|
|
|
| Benefit from our intuitive interface |
|
|
|
|
| Translate your content | ||||
| Translate posts, pages, media, categories, tags |
|
|
|
|
| Translate custom post types and custom taxonomies |
|
|
|
|
| Translate menus and widgets |
|
|
|
|
| Translations can share the same slug in the URL |
|
|
||
| Translate slugs in URLs (custom post types, taxonomies and more) |
|
|
||
| Duplicate the content when creating a translation |
|
|
||
| Synchronized posts to get the same content across translated posts, pages |
|
|
||
| Setup a multilingual website | ||||
| Use subdirectories, subdomains or separate domains |
|
|
|
|
| Add a language switcher |
|
|
|
|
| Enable or disable languages |
|
|
||
| XLIFF Import/Export for pages, posts, media |
|
|
||
| Import/Export of strings translations in PO or XLIFF format |
|
|
||
| Specific WooCommerce features | ||||
| Translate products, categories, tags, global attributes |
|
|
||
| Translate WooCommerce pages (Shop, Cart, Checkout, My Account) |
|
|
||
| Translate WooCommerce emails |
|
|
||
| Duplicate a product and its translations in 1 click |
|
|
||
| Synchronization of taxonomies, attributes, metadata across product translations |
|
|
||
| HPOS ready |
|
|
||
| Synchronisation of the cart across languages |
|
|
||
| Other features and compatibilities | ||||
| WPML API compatibility |
|
|
|
|
| Additional integration with ACF Pro |
|
|
||
| REST API Support |
|
|
||
| Site Editing support |
|
|
||
| Help and support | ||||
| Standard support on wordpress.org |
|
|
|
|
| Access to the documentation and guides |
|
|
|
|
| Premium professional support |
|
|
|
|
|
|
From / yr |
From / yr |
From / yr |
|
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:
-
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.
-
What is your refund policy?
If you have problems getting your purchased plugin to work, we will be happy to provide a full refund within 30 days of the original purchase.
Before a refund will be granted, you must allow us to try to solve your problem by opening a support ticket.
After 30 days, no refunds will be given.
Refunds do not apply to license upgrades or renewals.