Multilingual Websites: hreflang, Translation and UK Exporters

Why language versions pay for exporters

UK firms selling into Europe and beyond have learned the hard way that an English-only website caps growth. Buyers browse comfortably in English, then hesitate at the moments that matter: delivery terms, returns policies, guarantees, checkout. Most consumers strongly prefer to buy in their own language, and business buyers are little different once contracts and specifications are involved.

Language versions are also one of the few SEO expansions with genuinely untapped inventory. Competing for "workwear supplier" in English means fighting the entire anglophone internet; the equivalent German or Dutch query is often far less contested. But the technical build determines whether those pages ever rank, so get the plumbing right before spending a penny on translation.

Choose your URL structure before anything else

Search engines need each language version at a stable, crawlable URL. Three structures work; pick one and stay consistent:

• Country domains (yourbrand.de): the strongest local signal and the most trusted by German buyers, but each domain builds SEO authority from zero and multiplies hosting, registration and maintenance overhead.
• Subdirectories (yourbrand.com/de/): the pragmatic default for most SMEs. Every language inherits the main domain's authority, and one site is cheaper to run and secure.
• Subdomains (de.yourbrand.com): a middle ground that search engines treat as semi-separate; rarely the best pick for a small firm.

What does not work: switching language via cookies, JavaScript or a ?lang= parameter alone. If two languages share one URL, search engines index one and ignore the other.

hreflang without the tears

hreflang annotations tell search engines which page is the German version, which is the French, and which to show a given searcher. They stop your language versions competing with each other and stop German users landing on English pages in the results.

You can implement hreflang three ways: link tags in the head, HTTP headers, or the XML sitemap. For anything beyond a handful of pages, the sitemap is the easiest to maintain and keeps the markup out of your templates. The rules that trip people up:

• Tags must be reciprocal. If the English page points to the German one, the German page must point back, or the pair is ignored entirely.
• Every page needs a self-referencing tag for its own language as well.
• Use ISO codes correctly: language first, optional region second, as in en-GB, de-DE or plain fr. The region code for the United Kingdom is GB; "en-UK" is invalid and silently ignored.
• Add an x-default entry naming the page for users who match no listed language, typically your English homepage or a language selector.

A translation workflow that scales

Raw machine translation of an entire site is a false economy: it reads as foreign-made to native speakers, and thin machine-translated pages published at scale risk being treated as low-value content. The workflow that works for most exporters is machine translation post-editing (MTPE): a system such as DeepL produces the draft and a native-speaking editor fixes tone, terminology and cultural slips. Reserve fully human translation for your money pages: the homepage, key product or service pages, and anything legal.

Two additions separate translated from localised. First, a glossary: agree the translation of your product names and key terms once, so every page uses them consistently. Second, local keyword research: German buyers often search using a different term from the literal translation of your English keyword, so validate with a keyword tool before finalising page titles, meta descriptions and headings, all of which need translating too. And avoid client-side translation widgets; content generated in the browser is generally not indexed as your German or French site.

The indexing mistakes that waste budgets

• Auto-redirecting visitors by IP address. Googlebot crawls mostly from US addresses, so aggressive geo-redirects can mean it never sees your European versions at all. Show a polite suggestion banner instead and let people choose.
• Canonical tags pointing every language back to the English page, which tells search engines to ignore the translations you just paid for.
• Translating body copy but leaving titles, meta descriptions, navigation and checkout in English, which undermines both rankings and buyer trust.
• Pointing hreflang at URLs that redirect, return 404 or carry noindex; broken targets invalidate the whole annotation.
• Launching five languages half-finished instead of one done properly. A complete German site outperforms five skeletal ones every time.

Beyond words: currency, tax and trust

Language is necessary but not sufficient. European buyers expect prices in euros, and ecommerce exporters need a VAT plan: the EU's Import One Stop Shop (IOSS) simplifies VAT on lower-value consignments, and your checkout should show duties and taxes up front rather than surprising customers at the door.

Local payment habits matter too: iDEAL in the Netherlands, Bancontact in Belgium, invoice payment in parts of Germany and the Nordics. Add localised trust signals, such as a local phone number format, realistic delivery times to that country and reviews from customers there. These details convert the traffic your hreflang work wins. If you would like the technical build and the translation workflow set up as one project, our team can help.