Table of Contents
What Vendors Actually Build
A multilingual WordPress site is not a single feature — it is a set of decisions about URLs, data storage, editor workflow and output tags, made once and then expensive to revisit. Vendors at different price points build genuinely different things under the same label.
At the low end, “multilingual” means installing a translation plugin, adding a language switcher, and letting editors copy content between languages. At the top end it means designing how locale data is stored, how translations move through a release pipeline, and how each locale is annotated so search engines understand which version to serve to whom.
The practical question is not “does it support multiple languages” — every option does — but “what happens when I add the sixth language, and who fixes it when the switcher breaks”.
Vendor Option Comparison
| Option | Budget (2026) | Deliverables |
|---|---|---|
| Freelance plugin setup | $1,200–$3,500 | 2 languages, basic hreflang, no custom blocks |
| Agency WPML build | $4,000–$12,000 | 5 languages, SEO architecture, editor training |
| Custom headless i18n | $18,000–$45,000 | Unlimited locales, API translation, CI sync |
| Redesign + multilingual | $9,000–$25,000 | New theme, 4 languages, migration |
The step from freelance setup to an agency build is mostly about architecture and training: an SEO-aware URL structure, and editors who know how to publish without breaking it. The step from agency to custom headless is about automation: translation flowing through an API and a CI pipeline instead of being pasted by hand.
Most businesses are best served by the agency tier. Custom headless i18n earns its cost when locale count grows past the point where manual coordination is viable, or when translations already live in a translation management system that should be the source of truth.
How to Evaluate Architecture
Three technical decisions determine whether a multilingual site stays manageable. Ask about all three before signing anything.
URL Strategy
The main patterns are subdirectories (/en/, /de/), subdomains, separate domains per country, and query parameters. Subdirectories are the safest default: they consolidate authority on one domain, are simple to configure in Search Console, and behave predictably with caching and CDN rules.
Get a Quote
Email + requirement + budget range — we reply with a quote within 24 hours.
Whichever pattern you choose, decide it before launch. Changing URL structure later means redirects across every page in every language — the most expensive rework in multilingual projects.
Translation Storage
Translations can live in the same posts table with per-language rows, in separate posts per language, or outside WordPress entirely in a translation management system. Each has consequences:
- Same table, linked rows — easiest for editors, keeps one canonical post, but couples your content to the plugin’s schema.
- Separate posts per language — maximum flexibility and clean exports, at the cost of more editorial housekeeping.
- External TMS — best for large teams and continuous localisation, but requires sync engineering and a clear answer to “which side wins on conflict”.
Hreflang Output
hreflang tells search engines which language and region each URL targets. It must be reciprocal — if the English page points at the German page, the German page must point back. One-directional annotations are ignored, and missing self-references are a common silent failure.
Verify after launch rather than assuming. The check is simple: load a page in each language and confirm the tags exist, point at each other, and include a self-reference plus an x-default fallback for unmatched locales.
Step-by-Step WordPress Multilingual Website Setup
- Decide the locale list. Language plus region where it matters —
en-USanden-GBare different targets. Write the list down and freeze it. - Choose the URL pattern and configure the server, CDN and caching to respect it. Test that each locale serves the correct content from cache.
- Install and configure the translation layer, including which content types are translatable and which are shared.
- Define translatable vs shared fields. Product names and body copy translate; SKUs, prices and specification tables often do not — but currency and units usually do.
- Build the language switcher into the theme rather than bolting it on, so it works on every template including archives and search results.
- Translate and review. Machine translation for drafts, human review for anything that sells.
- Generate per-language sitemaps and confirm every locale is covered.
- Verify hreflang reciprocity and x-default across a representative sample of pages.
- Check performance per locale. A translation plugin adds queries; measure the slowest locale, not the fastest.
- Train editors and document the publishing workflow, including what to do when only some languages are ready.
What Translation Actually Costs
Translation is the line item most budgets underestimate, because it recurs with every new page. Machine translation is effectively free but needs review; professional translation is priced per word and varies by language pair and subject matter.
Two rules keep this under control: only translate what earns its keep in that market, and treat translation as an ongoing content cost rather than a launch cost. A site with 200 pages in five languages that never updates them is not a multilingual asset — it is a multilingual liability.
Common Mistakes
- Adding languages before the URL strategy is settled. The most common cause of expensive rework.
- Machine-translated pages published without review. They rarely rank and can dilute signals from properly localised content.
- Missing or one-directional hreflang. Search engines then guess, and usually guess wrong.
- Translating URLs inconsistently — some locales translated, others not — which fragments signals.
- Forgetting non-content strings: form validation, emails, error pages, checkout copy and date formats.
- No per-language sitemap coverage, leaving some locales effectively undiscoverable.
- Assuming the theme handles right-to-left languages without testing.
- Ignoring performance per locale. Translation layers add database queries; the slowest locale is what visitors actually experience.
Our Recommendation
For most businesses: subdirectories, a mature translation plugin configured properly, per-language sitemaps, verified hreflang, and editor training. That is the agency build tier at $4,000–$12,000, and it covers the overwhelming majority of real needs.
Move to custom headless i18n at $18,000–$45,000 only when locale count makes manual coordination unworkable, or when a translation management system should own the content. If you are redesigning anyway, the combined redesign plus multilingual path at $9,000–$25,000 is usually cheaper than doing the two projects separately.
FAQ
How many languages can WordPress handle?
Technically unlimited. Practically, the constraint is editorial: every additional language multiplies the content that must be created, reviewed and kept current. Most sites do better with three well-maintained languages than twelve neglected ones.
Does multilingual hurt site speed?
It can. Translation layers add database queries and the language switcher adds logic to every page load. The effect is usually small with object caching in place and significant without it. Measure the slowest locale rather than assuming the fastest represents the experience.
Should I use a plugin or WordPress multisite?
A plugin suits a single site with shared media and one editorial team. Multisite suits genuinely separate sites with different administrators or materially different structures. Multisite adds operational complexity that most single-brand sites do not need.
Can I launch with machine translation only?
You can launch, but do not leave it unreviewed. Unreviewed machine translation rarely ranks and reads poorly on the pages that matter most — pricing, product and policy pages. Use it for drafts and volume, then have a human review anything commercial.
Get a Multilingual Build Plan
Send your target locales, current site structure and who will maintain translations. You get back a URL strategy, an architecture recommendation and a scoped build plan with a fixed price.
Request a quote or see cross-border and multilingual site development.
