Do you need a multi-language website to sell across Europe?

Selling into a new European market often stalls on one question: does the site need to speak the customer's language, or is English enough? The honest answer is that it depends on the market and the margin — but the buying data leans hard towards localisation, and the cost of getting it wrong is quiet, invisible drop-off rather than an obvious error.

This post covers when multilingual is worth it, why buyers trust their own language, the difference between translation and true localisation, the SEO plumbing (hreflang) that makes it work, the tech approaches, and how to weigh the ROI before you commit.

The buying case: people trust their own language

The most-cited evidence comes from CSA Research. Their 2020 survey of 8,709 consumers across 29 countries found that 76% of online shoppers prefer to buy products with information in their native language, and 40% will never buy from websites in other languages at all. In Germany, 57% said they only purchase from local-language sites. (CSA Research, "Survey of 8,709 Consumers in 29 Countries", 2020.)

The earlier "Can't Read, Won't Buy" work put similar numbers on it: 72.4% of consumers were more likely to buy when information was in their own language, and 56.2% said obtaining information in their own language mattered more than price. (CSA Research / Common Sense Advisory.)

Two things worth noting so you don't over-read the data:

• Language preference is strongest in some markets (Germany, Japan, Korea) and softer in others where English fluency is high (Netherlands, Nordics). It varies by country, so treat "always localise" as a starting hypothesis, not a law.
• Price still wins sometimes — the same 2020 survey found 66% would pick a cheaper product even without native-language information. Localisation raises conversion and trust; it doesn't override a bad offer.

The takeaway: in most non-Anglophone European markets, an English-only site leaves conversions on the table, and you rarely see the visitors who bounced because they couldn't read a returns policy or checkout step with confidence.

When it is actually worth it

Localisation has real cost, so match it to the opportunity. It tends to pay off when:

• You are targeting a specific country with meaningful volume, not spraying pan-European traffic.
• The purchase carries perceived risk — higher price, subscriptions, anything where trust and clear terms matter.
• You compete against local players who already sell in the language.
• Post-sale content matters: support, warranties, instructions. Those are where language friction turns into refunds and churn.

It matters less when your buyers are a narrow, English-comfortable B2B niche, or when you are still validating a market and one clean English page is enough to test demand. If you are still deciding which market to enter first, our guide on the best country to start an ecommerce business in Europe is a better first read than a translation brief.

Before committing budget, it helps to put rough numbers on it — expected traffic, current conversion, and the lift localisation might add. Our multilingual ROI calculator lets you model that per market so the decision is based on payback, not gut feel.

Translation is not localisation

Running your copy through machine translation gives you words in another language. Localisation makes the site feel like it was built for that market. The gap between the two is where trust is won or lost.

True localisation covers:

• Currency and pricing shown in local currency, with tax handled the way that market expects (VAT-inclusive display is the norm for EU consumers).
• Formats — dates, addresses, phone numbers, units.
• Payment methods locals actually use (iDEAL in the Netherlands, Bancontact in Belgium, SEPA, Klarna, and so on).
• Tone and idiom — a literal translation of a clever English tagline often lands as awkward or meaningless.
• Trust signals — local-language support, reviews, and legal pages. CSA's data showed 73% want product reviews in their own language and 75% are more likely to repurchase when support is offered in it.

Machine translation is a reasonable first pass, but customer-facing pages — homepage, product pages, checkout, returns — deserve a human review. That is the difference between "translated" and "convincing".

The SEO plumbing: hreflang

If you publish the same page in several languages, search engines need to know these are alternates, not duplicates — and which version to serve to whom. That is what the hreflang attribute does. Get it right and a German searcher lands on your German page; get it wrong and Google may show the wrong language or discount the pages as duplicates.

The essentials, straight from Google's documentation:

• You can declare alternates three equivalent ways: HTML <link rel="alternate" hreflang="..."> tags in the head, HTTP headers (useful for non-HTML files like PDFs), or an XML sitemap.
• Language codes use ISO 639-1 (e.g. de, fr), optionally with a region in ISO 3166-1 Alpha-2 (e.g. en-GB, pt-PT). You can't specify a region on its own — the language part is required.
• Links must be reciprocal: if page X points to page Y, Y must point back to X, or the annotations are ignored.
• Add an x-default entry as the fallback for users whose language you don't cover.

hreflang is fiddly and easy to break — missing return tags and wrong codes are the usual culprits, and a single error in a cluster can make Google ignore the whole set — so it's worth validating rather than eyeballing. (Source: Google Search Central, Localized versions of your pages.)

Tech approaches

There are three common ways to structure a multilingual site, each with trade-offs:

• Subdirectories (example.com/de/) — simplest to run, inherits the domain's authority, easy to add languages. The most common sensible default.
• Subdomains (de.example.com) — cleaner separation, slightly more setup, authority is a little more diluted.
• Country ccTLDs (example.de) — strongest local signal and trust, but you manage multiple domains and their SEO separately. Worth it when you are seriously committed to a market.

For most SMBs selling across several European countries, subdirectories with correct hreflang give the best effort-to-result ratio. Pair that with local-currency pricing and payment methods, and remember cross-border VAT obligations — the EU's OSS and IOSS schemes for ecommerce VAT change how you charge and remit once you're selling into multiple member states.

Weighing the ROI

Localisation is an investment with a measurable return, so treat it like one. A simple frame:

1. Estimate addressable traffic for the target market.
2. Take your current conversion rate as the baseline.
3. Apply a conservative lift for buying in-language (even a few points is often material given the CSA data).
4. Subtract translation, localisation, and ongoing maintenance costs.

Do that per market and you'll usually find a clear "yes" for one or two countries and a "not yet" for the rest — which is exactly the disciplined roll-out you want. Model it with the multilingual ROI calculator before you brief anyone.

Deciding whether to localise is one piece of a bigger picture; if you're at the start of this, our pillar guide on how to start an online business in Europe puts it in context alongside structure, tax, and market choice.

Where to start

If you're expanding into one or two European markets and the numbers stack up, a well-structured multilingual site — proper localisation, clean hreflang, local payment and currency — is one of the highest-leverage things you can build. If you'd rather not wire up the SEO and localisation plumbing yourself, see our web development service or book a free consultation and we'll help you scope which markets to localise first and how to do it without breaking your search visibility.