How to Build a Multilingual Website the Right Way

$body$

If you sell to customers in more than one country, a multilingual website is not a luxury — it is a requirement. The numbers are clear: about 75% of shoppers prefer to buy in their native language, and 60% rarely or never buy from English-only websites. But a badly built multilingual site can do more harm than good: duplicate content, the wrong language showing up in search results, confused visitors.

First decision: URL structure

You have three realistic options, and this decision is expensive to change later:

• Subdirectories (site.com/de/) — easiest to maintain, and all domain authority stays in one place. For most small and mid-sized sites this is the right choice.
• Subdomains (de.site.com) — technically separate, but Google partially treats them as distinct sites, so you build authority from scratch.
• Separate domains (site.de) — the strongest local signal, but also the most expensive option: every domain needs its own registration, maintenance and SEO.

Our advice from experience: start with subdirectories. That is exactly the model we use on SEOhosting.rs — /en/ and /de/ versions on a single domain.

Hreflang: tell Google who gets what

Hreflang tags tell search engines which language version to show to which user. Without them, Google may serve your Serbian page to a German visitor, or flag your versions as duplicate content. The rules are strict: every page must reference all of its language versions including itself, and the links must be reciprocal. Most hreflang implementations on small sites contain errors — check yours in Search Console.

Translation: machine, human, or both

Auto-translating the whole site without review is the most common mistake. Since 2022 Google explicitly treats unedited machine translation as a spam signal. The realistic approach: machine translation as a first draft, then native-speaker review for the pages that sell — homepage, services, pricing. The blog can be translated gradually, by priority.

WordPress: which plugin

For WordPress there are three serious options: Polylang (free for basic needs, lightweight), WPML (the most complete, from €39/year) and TranslatePress (translate directly on the page). For smaller sites Polylang is entirely sufficient. Watch performance, though — multilingual plugins add database queries, so on slow hosting the site slows down noticeably. On WordPress hosting with NVMe storage that difference is barely measurable.

Do not forget the rest

Translate the things that are easy to forget: meta titles and descriptions, form messages, confirmation emails, the 404 page. Keep the language switcher visible in the header — and avoid flags, because a flag marks a country, not a language. Do not auto-redirect by IP address either: suggest a language, but let the visitor choose.

A multilingual site also means visitors from all over the world — and for them the site has to load fast. All of our plans include a free global CDN, so content is served from the location closest to each visitor, whether they are in Vienna, Zurich or Chicago.

$body$