When Google finds a multilingual or multi-regional site with zero hreflang markup, it has to guess which URL belongs to which audience. This flag fires when a site that clearly serves several languages or countries ships every one of those pages naked, without a single hreflang annotation to connect them.
What this check flags and why it stings
The check catches sites that publish parallel language or country versions (a /en/, /fr/, /de/ tree, or ccTLDs like example.de and example.fr) but never tell search engines those pages are alternates of one another. Without that signal, Google treats each version as an isolated document, often ranks the wrong one in a given market, and sometimes collapses near-identical translations into a duplicate-content pile where only one survives.
What correct hreflang looks like
Hreflang is a clustering signal, not a command. Google reads the whole set of annotations, confirms the pages point back at each other, and then uses that confirmed cluster to swap in the right regional URL for the right searcher. Here is a clean three-language set, placed in the <head> of every page in the group:
<link rel="alternate" hreflang="en" href="https://example.com/en/pricing/" />
<link rel="alternate" hreflang="fr" href="https://example.com/fr/tarifs/" />
<link rel="alternate" hreflang="de" href="https://example.com/de/preise/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/en/pricing/" />Every page in the cluster carries the identical block, including a self-referencing row for itself and an x-default fallback for searchers you do not explicitly target. Miss the return references and the whole thing degrades into noise Google quietly discards.
Where hreflang belongs, and where it does not
You have three delivery methods, and picking one is the first real decision. This table shows what each costs you in practice.
| Method | Best when | Real-world tax |
|---|---|---|
HTML <link> in <head> | Small to mid sites, full template control | Page weight grows with every added language; edits touch every template |
HTTP Link: header | Non-HTML files (PDFs) or when the head is locked | Harder to audit; needs server or CDN config access |
XML sitemap <xhtml:link> | Large sites, hundreds of URLs and locales | Slower for Google to pick up; sitemap must stay perfectly in sync |
You need hreflang only when the same content exists for different languages or regions. A single English site selling to one market does not need it, and bolting it on where it serves no purpose just gives you more surface area to break.
How to detect it
- Crawl with Screaming Frog and open the Hreflang tab. If the "Contains hreflang" column reads empty across your localized URLs while the site clearly has language folders or ccTLDs, that is your smoking gun.
- View source on two parallel URLs (say
/en/and/fr/of the same page) and search the head forhreflang. Nothing there confirms the annotations were never emitted. - Run the pair through a validator such as our hreflang validator to confirm no cluster exists yet.
- Check Search Console. Under the international-targeting and page indexing reports, an absence of any hreflang recognition on a genuinely multilingual property is the same signal from Google's side.
How to fix it
- Map the cluster. List every URL that is a true alternate of every other, one row per language or region.
- Pick one method and stick to it. Mixing HTML tags and sitemap entries for the same URLs is how you end up debugging ghosts. If you are unsure, the complete hreflang implementation guide walks the trade-offs.
- Emit the full block on every page, with a self-reference and an
x-default. Skipping either is the fastest way to get the cluster ignored. - Use correct codes: ISO 639-1 for language, optional ISO 3166-1 Alpha-2 for region (
en-gb,pt-br). Region without language is invalid. - Recrawl and validate. Confirm the return references resolve before you call it done.
Getting the annotations live is step one. Getting them to hold means each page must also point at itself, which is its own common failure covered in missing self-referencing hreflang. And once the cluster exists, you will want an x-default fallback so unmatched searchers land somewhere sensible instead of nowhere.
FAQ
Does every multilingual site actually need hreflang?
Only if the language or regional versions are genuine alternates of the same content. If your German and English pages are entirely different products, they are not alternates and hreflang would be lying to Google.
Will adding hreflang boost my rankings?
Not directly. It does not lift a page's authority. It routes the version you already rank into the right market, which fixes wrong-language impressions and the bounce that follows. That indirect win is the whole point.
Can I use hreflang and canonical tags together?
Yes, and you must be careful. Each localized page should self-canonicalize, never canonicalize to another language. A page that canonicalizes to a different-language URL while also claiming to be an hreflang alternate sends Google a contradiction it will resolve by ignoring your signals.
How long before Google acts on new annotations?
Google has to recrawl every URL in the cluster and confirm the return references before it trusts the set, so expect days to a few weeks depending on crawl frequency. Sitemap-delivered hreflang tends to lag HTML tags.
What is the single most common way this breaks?
Return references. Page A points to B, but B never points back to A, so Google throws out the pairing. Always ship the identical, complete block everywhere.
Claude Vincent is a technical SEO consultant focused on crawlability, rendering, and AI-search visibility. He writes the field guides and case studies at SEO ProCheck, with a bias toward the durable, unglamorous work that decides whether search engines and AI answer engines can actually read and cite a site.
About SEO ProCheck
Technical SEO consulting and GEO strategy with 20 years of enterprise experience. Case studies, resources, and tools for search and AI visibility.
Work With Me
Technical SEO audits, GEO strategy, site migrations, and international SEO. Hourly consulting for teams who need hands-on support, not just reports.
Subscribe to our newsletter!
