Websites
Multilingual websites for EU businesses: hreflang across several languages
How to structure a website in three or more EU languages: URLs, hreflang rules, language versus country targeting, translation workflow and SEO per market.
A website that sells across EU borders in several languages needs three things to rank in each market: one URL per language version, hreflang annotations that link every version to every other version (including itself), and content that is genuinely written for each audience rather than run through a translator and published. For most small and mid-sized EU businesses, the simplest structure that works is one domain with a subfolder per language, such as /el/, /en/, /de/, with hreflang tags in the page head or the XML sitemap. Country-specific domains only pay off when you have separate offers, prices or teams per country.
This guide covers the choices in the order you make them.
Decide first: are you targeting languages or countries
Google draws a clear line between the two. A multilingual site offers content in more than one language. A multi-regional site targets users in specific countries. Many EU sites are both, and mixing them up causes most hreflang problems.
Ask one question per market: does anything change besides the language?
- Only the language changes. Same products, same prices in euros, same shipping. Target languages:
de,fr,el,en. A German speaker in Austria and one in Germany land on the same German page. - The offer changes by country. Different prices, VAT display, delivery times, legal text or phone numbers for Germany and Austria. Target language and country:
de-DE,de-AT. Each needs its own page, because they are different pages.
Most small businesses start with languages only. Splitting by country later is easier than undoing a premature split, where de-DE and de-AT pages are near-duplicates competing with each other.
Choose a URL structure
Google's documentation compares four options:
| Structure | Example | Good for | Watch out for |
|---|---|---|---|
| Country domains (ccTLD) | example.de, example.gr | Strong country signal, separate operations per country | Cost, several domains to run, some registries have rules, each domain targets one country |
| Subdomains | de.example.com | Separate hosting per version | Visitors may not know if "de" means language or country |
| Subfolders | example.com/de/ | Easy set-up and maintenance on one host | Weaker country signal; everything on one server |
| URL parameters | example.com?lang=de | Nothing | Google says it doesn't recommend them |
Subfolders are the default recommendation for a business with one team and one offer. The domain's authority is shared across every language, and you maintain one site.
One detail people miss: Google identifies a page's language from the visible content, not from the lang attribute or the URL. A page at /de/ with German navigation and an English body is an English page as far as language detection goes. Keep one language per page, including menus, buttons and footers. Google specifically advises against side-by-side translations on one page.
Set up hreflang properly
Hreflang tells Google which pages are equivalents in other languages, so it shows the right one to each searcher. Google accepts three methods: <link> tags in the HTML head, HTTP headers (useful for PDFs), or the XML sitemap. They are equivalent. Pick one and use it consistently.
The rules that break most implementations
- Every version lists itself and all others. On a site with Greek, English and German, each page carries three hreflang lines plus
x-default. - Links must be reciprocal. If the Greek page points to the German page, the German page must point back. Google ignores annotations that don't match.
- Use absolute URLs including
https://. - Use valid codes. Language first in ISO 639-1 (
el,de,fr), with an optional region in ISO 3166-1 Alpha 2 (de-AT). A country code alone is invalid.EUandUKdon't work as regions; the United Kingdom isGB. - Add
x-defaultfor visitors whose language you don't offer. It usually points to the English version or a language selector page.
An example
For a product page in Greek, English and German, every one of the three pages carries the same block:
``html <link rel="alternate" hreflang="el" href="https://example.com/el/product/" /> <link rel="alternate" hreflang="en" href="https://example.com/en/product/" /> <link rel="alternate" hreflang="de" href="https://example.com/de/product/" /> <link rel="alternate" hreflang="x-default" href="https://example.com/en/product/" /> ``
When a page doesn't exist in every language
Leave it out of the hreflang set rather than pointing to a near match. If your blog post exists only in English, it has no hreflang tags, or only those for the versions that exist. Pointing the German tag at the German home page tells Google something false.
Generate it, don't hand-type it
Hand-maintained hreflang breaks within months: someone adds a page in one language and forgets the others. Build it into your CMS or site generator so that hreflang tags, the language switcher and the sitemap all come from the same list of translations.
Don't redirect people by IP or browser language
It's tempting to send German visitors to /de/ automatically. Google advises against it, for two reasons. Its crawler usually comes from the United States and doesn't send a language preference, so automatic redirects can hide your other versions from Google. And travellers, expats and bilingual customers often want a different version than the one you guess.
Use a visible language switcher on every page that links to the same page in the other language, not to the home page. If you want to help, show a small, dismissible suggestion ("This page is also available in Deutsch") instead of a forced redirect.
A translation workflow that holds up
Machine translation has improved a lot, and it is a sensible first draft. Publishing it unreviewed at scale is a risk. Google's spam policies list automated transformations, translating included, among the techniques behind scaled content abuse when the goal is to produce many pages without adding value. Beyond rankings, a stiff or wrong translation costs trust with exactly the buyer you want.
A workflow that works for small teams:
- Write the source version well. Translation multiplies mistakes.
- Research keywords per language before translating. People in different markets use different words for the same thing. The Greek, German and French search terms for your product are not literal translations of the English term, and search volumes differ.
- Machine-translate a draft, then have a native speaker edit it with the keyword list in hand. Titles, meta descriptions, headings and calls to action deserve the most attention.
- Localize the details: currency format, dates, phone numbers with country codes, units, sizes, delivery promises, and examples that make sense in that market.
- Translate the slug.
/de/produkte/korsett-overall/reads better for a German searcher than/de/products/corset-jumpsuit/. - Track every page's translations in one place, so an update to the source flags the other versions as outdated.
SEO per language: treat each market as its own
Each language version competes in its own search results with its own competitors. That means:
- separate keyword research and separate content priorities per market
- titles and descriptions written for each language, not translated literally
- links from sites in each market: a German page benefits from German-language mentions, a Greek page from Greek ones
- a Google Business Profile in the local language if you have a physical presence
- Search Console reporting filtered by country and by language folder, so you can see which version is pulling its weight
Expect uneven results. A version in a language with less competition may rank quickly, while a German or French version in a crowded market may need sustained work.
Common mistakes in short
- Hreflang pointing to pages that redirect or return errors
- Canonical tags on every language version pointing to the English page. Google's guidance is to set the canonical in the same language and use hreflang for the alternates
- One language's pages blocked in robots.txt during development and never unblocked
- Mixed-language pages with translated text but English menus
- A language switcher that drops visitors on the home page
How PNE approaches it
PNE builds sites in several languages through our Website Design service, with hreflang, sitemaps and the language switcher generated from the same source so they never drift apart. The DENES store, a premium corset activewear label, was designed and built in French and English, with the shop and product pages available in both. The same structure extends to three, four or more EU languages.