Could misconfigured hreflang ruin your indexing?

What does 'folding' mean in Google indexing?

Google uses the term 'folding' to describe a process where multiple similar pages are consolidated into a single entry in the index. When you have nearly identical content in US and UK English, for example, Google may decide to index only one version, ignoring the others to save crawl budget and space in the index.

Hreflang serves to prevent this folding by indicating that these similar pages each have a distinct geographical or linguistic target. Without this signal, Google may perceive you as duplicating content without a valid reason and arbitrarily choose which version to index.

Why does incorrect tagging pose a problem?

When your hreflang tags contain errors, Google can no longer rely on this signal to understand your multilingual architecture. The engine then falls into a degraded mode where it applies its own heuristics to guess which page corresponds to which region.

The result: your French pages may show up in Belgium, your Canadian content in France, or worse, Google may decide to fold multiple versions together and ignore some completely. You lose control over your visibility by market.

What are the most common tagging errors?

Classic issues include badly formed language codes (fr-be instead of fr-BE), non-reciprocal tags (page A points to B but B does not return to A), missing self-referencing pages, or syntax errors in x-default.

The Search Console displays these errors in the Coverage section, but messages often remain cryptic. A manual audit is usually necessary to understand the exact origin of the problem.

• Hreflang is not a ranking factor, but a geographical targeting signal
• Tagging errors do not create penalties, they simply nullify the signal
• Google may fold (consolidate) similar pages if it does not understand their geographical distinction
• Tags must be bidirectional: each referenced page must link to all others
• An incorrect hreflang is like having none at all, but with the added risk of confusing Google

Does this statement align with field observations?

Yes, we regularly see cases where multilingual sites with misconfigured hreflang have their French pages indexed but displayed in Spanish SERPs, or vice versa. The term 'folding' accurately describes what happens: Google mentally merges the versions and keeps only one, often the wrong one for the end user.

However, Mueller's wording remains unclear on one point: what precisely defines 'correct' tagging? Google tolerates certain imperfections (orphan pages in a hreflang cluster, for example) but penalizes others. The boundary is not publicly documented.

What nuances should be considered?

Hreflang is not binary: Google may partially ignore your tags if it judges that they contradict other signals (ccTLD, server geolocation, content language). I've seen cases where a perfectly configured hreflang was contradicted by a .fr ccTLD, and Google favored the ccTLD.

Another critical nuance: Mueller says 'pages do not fold incorrectly', but he omits to clarify that even with perfect hreflang, Google can still fold pages if it deems the content too similar. Hreflang reduces this risk, but does not completely eliminate it. [To be verified]: no official documentation quantifies the similarity threshold at which Google ignores hreflang.

When do these rules not really apply?

If your site has only one language version but several regional ccTLDs with identical content (for example: .fr, .be, .ch for the same French), hreflang does not resolve anything. Google will arbitrarily choose a dominant ccTLD and ignore the others, regardless of your tags.

Let’s be honest: some complex sites have abandoned hreflang in favor of consolidation by ccTLD + geotargeting in the Search Console. This approach is sometimes simpler and less prone to maintenance errors, especially if you have thousands of pages and a limited technical team.

What should be prioritized in auditing a multilingual site?

Start by checking the reciprocity of the tags: each page listed in a hreflang cluster must also point to all other pages in the cluster, including itself. A tool like Screaming Frog or Sitebulb can automate this check in minutes.

Next, verify the language and region codes: use the ISO 639-1 format for language (fr, en, es) and ISO 3166-1 Alpha 2 for region (FR, GB, US). Case sensitivity does not matter much in practice, but it is better to stick to uppercase convention for the region.

What errors should absolutely be avoided?

Never mix implementations: if you are using the HTML tags <link rel="alternate" hreflang>, do not simultaneously add hreflang in the XML sitemap or in HTTP headers. Google will prioritize one of the three sources and conflicts create confusion.

Avoid referencing canonicalized pages to another URL, noindex pages, or redirecting pages. Each URL in your hreflang cluster must be indexable and directly accessible. If Google encounters a 404 or a 301 redirect, it ignores the entire entry.

How can I check that my implementation works?

Use the URL inspector in the Search Console to verify that Google detects your hreflang tags correctly. The Coverage report will alert you to major errors, but not all of them. A manual audit remains necessary for edge cases.

Also test under real conditions: use a VPN to simulate queries from different countries and check that Google displays the appropriate local version in the results. If you see your .fr page appearing in google.de when you have a .de version, it means your signal is not understood.

• Check the full reciprocity of all hreflang tags
• Verify language/region codes according to ISO standards
• Never reference canonicalized, redirected, or noindex pages
• Choose a single implementation method (HTML, sitemap, or HTTP headers)
• Include an x-default tag pointing to a language selection page or the international version
• Test SERP display from different countries with a VPN