Running a multilingual WordPress Multisite network introduces a layer of complexity that single-site installs never face: do you translate within each site in the network, or spin up a separate site per language? The multilingual plugin you choose needs a clear answer to that question before you build anything else.
Two Different Multisite Approaches
Multisite multilingual setups generally fall into one of two models. The first keeps a single site and translates its content into multiple languages using a standard multilingual plugin, same as any non-multisite install. The second uses Multisite itself as the language-separation mechanism, with each subsite representing one language and content synced or duplicated between them. Your plugin choice depends heavily on which model fits your organization’s actual workflow.
Weglot: The Simpler Path for Single-Site Translation
If your Multisite network uses separate sites for separate purposes (departments, brands, regions) rather than separate languages, Weglot can translate any individual site in the network independently, without needing network-wide configuration. Each site gets its own Weglot setup, translating automatically without touching the underlying database structure or requiring network administrator involvement for every change.
WPML: Built With Multisite Support From the Ground Up
WPML explicitly supports WordPress Multisite, including the ability to run multilingual content within individual subsites or to use subsites as language containers under WPML’s Multisite configuration options. For organizations that need granular control over how languages map to the network’s site structure, WPML’s documentation and support for this exact scenario makes it the most thoroughly tested option for complex Multisite multilingual builds.
TranslatePress: Workable Per-Site, Less Network-Aware
TranslatePress works well installed on an individual site within a Multisite network, giving that site’s editors the same front-end translation experience they’d get on a standalone install. It doesn’t offer specific network-wide management tools, so coordinating settings across many subsites means configuring each one individually rather than centrally.
Network-Wide vs. Per-Site Licensing
Licensing structure matters more on Multisite than almost anywhere else. Check whether your chosen plugin’s license covers the entire network or must be purchased per subsite — this can dramatically change the real cost of a multilingual rollout across a network with many subsites, and it’s a detail that’s easy to overlook until the invoice arrives.
Centralized vs. Decentralized Administration
Decide early who manages translation settings: a network administrator configuring things centrally, or individual subsite editors managing their own translation setup independently. This organizational decision matters as much as the technical plugin choice, since a plugin built for centralized control will frustrate decentralized teams, and vice versa.
Multisite Multilingual Checklist
- Decide whether languages map to subsites or live within a single site
- Confirm your plugin’s license covers your network’s actual subsite count
- Clarify who administers translation settings — network admin or individual subsite editors
- Test plugin behavior on a staging subsite before rolling out network-wide
- Plan for consistent SEO metadata translation across every subsite, not just your primary one
Final Thoughts
There’s no single best multilingual plugin for every Multisite network — the right choice depends entirely on whether your languages live within sites or across them. WPML’s purpose-built Multisite support makes it the safest default for complex network structures, while Weglot and TranslatePress both work well when you simply need to translate an individual site within a larger network without touching the network architecture itself.