What is MultilingualPress plugin?
MultilingualPress takes a fundamentally different technical approach to WordPress multilingualism compared to WPML, Polylang, and TranslatePress. Rather than storing translations alongside original content in the same WordPress installation, MultilingualPress uses WordPress Multisite — each language gets its own separate WordPress site within a multisite network. A German version of your site is a distinct WordPress installation at /de/ (or de.yourdomain.com), containing only the German content, linked to the English original via relationship metadata.
This architecture provides significant performance advantages: each language site loads only its own content, with no translation lookup overhead on every page request. For multilingual sites with large content libraries where performance is critical, the multisite approach scales better than single-installation plugins that accumulate translation metadata. Each language site also has its own WordPress settings, plugins, and even theme — useful for sites where layout or functionality differs by region.
MultilingualPress is a premium plugin (pricing from the inpsyde.com marketplace) requiring WordPress Multisite, which adds setup complexity compared to single-site plugins. It is best suited for developers and agencies building high-performance multilingual WordPress networks rather than site owners looking for a quick translation solution. For most standard multilingual requirements, WPML, Polylang, or TranslatePress are simpler choices. For performance-critical multilingual sites or agencies managing large multilingual networks, MultilingualPress’s architecture provides advantages that single-site plugins cannot replicate.
Need Help With MultilingualPress Setup, Troubleshooting, or Customization?
Need help with MultilingualPress? Whether you are dealing with errors, broken functionality, styling problems, plugin conflicts, or advanced customization, we can help you fix the issue and get the plugin working properly on your WordPress site.
Get MultilingualPress Expert HelpKey Features
- WordPress Multisite architecture — one site per language
- Zero translation lookup overhead — each site serves its own content only
- Content relationship linking between language sites
- Hreflang SEO tags across network sites
- Language switcher (posts, pages, custom post types)
Pros & Cons
Pros
- Best performance of any multilingual approach — no database overhead per page request
- Full data separation by language — each site is independently scalable
- Language-specific plugin and theme configuration
Cons
- Requires WordPress Multisite — more complex server and WordPress configuration
- Higher setup and maintenance complexity than single-site multilingual plugins
Free vs Premium
No free version. Premium licensing from inpsyde.com — pricing on their website. Trial available.
Common Problems & Fixes
MultilingualPress language relationships are broken — editing a post on one site does not show the connected translation on the other. How do I fix this?
Language relationships in MultilingualPress are stored in a shared database table (wp_mlp_content_relations). If relationships appear broken, check: (1) the MultilingualPress plugin is active on all sites in the network — network-activate it via the Network Admin; (2) go to Network Admin → MultilingualPress → Relationships and run the relationship integrity check to identify orphaned or broken links; (3) if relationships were damaged by a migration or database export/import that did not include the MultilingualPress tables, recreate the relationships manually by editing each post and setting the translation in the MultilingualPress Translation Meta Box.
Hreflang tags are not appearing on MultilingualPress sites — search engines are not recognizing the language relationship. How do I add them?
MultilingualPress adds hreflang tags automatically when connected content relationships exist between sites. If hreflang tags are missing: (1) ensure content relationships are correctly configured (each post/page linked to its translation on other network sites); (2) verify the language assignment for each site in Network Admin → Sites → [site] → Settings → MultilingualPress; (3) check if a conflicting SEO plugin is removing or overriding MultilingualPress hreflang output — Yoast SEO and Rank Math have their own hreflang handling that may conflict.
A plugin that works correctly on a single WordPress site is behaving incorrectly on a MultilingualPress network. How do I resolve compatibility issues?
Not all WordPress plugins are Multisite-compatible. Check the plugin’s documentation for multisite support. Common issues: (1) plugin stores site-specific options in the wrong table (wp_options vs wp_[site_id]_options) — database prefixes differ per site in multisite; (2) plugin hardcodes site URL assumptions that break in a subdirectory multisite; (3) plugin uses network-level caching that conflicts across sites. Contact the plugin developer about multisite compatibility or test with a staging network to identify the conflict source.
Customization & Developer Notes
How do I copy content from the source language site to a translation site as a starting point?
MultilingualPress includes a content duplication feature. When editing a post on the source site, the MultilingualPress Translation Meta Box shows all connected sites. Click “Duplicate content to [language site]” to copy the post content to the translation site. The copied content retains the original language text as a starting point — the translator then edits this on the translation site and replaces it with the translated version. This is faster than creating each translated post from scratch.
How do I configure WooCommerce product translation across MultilingualPress network sites?
With the WooCommerce add-on for MultilingualPress, enable WooCommerce on all language network sites and connect product relationships between sites as you would for standard posts. In the product edit screen, the MultilingualPress meta box shows the connected products on other language sites. Product variations, attributes, and prices are managed independently on each site — translation is not automatic and each language site’s WooCommerce catalog is separate. This approach allows different pricing or product availability per language market if needed.
Frequently Asked Questions
When should I choose MultilingualPress over WPML?
Choose MultilingualPress when: performance is a primary concern and your content library is large enough that WPML’s per-page query overhead is measurable; you need each language site to have distinct plugin configurations or themes; you manage a network of high-traffic multilingual sites and need horizontal scaling. Choose WPML when: setup simplicity is valued over performance optimization; you need all translations managed within a single WordPress installation; your team is not comfortable with Multisite administration.
Can MultilingualPress be used on a regular (non-multisite) WordPress installation?
No — MultilingualPress requires WordPress Multisite. It cannot be used on a standard single-site WordPress installation. If WordPress Multisite is not configured or not supported by your hosting, use WPML, Polylang, or TranslatePress as single-site multilingual alternatives.
Can MultilingualPress break after updates?
Yes, that can happen, especially on older sites with many plugins. This usually happens when the plugin, theme, and add-ons are updated out of sequence. In most cases, testing on staging catches the issue before it reaches the live site. From experience, backups and changelog reviews save a lot of cleanup time.
What should I check before installing MultilingualPress?
Start by checking whether another plugin already does the same job. In most cases, overlap is what creates avoidable conflicts and performance issues. A common issue is installing a plugin because it looks convenient without checking the stack first. From experience, a short compatibility review avoids most of the pain later.