Polylang Pro

Overview

Polylang Pro is a multilingual WordPress plugin for site owners who want translations managed within the familiar WordPress editing workflow. Administrators can define languages, associate translations for posts, pages, taxonomies, and custom post types, and expose language choices through switchers and multilingual navigation. Pro-specific workflows also cover translated slugs, locale fallback, language deactivation, selected translation capabilities, and REST API access.\n\nThe practical setup depends on the site’s theme and content stack. Block-theme users can translate Site Editor patterns, template parts, and navigation elements, but the documentation notes that templates themselves are not translated; an untranslated template part may therefore appear across languages. Teams should also confirm how their theme, page builder, custom fields, SEO tooling, and forms handle language-specific content. Polylang’s own pricing documentation states that Polylang or Polylang Pro alone is not sufficient for a multilingual WooCommerce shop, so an ecommerce implementation should be tested with the dedicated WooCommerce extension on a staging site before production changes are made.

Compatibility and setup context

• Site Editor navigation and related Pro workflows require a block theme and Polylang Pro 3.8 or later.
• Site Editor content can include translatable patterns and template parts, but WordPress templates themselves are not translated by Polylang Pro.
• Custom post type and taxonomy translation follows the same general language-assignment workflow as posts and pages, but the site’s registration and builder integrations should be tested.
• WooCommerce requires the separate Polylang for WooCommerce extension; Polylang Pro alone is not sufficient for a multilingual shop.
• Translation permissions can be assigned to selected roles and languages, while Site Editor patterns, navigation, and templates have documented capability limitations.

Product Details