The short answer
For most Bangkok businesses with an English and a Thai version of the same pages, a single WordPress install with a translation plugin is the simpler and cheaper choice. One dashboard, one set of plugins, one backup, and each Thai page sits linked to its English twin.
Multisite earns its extra complexity in a narrower case: when the Thai and English sites are run by different teams, publish different content for different markets, or need separate plugins and user permissions. Two fully separate installs make sense only when the two sites have almost nothing in common. The rest of this guide explains why, with a comparison table and the SEO details that apply whichever route you take.
What WordPress Multisite is
Multisite is a feature built into WordPress that lets one installation run a network of sites. You switch it on in the configuration file, and the install becomes a network with shared core files, a shared plugin and theme library, and one database holding tables for every site.
The roles
A new role appears: the super admin, who manages the whole network, installs plugins and themes, and creates subsites. Each subsite still has its own administrators, who can activate the plugins and themes the super admin has made available but cannot install new ones.
Subdomains or subdirectories
When you set up the network you choose how subsites are addressed. A subdomain network gives addresses such as th.example.com. A subdirectory network gives example.com/th/. You pick once, at setup, and changing it later is a technical job rather than a setting. Subsites can also be mapped to entirely separate domains.
What is shared and what is not
Users are shared across the network, so one login can have roles on several subsites. Media libraries, posts, menus and settings are separate per subsite. That separation is exactly what makes Multisite attractive for independent markets and awkward for sites that should mirror each other.
Three ways to run English and Thai on WordPress
Multisite with a connector. Each language is a subsite, for example the main site in English and a Thai subsite at /th/. A connector plugin such as MultilingualPress links each page to its translation so the language switcher and hreflang tags work.
One site with a translation plugin. Polylang or WPML stores both languages in the same install and pairs each post with its translation. This is the common setup for a bilingual business site.
Two separate installs. Two independent WordPress sites, possibly on different hosts. Nothing is shared, and any links between languages are maintained by hand.
| Factor | Multisite | One site plus plugin | Two installs |
|---|---|---|---|
| Content independence | High: each subsite has its own pages and menus | Low: pages are paired by design | Total |
| Shared media and users | Users shared; media separate per subsite | Everything shared | Nothing shared |
| Plugin compatibility | Some plugins do not support networks | Standard WordPress; widest choice | Standard WordPress |
| Hosting | Needs a host that supports Multisite | Any WordPress host | Two sites to host |
| Backups and restores | One database, harder to restore one subsite alone | One site to back up | Two separate routines |
| Editorial workflow | Separate teams per language work well | One team translating side by side | Fully separate teams |
| Linking translations | Connector plugin | Built in | Manual |
SEO for two languages: hreflang and URLs
Search engines do not care which architecture you use. They care that each language version has its own URL, that the versions point to each other, and that each page is fully in one language. Our WordPress SEO guide covers the settings that apply either way.
hreflang
Google's guidance asks you to mark alternate language versions with hreflang annotations, and each version must list the others as well as itself. If the English page points to the Thai one but the Thai page does not point back, the pair can be ignored. Translation plugins and Multisite connectors write these tags for you, but only for pages you have linked as translations. An orphan Thai page with no English partner gets no tag.
URL structure
A subdirectory such as /th/ keeps both languages on one domain, which is simple to manage and to verify in Search Console. A subdomain works too. Whatever you choose, keep it consistent and never rely on cookies or browser language to swap content at the same URL, because a crawler sees only one version.
Duplicate content
A properly translated page is not duplicate content. The risk comes from half-translated pages, where the Thai version still carries English body text, or from auto-redirecting visitors by location. Translate the whole page, including titles, meta descriptions and image alt text, and let visitors choose their language.
When is Multisite the right call?
Multisite starts to pay off when at least two of these are true:
- Different teams own each language. A Thai marketing team and an English regional team who should not be able to edit each other's pages.
- Content genuinely differs by market. The Thai site promotes local offers, PromptPay checkout and Thai events, while the English site targets expatriates or overseas buyers with different products and pages.
- You expect more sites. A group planning further brands, branches or country sites that should share a code base and a login system.
- Different plugins per site. For example, an English site with a booking engine that the Thai site does not need.
A hypothetical example: a hotel group with a Thai-language site aimed at domestic weekend travellers and an English site for international guests, each run by a separate sales office. The pages would not mirror each other, and separate subsites keep each team inside its own lane.
When is Multisite overkill?
For a clinic, restaurant, law firm or trading company whose Thai and English pages say the same thing, Multisite adds work without adding value. You still have to translate every page, but now through two dashboards, with a connector plugin to keep in step and a network to administer.
Plugin support is the other cost. Many plugins work on a network, but some assume one site: licences may be priced per subsite, settings may need to be repeated, and a few simply do not support network activation. Before choosing Multisite, check each plugin on your list against that. Our guide to the essential WordPress plugins for a business site is a sensible starting list. Hosting and backups get harder too: some budget hosts do not support Multisite, and restoring one subsite from a shared database is not a one-click job.
Multisite belongs with other powerful setups that small sites rarely need. Running a headless WordPress front end is a similar case: impressive, occasionally right, and usually more than the business requires.
What goes wrong when you convert later?
You can turn an existing single site into a Multisite network, or split a bilingual single site into subsites, but neither is a quick switch. The usual problems:
- URLs change. Moving Thai pages from a plugin's /th/ structure to a subsite can change addresses. Every old URL needs a 301 redirect to its new home, or you lose the search visibility those pages built.
- Translation links break. The pairing a translation plugin stored is not understood by a Multisite connector. Each page pair has to be linked again.
- Media is duplicated. Images shared by both languages must be copied into each subsite's library.
- Plugins need rechecking. Anything not network-compatible has to be replaced before the move.
The lesson is to decide the architecture before content is written: deciding early costs one planning conversation, while deciding late costs a rebuild.
Planning your bilingual WordPress build
Cost follows the choice. A single install with a translation plugin is the setup we use for English and Thai websites built as one site, and our Business package, from THB 30,000 as an indicative one-time price, includes up to 15 pages in both languages on a custom WordPress theme.
Multisite adds setup and testing work, so it raises both the build quote and the ongoing maintenance effort. For a line-by-line picture, read how much a WordPress website costs in Bangkok. A typical project takes around 15 days from the agreed brief to launch; a network with several subsites needs more time, and the written quote says how much.
Our overview of running WordPress for a Thai business covers hosting, Thai fonts and local payment options. If you are still at the start, our general guide on how to build a website from plan to launch sets out the order of decisions, and the practical tutorial on setting up a WordPress website step by step shows where the translation plugin fits into the build.
Who reviewed this guide
Who builds your site
Litesh Dhir
Builds and ranks the websites: the systems behind the 17 client sites whose Search Console numbers we publish.
More about usMore on WordPress and bilingual sites
Sources
- WordPress Developer Resources: Multisite
- Google Search Central: Tell Google about localized versions of your page
- Google Search Central: Managing multi-regional and multilingual sites
- MultilingualPress on WordPress.org
- Polylang on WordPress.org