Polylang

Description

With Polylang fully integrated to WordPress and using only its built-in core features (taxonomies), keep steady performances on your site and create a multilingual site featuring from just one extra language to 10 or more depending on your needs. There is no limit in the number of languages added and WordPress’ language packs are automatically downloaded when ready.

Features

Depending on the type of site you have built or are planning to build, a combination of plugins from the list below might be of interest.
All plugins include a wizard allowing to setup them in just a few clicks.

Polylang

Polylang and Polylang Pro share the same core providing features such as:

  • Translating posts, pages, media, categories, post tags, custom post types and taxonomies, RSS feeds; RTL scripts are supported.
  • The language is either set by the language code in URL, or you can use a different sub-domain or domain per language.
  • Automatic copy of categories, post tags and other metas when creating a new post or page translation.
  • Translating classic menus and classic widgets. Also accessible with Site Editor Classic Features in block themes.
  • Customizable language switcher available as a classic widget or a classic navigation menu item.
  • Compatibility with Yoast SEO.

Polylang Pro

Helps optimizing the time spent translating your site with some very useful extra features such as:

  • Better integration in the new Block Editor.
  • Language switcher available as a block.
  • Language options available in the widget block editor.
  • Template parts translatable in the site editor (FSE).
  • Duplicate and/or synchronize content across post translations.
  • Improved compatibility with other plugins such as ACF Pro.
  • Share the same URL slug for posts or terms across languages.
  • Translate URL slugs for categories, author bases, custom post types and more…
  • Machine translation with DeepL.
  • Export and import of content in XLIFF format for outsourced professional translation.
  • Access to a Premium Support for personalized assistance.

Polylang for WooCommerce

Add-on for the compatibility with WooCommerce which provides features such as:

  • Translating WooCommerce pages (shop, check-out, cart, my account), product categories and global attribute terms directly in the WooCommerce interface.
  • Translating WooCommerce e-mails and sending them to customers in their language.
  • Products metadata synchronization.
  • Compatibility with the native WooCommerce CSV import & export tool.
  • Compatibility with popular plugins such as WooCommerce Subscriptions, Product Bundles, WooCommerce Bookings, Shipment Tracking and more.
  • Ability to use the WooCommerce REST API (available with Polylang Pro).
  • Access to a Premium Support for personalized assistance.

Neither of them will allow to do automated translation.

Our other free plugins

  • WPML to Polylang allows migrating from WPML to Polylang.
  • DynaMo speeds up the translation of WordPress for all non-English sites.
  • Site Editor Classic Features allows to use classic widgets (including the Polylang language switcher) and menus in the site editor (FSE).

Credits

Thanks a lot to all translators who help translating Polylang.
Thanks a lot to Alex Lopez for the design of the logo.
Most of the flags included with Polylang are coming from famfamfam and are public domain.
Wherever third party code has been used, credit has been given in the code’s comments.

Screenshots

  • The Polylang languages admin panel
  • The Strings translations admin panel
  • Multilingual media library
  • The Edit Post screen with the Languages metabox

Installation

  1. Make sure you are using WordPress 6.2 or later and that your server is running PHP 7.0 or later (same requirement as WordPress itself).
  2. If you tried other multilingual plugins, deactivate them before activating Polylang, otherwise, you may get unexpected results!
  3. Install and activate the plugin as usual from the ‘Plugins’ menu in WordPress.
  4. The setup wizard is automatically launched to help you get started more easily with Polylang by configuring the main features.

FAQ

Where to find help ?

Is Polylang compatible with WooCommerce?

Reviews

