Polylang allows you to create a bilingual or multilingual WordPress site. You write posts, pages and create categories and post tags as usual, and then define the language for each of them. The translation of a post, whether it is in the default language or not, is optional.

  • Je kunt zoveel talen gebruiken als je wilt. RTL taalscripts worden ondersteund. WordPress taalpakketten worden automatisch gedownload en geüpdatet.
  • Je kunt berichts, pagina’s, media, categorieën, berichttags, menu’s, widgets… vertalen.
  • Aangepaste berichttypen, aangepaste taxonomieën, vastgezette berichten en berichtformaten, RSS-feeds en alle standaard WordPress-widgets worden ondersteund.
  • De taal wordt bepaald door de inhoud of door de taalcode in url, of je kunt een ander subdomein of domein per taal gebruiken
  • Categories, post tags as well as some other metas are automatically copied when adding a new post or page translation
  • A customizable language switcher is provided as a widget or in the nav menu

The author does not provide support on the wordpress.org forum. Support and extra features are available to Polylang Pro users.

Als je wil migreren van WPML kun je de plugin WPML to Polylang gebruiken

Als je gebruik wenst te maken van een professionele of automatische vertaaldienst kun je Lingotek Translation installeren als een add-on van Polylang. Lingotek biedt een compleet vertaal managementsysteem dat diensten aanbiedt zoals vertaalgeheugen of semi-geautomatiseerde vertaalprocessen (b.v. machine vertaling > menselijke vertaling > beoordeling op legaliteit).


Veel dank aan alle vertalers die helpen om Polylang te vertalen.
Veel dank aan Alex Lopez voor het ontwerp van het logo.
De meeste vlaggen die bij Polylang zijn inbegrepen komen vanfamfamfam en zijn publiek domein.
Waar derde partij code gebruikt is, wordt credit gegeven in de comments van de code.

Vind je Polylang leuk?

Aarzel niet om je feedback te geven.


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


  1. Make sure you are using WordPress 5.1 or later and that your server is running PHP 5.6 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. Installeer en activeer de plugin als gebruikelijk vanuit het ‘Plugins’ menu in WordPress.
  4. Go to the languages settings page and create the languages you need
  5. Add the ‘language switcher’ widget to let your visitors switch the language.
  6. Take care that your theme must come with the corresponding .mo files (Polylang automatically downloads them when they are available for themes and plugins in this repository). If your theme is not internationalized yet, please refer to the Theme Handbook or ask the theme author to internationalize it.


Where to find help ?

Is Polylang compatibel met WooCommerce?

  • Je hebt een aparte add-on nodig om Polylang en WooCommerce samen te laten werken. Er is een Premium add-on beschikbaar.

Heb je vertaaldiensten nodig?

  • If you want to use professional or automatic translation services, install and activate the Lingotek Translation plugin.


18 september 2021
I love the plugin. It is pretty straightforward. Thanks for creating it!
17 september 2021
If you upgrade your site from a wordpress version older than 5.8 you can lost all your widgets, as the language selector is not available for free version of this plugin in the new block widget editor.
15 september 2021
Easy to use, and not complicated to start with, it is doing the job.
9 september 2021
It is easy to use and works great for posts and pages. It's not always working great with frontpage and/or other widget areas. It often translate sme parts of the widget, but not everything. My website is in Dutch and I use Polylang to translate it to English, but then there are still small parts in the sidebar, footer or front page that will stay Dutch, which looks a bit unprofessional. But I use the free version, and it's working great for the blogs and pages on my website. And also works good with Complianz, my portfolio and most of the other plugins I'm using.
6 september 2021
A friend of mine has a small website based on WordPress v5.8. He uses Elementor / Elementor Pro. Everything is in German language. He wants to present the whole contents of his website also in English and Russian. Translation of texts will be done by native speakers, not by automated translation. We are looking for a (simple) WP plug-in to achieve a multi-language website supporting at least 3 languages (German [standard], English and Russian). The required plug-in should support Elementor and Elemetor Pro, and ideally also Gutenberg (however not mandatory), but we plan to deploy Gutenberg as a replacement for Elementor (Pro) in about 2 years. The plug-in should provide a language switcher so that visitors can select their desired language. If possible, the WP plug-in should allow for further languages, although currently not required. For the beginning the WP plug-in should be FREE software and should fulfill the above mentioned requirements. A PRO version is planned later on. I understand that there is a FREE version of PolyLang. Does the FREE version support all the features mentioned above? (I went through the documentation but could not find clear answers.) Best regards Dieter
Lees alle 2.041 beoordelingen

Bijdragers & ontwikkelaars

“Polylang” is open source software. De volgende personen hebben bijgedragen aan deze plugin.


“Polylang” is vertaald in 45 talen. Dank voor de vertalers voor hun bijdragen.

Vertaal “Polylang” naar jouw taal.

Interesse in ontwikkeling?

Bekijk de code, haal de SVN repository op, of abonneer je op het ontwikkellog via RSS.


3.1.1 (2021-08-16)

  • Pro: Fix a fatal error with The Events Calendar
  • Allow to remove the cookie with the pll_cookie_expiration filter #905

