WordPress Multisite lets one WordPress installation run multiple sites, which some organizations use specifically for multilingual setups, one subsite per language, alongside more common uses like managing multiple brands or regional divisions from a single installation. Translating content across a Multisite network raises questions a single-site translation setup does not: does each subsite get translated independently, or does content flow from a primary site to language-specific subsites automatically?
Two Ways Multisite Gets Used for Multilingual Content
Some networks use one subsite per language deliberately, with a plugin or manual process syncing content from a primary language subsite to the others. Other networks use Multisite for unrelated reasons, multiple regional brands, a network of client sites, and simply need each subsite translated into its own relevant language independently, without any content relationship between subsites. The right translation approach differs meaningfully between these two patterns.
Translating a Language-per-Subsite Network
When subsites are explicitly organized by language, translation needs to flow from the primary content subsite to each language subsite, ideally automatically when content changes, following the same incremental translation logic used for single-site multilingual setups, just applied across a network boundary instead of within one site’s post table. Shared elements, plugins, some theme settings, network-wide announcements, need a clear policy for whether they are translated per subsite or intentionally left uniform.
Translating Independent Subsites
When subsites are independent, each one is translated on its own terms, similar to running translation separately on multiple unrelated single-site WordPress installations, just managed from one network admin. This is generally simpler, since there is no cross-subsite content relationship to maintain, but it does mean translation configuration, target languages, formality settings, model selection, needs to be set per subsite rather than assumed to be uniform across the network.
Shared vs Subsite-Specific Content
- Network-activated plugins: function the same across subsites, but plugin-generated front-end text still needs per-subsite translation.
- Shared media library (if configured): image files are shared, but alt text and captions may need to be subsite-specific.
- Per-subsite content: posts, pages and custom post types are stored per subsite and translated independently for each one.
How GPTranslate Handles Multisite Networks
GPTranslate can be configured per subsite, so a language-per-subsite network can sync translated content from a primary subsite, while a network of independent subsites can each run their own translation configuration and target languages without interference between subsites.
Frequently Asked Questions
Is Multisite necessary for a multilingual WordPress site?
No, most multilingual sites run on a single WordPress installation with language variants managed within it; Multisite is one architectural option among several, not a requirement for multilingual functionality.
Can translation settings differ between subsites in the same network?
Yes, each subsite can have its own translation configuration, including target languages and AI model preferences, independent of other subsites in the network.
Conclusion
Translating a Multisite network starts with understanding which pattern is in play, language-organized subsites needing synced content, or independent subsites each needing their own translation setup. Getting this distinction right before configuring translation avoids building a workflow that assumes a content relationship between subsites that does not actually exist, or missing one that does.