Manage WordPress content by language

WP Multilang Premium manages translations for posts and post types, taxonomies, meta fields, options, multimedia text fields, menus, titles, widgets, and comments. Posts, terms, menus, widgets, and comments can be managed separately for each language without duplicate posts, terms, menus, or widgets. Translation processing runs in PHP, with REST support. The add-on also supports multisite and WordPress installations in a subfolder, without requiring a subdomain for each language or adding database tables.

Translation workflows

Premium features include automatic translation, URL slug translation, automatic slug translation where supported, and base translation for supported tasks. For external translation, export selected content in XLIFF or XML, complete the translation, then import it.

Language settings can cover multidimensional arrays in options, meta fields, and post content. Configure settings through JSON in wpm-config.json or use filters to apply them dynamically. A single localization can cover regional variations, and custom HTML locales such as en, en-UK, or en-AU can be set without installing another localization. Users with the manage_options capability can add languages. The Translator role can edit posts and terms but cannot publish or delete them.

WooCommerce and supported integrations

For WooCommerce, translate simple, variable, and grouped products, plus categories, tags, and global attributes. The add-on can synchronize carts across languages and send customer emails in the language selected by each customer.

Premium compatibility is listed for Elementor, Divi Builder, Bricks Builder, and Oxygen Builder. Other listed integrations include ACF and ACF Pro, Gutenberg, WooCommerce Customizer, Yoast SEO, SEOPress, Contact Form 7, WPBakery, SiteOrigin Page Builder, NextGEN Gallery, Rank Math SEO, WPGraphQL, Gravity Forms, Forminator Forms, Fluent Forms, Ultimate Member, BuddyPress, TablePress, and MailChimp for WordPress.

Compatibility can vary because plugins shop data differently. Some integrations, especially page builders, may need settings in wpm-config.json or filters to translate content or save translations correctly.

Set up and test

Install and activate the plugin, define the site languages, then configure the post types, fields, taxonomies, menus, widgets, products, and other content to translate. Before publishing a multilingual store, review product translations, language-specific categories and attributes, cart synchronization, and customer email language settings. Test the plugin in a staging environment and back up the website before activating it on an existing production site.