Localisation
Multilingual Websites: A Practical Guide to Localisation for EU and Global Markets
76% of online shoppers prefer buying from websites in their own language, and 60% rarely buy from English-only sites at all. Translating your homepage isn’t the same as localising it — currency, payment methods, URL structure and hreflang tags matter as much as the words themselves, and getting the technical setup wrong is the single most common way multilingual projects underperform.
A German visitor lands on your English homepage, sees prices in dollars, and leaves before reading a single line of your copy — not because the writing was bad, but because nothing about the page told them it was built with them in mind. That’s the gap between translation and localisation, and it’s why a genuinely well-translated site can still convert at a fraction of its English performance.
Translation is words. Localisation is trust.
Translating a page swaps the language. Localising it adapts everything around the language too: currency, payment methods people actually use in that market, date formats, imagery that doesn’t feel imported, and metadata — titles, descriptions, alt text — that too often gets left in the source language even after the body copy is fully translated. Skip that layer and the page looks unfinished to the exact audience you built it for.
The technical foundation: hreflang
Hreflang is the HTML attribute that tells Google which language and regional version of a page to show a given searcher. Get it right and your language versions support each other in search. Get it wrong and they compete against each other, or the wrong version shows up in the wrong market entirely. Only around 18% of multilingual sites implement hreflang correctly — which means most of the businesses doing this are leaving visibility on the table without realising it.
The failures are consistent across almost every audit: mixing implementation methods (HTML head, HTTP header, and sitemap all at once), inconsistent locale codes, pointing hreflang at a redirected URL instead of the final one, or missing the x-default fallback entirely. None of these are exotic mistakes — they’re the default outcome of adding languages without a technical plan.
What sitemaps have to do with it
Hreflang tags don’t work in isolation — for a multilingual site of any real size, they belong in your XML sitemap too, with every language variant of a page cross-referenced against every other variant, including the x-default fallback for visitors outside any targeted locale. Skip this and Google may simply never discover your translated pages at all, no matter how well they’re written or how correctly the hreflang tags are set in the page head. This is also where a cookie-based or URL-parameter language switcher quietly sabotages everything: if a language only exists behind a JavaScript toggle with no distinct crawlable URL, there’s nothing for a sitemap to reference in the first place, and that language effectively doesn’t exist as far as search is concerned.
Choosing a URL structure
| Structure | Example | Best for |
|---|---|---|
| Subfolder | yoursite.com/de/ | Most small and mid-sized businesses — default recommendation |
| Subdomain | de.yoursite.com | Teams that need separate hosting per market |
| Country domain | yoursite.de | Large operations with a local legal entity per market |
Subfolders consolidate your SEO authority under one domain and are the simplest to maintain, which is why they’re the right default for almost every small business expanding into new markets. Reach for subdomains or country domains only once you have a genuine operational reason — separate legal entities, separate hosting requirements — not by default.
What actually moves the conversion number
Beyond translation quality, a handful of specific, measurable choices account for most of the lift. None of these require a full redesign — they’re additive changes on top of an existing site, which is exactly why they’re worth prioritising before a larger localisation project:
- Local currency display — a documented conversion lift in the low double digits, just from showing prices in the currency a visitor actually spends.
- Local payment methods — an even larger lift in checkout completion when familiar payment options are available, not just a foreign card form.
- Native-language reviews and social proof — the majority of customers say they prefer reading reviews in their own language before buying.
- Locale-appropriate imagery — visuals that don’t read as obviously stock or culturally mismatched.
The EU angle specifically
For any business trading into the EU, two things compound with everything above: the European Accessibility Act, which we covered in our accessibility guide, applies alongside localisation rather than instead of it — an inaccessible translated page is still failing half its audience. And GDPR-driven cookie consent banners need the same localisation treatment as the rest of the page; a consent banner that’s still in English on an otherwise-French page is one of the fastest ways to signal the translation was an afterthought, not a real investment. It’s a small detail with an outsized effect on trust, precisely because it’s usually the very first thing a visitor reads.
Before you launch a new language
- Confirm each language lives at its own indexable URL — never just a cookie-based switcher.
- Set hreflang consistently across HTML head, sitemap, or HTTP header — pick one method.
- Localise metadata, not just body copy — titles, descriptions, alt text.
- Show local currency and at least one familiar local payment method.
- Translate legal and consent content with the same care as marketing copy.
This is exactly what our localisation service handles end-to-end — hreflang architecture, metadata, and content adaptation together, not translation handed off separately from the technical setup that actually makes it findable.
Thinking about a new market?
Tell me which language or region you’re targeting and I’ll tell you honestly what it takes to do it properly.
Start a projectFrequently asked questions
What’s the difference between translation and localisation?
Translation converts words from one language to another. Localisation goes further — adapting currency, payment methods, imagery, date formats, and cultural references so the page feels like it was built for that market, not just translated for it. A page can be perfectly translated and still convert poorly if it’s not localised.
What is hreflang and why does it matter?
Hreflang is an HTML attribute that tells search engines which language and regional version of a page to show a given visitor. Implemented correctly, it prevents your different language versions from competing against each other in search and stops the wrong version showing up in the wrong market. Only a small share of multilingual sites implement it correctly, which makes it one of the highest-impact technical fixes available.
Should I use subfolders, subdomains, or separate country domains for different languages?
Subfolders (yoursite.com/de/) are the default recommendation for most small and mid-sized businesses — they consolidate SEO authority under one domain and are the simplest to maintain. Subdomains or country-specific domains only make sense at a scale where you need fully separate hosting, legal entities, or infrastructure per market.
Is automatic browser-based language detection enough for a multilingual site?
No — relying only on automatic redirects based on browser or location settings, without unique indexable URLs per language, is one of the most common multilingual SEO mistakes. It can trap search engines in the wrong version entirely and prevents each language from building its own search visibility.
Does localisation actually pay for itself?
Industry data compiled from multiple localisation studies points to roughly 20% higher conversion rates and up to 3x ROI within the first year for businesses that localise properly, driven mainly by local currency display, native-language checkout, and content that matches how people in that market actually search.