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.
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 install them in just a few clicks.
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 menus and widgets.
- Customizable language switcher available as a widget or a navigation menu item.
- Compatibility with Yoast SEO
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 Full Site Editing (FSE).
- Duplicate and/or synchronize content across post translations.
- Improved compatibilities with other plugins such as ACF Pro.
- Share the same URL slug for posts or terms across languages.
- Translate URLs slugs for categories, author bases, custom post types and more…
- 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. Nevertheless, can be isntalled alongside Polylang Pro or Polylang, a third party plugin such as Lingotek Translation which offers a complete translation management system and provides services such as a translation memory or semi-automated translation processes (e.g., machine translation => human translation => legal review).
Migrating from WPML is possible using the plugin WPML to Polylang.
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.
- Make sure you are using WordPress 5.6 or later and that your server is running PHP 5.6 or later (same requirement as WordPress itself).
- If you tried other multilingual plugins, deactivate them before activating Polylang, otherwise, you may get unexpected results!
- Install and activate the plugin as usual from the ‘Plugins’ menu in WordPress.
- The setup wizard is automatically launched to help you get started more easily with Polylang by configuring the main features.
Where to find help ?
- First time users should read Polylang – Getting started, which explains the basics and includes a lot of screenshots.
- Read the documentation. It includes a FAQ and the documentation for developers.
- Search the community support forum. You will probably find your answers here.
- Read the sticky posts in the community support forum.
- If you still have a problem, open a new thread in the community support forum.
- Polylang Pro and Polylang for WooCommerce users have access to our premium support through helpdesk.
Is Polylang compatible with WooCommerce?
- You need Polylang for WooCommerce, premium addon described above, which will make both plugins work together.
Do you need translation services?
- If you want to use professional or automatic translation services, install and activate the Lingotek Translation plugin.
Contributors & Developers
“Polylang” is open source software. The following people have contributed to this plugin.Bidragsydere
- Pro: Fix creation of WC product categories with shared slug via REST API
- Pro: Fix conflict with WooBuilder when editing a WC product
- Fix: Force empty string translation to empty string #1058
- Fix CSS conflict with Dynamic content for Elementor #1060
- Pro: Remove “Navigation menus” from the post type settings list
- Pro: Fix block editor languages panel missing in WordPress 5.6
- Pro: Fix wrongly indexed languages list returned by REST API when the first language is deactivated.
- Revert fix for category feed not redirected when the language code is wrong #1054
- Fix wrong redirect of category when the url includes a query string #1048
- Fix querying multiple categories failing
- Pro: Fix a fatal error when inserting a term
- Pro: Fix translation of the block cover when duplicating a post
- Pro: Fix a CSS issue in bulk tranlate form introduced by WP 6.0
- Pro: Fix a CSS issue in string import/export metaboxes.
- Prevent random languages order in WP 6.0 #1041
- Translate site title in retrieve password email #1042
- Fix ‘lang’ attribute in language widget dropdown #1039
- Pro: Fix redirect occuring for tags sharing the same slug as their translations
- Fix quick edit allowing to modify the language of the default category when it should not #1018
- Pro: Fix users with editor role not able to save or publish posts
- Pro: Fix FSE compatibility not loaded when the plugin Gütenberg is active
- Pro: Fix a fatal error occuring with Yoast SEO Premium
- Pro: Fix a fatal error with ACF when no language is defined
- Requires WP 5.6 as minimum version
- Pro: Add compatibility with the full site editing introduced in WP 5.9
- Pro: Add a language switcher block for the navigation block introduced in WP 5.9
- Pro: Add compatibility with the new gallery block introduced in WP 5.9
- Pro: Make the language switcher block available in the widget section of the customizer
- Pro: Fix wrong category when translating the latest posts block
- Pro: Fix the language switcher block when using the dropdown option
- Pro: Fix some edge cases with locale fallback
- Pro: Fix post template replacing the post content when duplicating a post
- Pro: Fix synchronization groups not correctly cleaned up when a language is deleted
- Pro: Fix incorrect sticky property when duplicating / synchronizing posts
- Pro: Fix “Page for posts” label after the page has been bulk translated
- Pro: Fix translated slug when the url includes a query string
- Pro: Synchronize ACF layout fields if a child field is synchronized or translatable
- Pro: Fix wrong field group translation displayed when using object cache with ACF
- Update plugin updater to 1.9.1
- Add compatibility with the block site title introduced in WP 5.9
- Add the list of wpml-config.xml files in the site health information
- Improve the performance of the get_pages() filter #980
- Improve the compatibility of ‘wpml_object_id’ with the original filter #972
- Prevent term_exists to be filtered by language in WP 6.0
- Fix some PHP 8.1 deprecations #949 #985
- Fix a fatal error in PHP 8.1 #987
- Fix category feed not redirected when the langage code is wrong #887
- Fix default category not created for secondary languages (introduced in 3.1) #997
- Fix parent page when the parent post type is not translatable #1001
- Fix the Yoast SEO breadcrumb when it includes a non-synchronized taxonomy #1005
- Fix a PHP Notice when adding a new language and Yoast SEO is active #979
- Fix a PHP warning in Yoast SEO compatibility #954
See changelog.txt for older changelog