18 JUL 2026

Multilingual website: hreflang without the headache

Hreflang for a multilingual website: the Italian, English and German versions linked so Google serves the right language

You’ve translated the site into English and German, rightly so. But now an Italian customer searches Google and ends up on the English page; a German lands on the Italian version; and your two pages — same content, different languages — compete with each other in the results. The culprit is almost always the same: hreflang is missing or wrong. It’s the attribute that tells Google “this page is the Italian version, that one is English, serve each to the right person.” People talk about hreflang for a multilingual website as something forbidding: it is, if you treat it as a plugin to switch on. Let’s see what it really is, how to set it up without errors and why it’s engineering, not luck.

What hreflang is (in plain terms).

Imagine you have the same page in three languages: Italian, English, German. To a search engine they’re three different addresses with contents that look very much alike — and without an explicit signal, Google has to guess which to show to whom, risking mistakes or treating them as duplicate content. Hreflang is that explicit signal: a small marker, present on every version, that says “I exist in these languages, here are the addresses of all of them, and I’m the one for Italian.”

The golden rule is reciprocity: if the Italian page points to the English one, the English must point back to the Italian, and every version must list all the others — itself included. Google, in its official documentation on localised versions, insists on exactly this: the references must be bidirectional and complete, or it ignores them. This is where most of the headaches come from: not in the concept, but in the consistency to maintain across dozens of pages.

How hreflang works in a multilingual website: the Italian, English and German versions cite each other reciprocally — Hreflang links the versions of a page: each declares itself and all the others, reciprocally (if IT points to EN, EN must point to IT). This way Google serves the right language and doesn’t treat them as duplicate content. Source: Google Search Central, localised versions.

The mistakes that break a multilingual website.

Almost every hreflang problem comes from a few recurring mistakes. Knowing them is half the job, because they’re almost always the same ones.

aNon-reciprocal references: the IT page cites the EN one, but the EN doesn’t reciprocate. Google discards the whole pair and goes back to guessing.

bWrong language codes: “en-UK” doesn’t exist (it’s “en-GB”), and a made-up code is silently ignored.

cRelative URLs or pages pointing to “noindex” versions: hreflang must point to absolute, indexable addresses, or it’s useless.

dThe self-reference is missing: every version must also list itself. Forgetting it is the most common and most silent mistake.

Google — tell Google about localised versions (hreflang) →

Hreflang isn’t everything: the language has to ring true.

There’s a misconception to dismantle: hreflang solves “which version to show,” not “the version is any good.” You can have perfect hreflang and still lose the customer if the translation sounds fake. A machine-translated product page with the wrong register drives away the person reading it in their own language — and no technical attribute makes up for that. CSA’s research (“Can’t Read, Won’t Buy”) has said it for years: people buy far more willingly in their own language, and distrust text that sounds foreign.

That’s why, for us, multilingual is two crafts in one: the engineering that links the versions (hreflang, sitemap, URL structure) and the native-speaking editors who write, rather than machine-translate. The languages are handled by native speakers of the Remarka group, in the field since 2001, selected by an internal testing platform that rejects the vast majority of candidates — the same one that holds the quality of every multilingual project of ours. And if a market has its own rules — for Germany, Austria — the technical part goes beyond hreflang: it’s the handling of multi-regional sites.

Multilingual websites with native-speaking editors →

Google — managing multi-regional and multilingual sites →

The platform that selects who translates (only 8% pass) →

How to keep it in order, without losing your mind.

The secret to not losing your mind over hreflang is not managing it by hand. Across dozens of pages and three languages, keeping reciprocal references by hand is an endless source of errors. The solution is to generate hreflang from a single map of correspondences — one source of truth, from which every page inherits its own links — so that adding a page doesn’t mean updating thirty. It’s exactly the approach this site is built on: Italian at the root, English and Russian as coherent trees, linked by a map that’s never touched by hand.

In practice, before adding languages it’s worth checking how Google already reads your site: whether the existing versions cite each other correctly, whether there are wrong codes, whether something ends up out of the index. An on-page SEO analysis surfaces these problems before they cost you positions. And if you’re thinking not just of translating but of opening a foreign market for real, hreflang is only the first piece of a bigger picture: digital export.

Analyse your page’s on-page SEO for free →

We design your multilingual site at a fixed price →

Sources.

The figures and claims in this article come from here. These are primary sources, not summaries: open them and check for yourself.

Google Search Central — localised versions (hreflang)The official documentation: how to declare versions by language, with reciprocal and complete references.
Google Search Central — multi-regional and multilingual sitesHow to handle language and country together: URL structure, targeting and pitfalls to avoid.
CSA Research — “Can’t Read, Won’t Buy”The research on buying behaviour: people buy far more willingly in their own language.

Multilingual sites with hreflang and native speakers, at a fixed price →