What Happens If You Don't Implement Hreflang Correctly for Translated Pages?

If you skip hreflang or set it up wrong, Google has to guess which page serves which audience. The guess is often wrong. A Spanish buyer in Madrid may see your English page. A German buyer in Berlin may see your French page. Google may also decide that two translated pages are duplicates and index only one of them.

The direct business cost is lost organic traffic in every market you tried to reach. You paid for translation, but search engines cannot connect the right page to the right query. Ranking signals split across language versions, so no single version builds enough authority to compete.

How Google Reads Translated Pages Without Hreflang

Hreflang is a signal, not a directive. It tells Google which URL is the alternate version for a specific language or region. Without it, Google relies on page content, server location, and backlinks to infer language targeting.

That inference fails often. A page written in Spanish can still rank for English queries if Google sees strong English backlinks. A page hosted in Germany can rank in Austria and Switzerland even when the content is meant only for Germany. The result is a mismatch between the page you built and the audience that finds it.

The Four Main Failure Modes

When hreflang is missing or broken, one of four problems usually appears.

1. Only One Language Version Gets Indexed

Google may treat translated pages as duplicates. If the pages share the same template, images, and navigation, Google can decide they are the same content in different wrappers. It then indexes one version and drops the rest from search results.

Your German page exists, but it never appears in German search results. The translation investment produces no organic return.

2. The Wrong Language Shows in Local Results

A user in France searches in French. Google shows your English page because it has more authority. The user clicks, sees English, and leaves. You lose the click, the session, and the chance to convert.

This is worse than not translating at all. The user expected a French experience and got a jarring mismatch.

3. Ranking Signals Split Across Versions

Backlinks, engagement metrics, and internal links are ranking signals. When Google cannot connect your English and Spanish pages as alternates, those signals stay separate. Each page competes alone against competitors whose signals are consolidated.

Your English page may rank well. Your Spanish page may rank poorly. Neither reaches its potential because the authority is fragmented.

4. Duplicate Content Filters Suppress Visibility

Google does not penalize duplicate content the way many people fear, but it does filter. If two pages look similar, Google picks one to show. The filtered page can still be indexed, but it rarely appears for competitive queries.

Translated pages are not duplicates in the traditional sense, but Google's systems may not know that without hreflang. The filter then suppresses the exact pages you built for international growth.

Hypothetical Scenario: The Silent Traffic Leak

Imagine a B2B software company with English, German, and French versions of its pricing page. The team translates all three pages but skips hreflang because the CMS does not support it natively.

After three months, organic traffic from Germany is flat. The German page is indexed, but it ranks on page three for the main keyword. The English page ranks on page one for the same keyword in Germany because it has more backlinks.

German buyers click the English page, see English pricing, and bounce. The company concludes that German demand is low. The real problem is that Google never learned which page to show German users.

This is a hypothetical example, but the mechanism is common. Hreflang errors rarely cause a dramatic traffic drop. They cause a silent leak: the right page exists, but the wrong page wins the click.

Common Hreflang Mistakes That Trigger These Failures

Most broken implementations share a few patterns.

• Missing self-referencing tags. Each page must list itself as an alternate. If the English page lists only the German page, Google sees an incomplete cluster.
• Non-reciprocal tags. If page A points to page B, page B must point back to page A. One-way tags break the cluster.
• Wrong language or region codes. Using "en" for a UK page when it should be "en-GB" sends a weaker signal. Using "es" for a page meant only for Mexico misses the regional intent.
• Pointing to redirects or non-canonical URLs. Hreflang URLs must return 200 status codes and be canonical versions. Pointing to a redirect or a page with a different canonical breaks the signal.
• Conflicting canonical and hreflang signals. If a page canonicalizes to another URL but also declares hreflang alternates, Google may ignore the hreflang entirely.

How to Check Whether Your Hreflang Is Working

Start with a manual check. Open a translated page, view the source, and confirm the hreflang tags are present in the <head>. Then check the reciprocal tags on every other language version.

Use Google Search Console. The International Targeting report shows hreflang errors and missing return tags. Fix every error before assuming the implementation works.

Run a crawler like Screaming Frog. It can extract hreflang tags across the site and flag non-reciprocal pairs, redirects, and missing self-references.

Finally, search from a target country using a VPN or the gl parameter. See which page Google actually shows. If the wrong language appears, the signal is not strong enough.

When Hreflang Is Not the Problem

Hreflang fixes language targeting, not content quality. If your translated pages are thin, poorly written, or machine-translated without review, hreflang will not make them rank. Google still evaluates content quality independently.

Hreflang also does not fix technical issues like slow load times, broken internal links, or poor mobile experience. Those problems suppress rankings regardless of language signals.

If you have only one language version, hreflang is unnecessary. It only matters when multiple language or regional versions exist.

Key Facts

Limitations of Hreflang

Hreflang is a hint, not a command. Google may still show a different language version if it believes that version better matches user intent. This is especially common when a user's browser language differs from their location.

Hreflang does not consolidate ranking signals automatically. It helps Google understand the relationship between pages, but backlinks and engagement still matter. A translated page with no links will struggle even with perfect hreflang.

Hreflang does not work across different domains unless the tags are reciprocal and canonical signals align. Cross-domain implementations are more error-prone.

Terminology

Hreflang: An HTML attribute that tells search engines which language and region a page targets, and which other URLs are alternate versions.

Canonical tag: An HTML element that tells search engines which URL is the preferred version when duplicate or similar pages exist.

Reciprocal tags: Hreflang tags that point both ways between two language versions. Page A lists page B, and page B lists page A.

Self-referencing tag: A hreflang tag on a page that lists the page itself as an alternate for its own language.

Frequently Asked Questions

Does hreflang affect rankings directly?

No. Hreflang does not boost rankings. It helps Google show the right page to the right user, which can improve click-through rate and engagement. Those signals may indirectly support rankings.

Can I use hreflang for pages in the same language but different regions?

Yes. Use language and region codes like en-US and en-GB to distinguish regional variants. This is useful when pricing, spelling, or legal terms differ.

What is the difference between hreflang and canonical?

Canonical tells Google which page is the primary version. Hreflang tells Google which pages are alternates for different languages or regions. They serve different purposes and should not conflict.

How long does it take for hreflang changes to take effect?

Google must recrawl the pages and reprocess the signals. This can take days to weeks, depending on crawl frequency. Check Search Console to confirm the new tags are seen.

Do I need hreflang if I use a subdirectory structure like example.com/es/?

Yes. The URL structure helps, but hreflang makes the relationship explicit. Without it, Google may still misinterpret which pages are alternates.

What happens if I point hreflang to a page that redirects?

Google may ignore the tag. Hreflang URLs must return 200 status codes and be the canonical version of the page. Redirects break the signal.