3.1 (2021-07-27)

  • Add compatibility with WordPress 5.8
  • Raise Minimum WordPress version to 5.4
  • Pro: Allow to filter blocks by language in the widget block editor
  • Pro: Allow to export and import XLIFF files for string translations
  • Pro: Add the language switcher in the navigation block (experimental)
  • Pro: Replace dashicons by svg icons in the block editor
  • Pro: The Events Calendar: Add compatibility with Views V2 (only for sites using only one domain)
  • Pro: Fix + icon displayed in the block editor sidebar when the user cannot create a translation
  • Add a warning section to the site health for posts and terms without languages #825
  • Require the simplexml extension in the site health if a wpml-config.xml is found #827
  • Remove the information about the WPML compabitility mode in settings #843
  • The browser preferred language detection is now deactivated by default
  • The media are now untranslated by default
  • Highlight the language filter in the admin toolbar when it’s active #821
  • Allow to query comments in multiple languages (just as posts and terms) #840
  • Don’t disable the translation input field in the classic metabox #841 Props Onatcer
  • Optimize all images including flags #848 Props lowwebtech
  • Don’t redirect if WordPress doesn’t validate the redirect url to avoid redirects to /wp-admin/ #879
  • Fix media appearing to have a language after the language is changed in the media library grid view #807
  • Fix media not all deleted when bulk deleting from the grid view of the media library #830
  • Fix when more than one language switcher are added to the same menu #853
  • Fix PHP notice when adding a CPT archive link to a menu #868 Props davidwebca

3.0.6 (2021-06-22)

  • Fix a conflict with the WooCommerce cart translation and cache plugins #876

3.0.5 (2021-06-08)

  • Pro: fix original post not assigned to a new translation when the languages sidebar is closed
  • Pro: Attempt to fix zip file corrupted on some installations when exporting string translations
  • Support session cookie with the pll_cookie_expiration filter #835
  • Fix javascript error when a plugin defines its own editor for translated post types #837
  • Fix languages displayed in screen options when editing a term #850
  • Cache: fix post type archive cache not cleared when saving a post #828

3.0.4 (2021-04-27)

  • Improve performance in the pages (or hierarchical post types) list table
  • Fix an ajax conflict with WooCommerce License manager

3.0.3 (2021-03-23)

  • Fix a warning when a language is corrupted in database (term_language missing)
  • Fix confirmation modal with WooCommerce and WordPress < 5.6
  • Fix an ajax conflict with WooCommerce Tree Table Rate Shipping and HubSpot All-In-One Marketing

3.0.2 (2021-03-16)

  • Move hreflang attributes higher in the head section #771
  • Fix custom flags not working (introduced in 3.0)
  • Fix translation of the confirmation modal when changing the language of a post
  • Fix js and css not loaded when Polylang is used as a mu-plugin (introduced in 3.0)
  • Fix support for html5 stylesheet link tags #775
  • Fix possible warning in frontend-filters-links.php
  • Yoast SEO Premium: Take over the multilingual compatibility removed in Yoast SEO Premium 15.8 #796
  • Yoast SEO: Fix CPT breadcrumb title when the option is left empty #794
  • Yoast SEO: Fix sitemap.xml not redirected on secondary domains #789

3.0.1 (2021-03-10)

  • Fix media gallery messed when editing a post in the classic editor
  • Fix missing script dependency on old WP versions
  • Fix CSS conflict with WooCommerce Bookings for WP < 5.6
  • Fix conflict resulting in ‘__’ already defined in block-editor.js. #779
  • Fix search form removed for some themes. Props Marián Kadaňka. #780
  • Fix fatal error with very old versions of Yoast SEO. Props Nicola Peluchetti. #781

3.0 (2021-03-08)

  • Add compatibility with WordPress 5.7
  • Remove upgrades from Polylang older than 1.8
  • Remove deprecated class PLL_Pointer
  • Pro: Hide the license keys
  • Pro: Fix redirect to the home page of a deactivated language
  • Pro: Fix synchronization of post status not working
  • Pro: Fix language switcher block not working in a post retrieved in REST API
  • Pro: Fix PO export of strings with line breaks
  • Pro: Fix file block title customization lost
  • Add a dialog box to ask a confirmation about a language change in classic and block editors
  • Improve browser language detection #591
  • Improve robustness and documentation of code
  • Fix media library after the language has been chnaged in the editor metabox
  • Fix duplicated title attribute on flag link in posts list
  • Fix legacy block editor language metabox compatibility with WordPress 5.6
  • Fix uploaded theme and plugin files in media library
  • Fix site title not translated in email change confirmation email
  • Fix remaining deprecated jQuery notices #741
  • Fix compatibility with GN publisher
  • Fix compatibility with Woodmart theme search form
  • Fix compatibility issue with 3rd party ajax requests since jQuery 3.3 #744
  • Fix CSS conflict with WooCommerce Bookings
  • Fix browser error when displaying an embed and using a cache plugin #757
  • Fix post type archive title and metadesc not translated in Yoast SEO
  • Fix PHP notice in REST API

See changelog.txt for older changelog