Client-Facing
Multilingual site hosting — A client with four language markets, and one account
Going multilingual barely changes what the client needs from the server and changes a great deal about what they will expect from you.
Straight answer first
Build it as one WordPress site on subfolders and host it on a Pro account. One site, clean hreflang, and the translation effort spent where the audience actually is, because the structural decision is the part that determines whether you are supporting a website or four of them.
Below: what a language site really does to your account allowance, who owns the structure decision and why it should be settled in writing, where your support scope ends and the translator's begins, and what to sell.
Written by the Hosting Seller staff · Checked 24 August 2026
99.9%
Uptime target we hold
24/7
People on the counter, for you and them
Free
SSL on every site you host
NVMe
Disks under every client account
Putting each language in a subfolder such as /fr/ or /de/ keeps a domain's authority in one place, where subdomains and separate country domains divide it. That should be the default unless legal or market reasons say otherwise.
For the person hosting the site the good news is that this is a light workload. Translated content multiplies pages and cache entries rather than cost per visitor. The work that arrives is scope, not capacity.
What it does to your account allowance
Less than the client expects. Four languages on subfolders is one WordPress install, one database that grows, and four times the cache entries, which are cheap.
The translation plugins are the heavier part. WPML and Polylang add tables and queries, and a site with a large catalogue in several languages will feel the database before it feels anything else.
So plan for a Pro-tier account, watch the database rather than the disk, and only think about a bigger tier when the query profile says so rather than when the client mentions the word international.
Who owns the structure decision
Subfolders, subdomains or country domains is a decision with consequences years long, and it is usually made by whoever is in the room when the client asks.
Make it yours, in writing. Subfolders for most people: one domain gathering all the authority and the simplest hosting arrangement. Country domains when a national presence is genuinely strategic and the budget covers running several. Subdomains rarely win this comparison.
If the client insists on country domains, price the extra accounts, the extra certificates and the extra renewals honestly at the start rather than absorbing them one at a time.
Where your scope ends
Hreflang tags done correctly are a survival requirement in search, and they are configuration rather than content, which usually makes them yours.
Translation quality is not. Machine-translating a site into a pile of thin duplicate pages is a real risk to the client's rankings, and it is worth saying so plainly and in advance, because you will otherwise be blamed for the outcome.
Write both positions into the agreement. Structure, hreflang and hosting here; content and translation quality with them or their agency. Ambiguity on this one costs more than most.
The account to sell them
The plan for this is Pro. One flat price, several sites on the account if the structure ever needs them, and the certificate, the move-in and the mailboxes already in it.
Caching does most of the performance work across regions, and LiteSpeed runs at the server rather than as a plugin the client can disable while experimenting.
The renewal price matches the order price, so a client whose project runs over two years does not arrive at a repricing conversation in the middle of it.
The part we cannot sell you
Hosting does not fix a badly translated site, and we would rather say so before the client's rankings do. What we can supply is the platform, the caching and the certificate; the rest belongs to whoever writes the words.
NVMe disks and LiteSpeed caching sit on the shelf at every price point, not behind a premium tier.
- Several sites on one account from the Pro tier up
- Caching at the server, not a plugin the client can disable
- Certificates issued and reissued automatically
- The renewal price is the price you quoted
Why Hosting Seller
On every plan, as standard
The plan behind this page
Pro carries a multilingual WordPress site comfortably, with room for extra sites if the structure ever needs them.
Room for the plugin weight
WPML and Polylang add tables and queries rather than traffic, and this tier has the database headroom for that.
Caching that survives the client
LiteSpeed runs at the server, so cache performance does not depend on a plugin nobody has disabled this week.
Certificates for every hostname
Free SSL issued and reissued automatically, which matters more once a client is running more than one domain.
A supplier you can name
IGI Security Services Ltd, registered in England and Wales, with terms published under English law.
Margin that survives renewal
The order price is the renewal price, so a two-year project does not meet a repricing conversation halfway through.
Price Tags Compared
How we compare with the household names
Typical sign-up and renewal prices across the market, set next to ours — the second number most comparison charts leave off.
| Line item | Hosting SellerBest seller | Typical big-brand host | Typical budget host | Typical loss-leader |
|---|---|---|---|---|
| Entry price / mo* | $2.42/mo | $4–$6 | $2–$4 | $1–$3 |
| Price at renewal / mo | $2.42/mo | $10–$15 | $8–$12 | $4–$6 |
| Renewal price on the entry plan is unchanged | ||||
| SSL on every plan | ||||
| Site migration included | ||||
| The entry plan uses NVMe storage | ||||
| Entry plan gets a backup daily | ||||
| Live human support, 24/7 |
*The number in our column is the cheapest plan on our shelf, priced on an annual term and pulled live from the very catalogue that feeds the pricing page, so it cannot drift out of date. Other columns show the ranges shared hosting tends to advertise inside each bracket: introductory rates that normally ask for a one-to-four-year commitment, then climb once that term expires. Naming individual competitors and printing their prices is something we have stopped doing. A figure we cannot re-check on the day you read it has no business sitting in front of you. So compare us with whoever you are genuinely weighing up, and read the renewal line first. That line tells you more than the headline ever will.
First Steps
From choosing to live
- 1
Settle the structure before anything is built
Subfolders unless there is a legal or market reason otherwise. Write the decision down, because it is expensive to revisit once content exists.
- 2
Price country domains honestly if they insist
Extra accounts, extra certificates and extra renewals, quoted at the start rather than absorbed one at a time over two years.
- 3
Put translation quality outside your scope
Hreflang and hosting are yours; the words are not. Say so in the agreement or you will be blamed for a machine-translated ranking problem.
In the Box
Packed with every plan
- Several sites on one account from the Pro tier upward
- Free SSL on every hostname, reissued before it lapses
- LiteSpeed caching running at the server rather than by plugin
- Daily backups with restores you run yourself
- Staging copies so a structural change is tested first
- PHP versions picked per site from the panel
- Mailboxes on the client's own domain, with filtering fitted
- Site migration handled by our staff at no charge
- DDoS filtering handled out at the network edge
- The renewal price on the tag matches the order price
Across the Counter
Things people ask us all the time
Does a multilingual client need a bigger plan?
Only modestly. Translated content multiplies pages and cache entries rather than cost per visitor, and a Pro-tier account carries several languages comfortably. Watch the database rather than the disk, because the translation plugins are the heavier part.
Subfolders, subdomains or country domains?
Subfolders for most clients: one domain gathering the authority and the simplest hosting arrangement. Country domains when a national presence is genuinely strategic and the budget covers running several. Subdomains rarely win this comparison.
Who is responsible if the translations hurt their rankings?
Whoever wrote them, provided you said so in advance. Structure, hreflang and hosting are reasonably yours; translation quality is not. Machine-translating a site into thin duplicate pages is a real risk and it is worth flagging before the work starts.
What if the client wants a separate domain per market?
It is a legitimate choice when a national presence is strategic, and it costs more to run. Price the additional accounts, certificates and renewals at the start. Transfers of names they already own are routine: unlock at the current registrar, collect the auth code, and start the transfer from the client area.
Read next
Laravel Hosting Plans
The Laravel client who would rather you handled the infrastructure, and what that commits you to.
White-Label Hosting
A surface-by-surface audit of what can name your upstream supplier, and the pack to start on.
Web Hosting
cPanel accounts on NVMe disks, with SSL, the move-in and year-one domain included.
VPS Hosting
KVM virtual servers with root access, DDoS filtering and one flat price.
Moving your site to another host? Start with this checklist.
A step-by-step order of work for a move your visitors never spot: which files to copy first, how to carry email across without losing one message, the right moment to repoint DNS, and the two mistakes behind nearly every hour of downtime people ring us about.
Host the site, scope the rest.
Accounts that carry several sites, caching at the server, free certificates on every hostname and a flat renewal price.
See Web Hosting plans