If a brand runs more than one language on the same domain, hreflang is the single most under-implemented technical asset it has. Most sites either omit it entirely, add it wrongly, or add it partially — and lose a meaningful share of foreign-market search visibility as a consequence.
What follows is what actually needs to be true, plus the four failure modes we see in almost every diagnosis.
What hreflang actually does
Hreflang tells Google that two URLs are the same content in different languages, and instructs the crawler to serve each user the version that matches their language and region. It does not affect rankings directly. It affects which of your ranking pages is shown to which user.
Without hreflang, an Italian searching for a hotel in Como may see the English version of your page in results. They bounce. Google reads the bounce as a relevance signal against the page, and the whole cluster loses.
The four failure modes
1. Missing return tags
The most common failure. Page A links to page B via hreflang="it", but page B doesn't link back to page A. Google treats this as a broken cluster and ignores the whole set.
2. Wrong canonical direction
Each page in a cluster must self-reference its canonical, not point to a single "master" language. Setting the Italian page's canonical to the English URL kills its indexation entirely — the page ceases to exist to Google.
3. Missing x-default
Without hreflang="x-default", users from unmatched locales get whatever Google guesses. Add x-default and it usually points to the English version — the safe fallback for a global audience.
4. Language codes with mismatched regions
hreflang="en-US" is a different declaration from hreflang="en". If the site targets English-speaking audiences broadly, use the language-only code. Region codes narrow the audience — sometimes intentionally, often accidentally.
The audit that catches this before Google does
For each URL in the multilingual cluster:
- Fetch the page and extract every
<link rel="alternate" hreflang="…">tag. - Verify each referenced URL returns 200, has a self-referencing canonical, and links back via hreflang to every sibling in the cluster.
- Confirm
hreflang="x-default"is present and points to a reachable URL. - Cross-check that no page in the cluster has its canonical pointing to a sibling instead of itself.
Google Search Console's International Targeting report catches most of this, but only after Google has crawled and processed. An audit run at the source catches it before it costs visibility.
"Hreflang doesn't rank pages. It routes users to the right one. The site that ranks and routes wrong is worse off than the one that doesn't rank at all."
Where the payoff sits
The obvious win — foreign-language searchers landing on the correct-language page — matters. The compound win is that a hreflang-clean site tells Google the whole cluster is intentional, which reduces the risk of one language cannibalising another in the SERP. That's the invisible upside that shows up in Search Console as steadier organic growth over months.
The International SEO Strategy engagement makes this happen at the template layer — audit, rebuild, and monitor. The luxury resort case is one example where the hreflang rebuild alone drove a measurable share of the traffic lift.
For a specific site's audit, the 30-minute strategy session is the right entry.