11. Oktobar 2024.
Some details are not completly translated (in my case) like the forward/back navigation buttons on a blog. But that can be changed with little code knowledge.
10. Oktobar 2024.
I WAS RUNNED UP TRANSLATING MY PAGE WITH SEVERAL LANGUAGES, I’D BETTER OPT FOR AN AUTOMATIC ONE, ALL THE CONFIGURATION IS GOOD, EXCEPT FOR THE LANGUAGE MENU WHICH HAS TO ADD CSS TO CENTER IT AND ADJUST TWO PER ROW. ANOTHER THING IS THAT THE PERMANENT LINKS CROSS, MAINLY IN HOME, BECAUSE WHEN YOU PLACE PERMANENT IN ANOTHER LANGUAGE, IT IS DISABLED AND REMAINS AS DOMAIN.COM/EN/MAIN/. IT CAN BE CHANGED IN YOUR PERMANENT LINKS SETTINGS BUT IT IS CROSSED, THE SOURCE LANGUAGE IS LOST, DOMAIN.COM/ES/PRINCIPAL/ IS PLACED WHEN BEFORE IT WAS ONLY DOMAIN.COM NOTE: THE BAR AT THE END SHOULD ALSO BE REMOVED BUT IT CANNOT BE, IT IS LIMITED. THEN I SEE THAT THE REST WORKS WITH A NEW PAGE, WHICH IS GOOD FOR PERFORMANCE, BUT THE LINKS SHOULD BE IMPROVED.
9. Oktobar 2024.
It took me some time to set up the plugin correctly. Since then I have been very satisfied.
7. Oktobar 2024.
J’utilise le plugin depuis 1 mois pour traduire mon site à l’origine en Français, et avoir une traduction en anglais. Il est assez rudimentaire dans la version gratuite que j’utilise, mais avec un peu de temps de traduction manuelle j ‘ai traduit une bonne partie de mes pages et articles. Il est robuste, j attend de voir par rapport au référencement, si il permet un bon référencement sur les moteurs de recherches étrangers pour l’instant je n ai pas assez de recul pour. Le changement de langue par menu marche bien, L intégration avec l interface admin est top et facile J utilise avec Divi cela marche sans probleme
Read all 2.698 reviews

Contributors & Developers

“Polylang” is open source software. The following people have contributed to this plugin.

Contributors

“Polylang” has been translated into 52 locales. Thank you to the translators for their contributions.

Translate “Polylang” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Changelog

3.6.4 (2024-07-29)

  • Pro: Fix infinite loop with WP 6.6 when the locale fallbacks include the main locale of a language
  • Pro: Prevent saving the main locale among the locale fallbacks of a language
  • Pro: Hide the characters consumption graph when the DeepL cost control is deactivated
  • Add Yoast SEO social title and social description to the strings translations
  • Fix incorrect page on front and page for posts translations when the option is saved with admin language filter active

3.6.3 (2024-06-18)

  • Pro: Fix locale fallback for translations loaded just in time (requires WP 6.6)
  • Allow to pass an array as context to icl_register_string() #1497
  • Fix admin bar search menu in WP 6.6 #1496
  • Fix a regression in the usage of the filter pll_flag #1489

3.6.2 (2024-06-03)

  • Pro: Fix XLIFF files not correctly imported when exported from older version than 3.6
  • Pro: Fix translated categories not assigned to translated post when using machine translation
  • Pro: Fix ‘lang’ param not applied for secondary queries during a REST request
  • Pro: Fix newlines for content edited in classic editor and translated with DeepL
  • Pro: Fix a conflict with the Stream plugin on multisite

3.6.1 (2024-04-09)

  • Pro: Fix ACF fields not shown after a post was translated with DeepL
  • Remove rewrite when registering the language taxonomy #1457
  • Fix search block not filtered when displayed as button only #1459
  • Fix current language not kept when using switch_to_blog() in multisite #1458

3.6 (2024-03-18)

  • Requires WP 6.2 as minimum version
  • Add compatibility with WP 6.5
  • Pro: Add DeepL machine translation for posts
  • Pro: Add export and import in XLIFF 2.0/2.1 formats
  • Pro: Improve translator comments in exported PO files
  • Pro: Allow to export JSON encoded post and term metas in XLIFF files
  • Pro: Allow to export block sub-attributes in XLIFF files
  • Pro: Add footer notes block to XLIFF files
  • Pro: Single files are now exported directly instead of inside a zip
  • Pro: Reworked the language switcher navigation block
  • Pro: Fix language switcher navigation block justification not aligned with core settings in overlay menu (requires WP 6.5)
  • Pro: Fix a race condition which could lead to display a notice to the wrong user
  • Pro: Fix a conflict with ACF when rewrite rules are flushed with WP-CLI on a multisite
  • Pro: Fix import of several metas with same sources but different translations
  • Add filter pll_cookie_args to filter the Polylang cookie arguments #1406
  • Fix wrong translated post types and taxononies after a switch_to_blog() #1415
  • Fix a minor performance issue for the page for posts #1412
  • Fix a JS errors after quick edit. Props @mcguffin #1435, #1444
  • Fix a possible warning in view-translations-post.php #1439

See changelog.txt for older changelog