Can hreflang really substitute for internal links on your international pages?

Does hreflang merely change the display in search results?

Exactly. Hreflang is a technical signal indicating to Google: “If a French-speaking user seeks this content, show them the .fr version instead of the .com version.” It is a mechanism for swapping in the SERPs, not a vehicle for transmitting SEO value.

The engine reads the hreflang annotations and, if everything is correctly set up, replaces the originally ranked page in the results with its relevant linguistic or geographical variant. But this swap only happens if Google has already crawled, indexed, and understood the alternative version — which requires that this page is discoverable via internal HTML links.

Why is an internal HTML link essential for a new country page?

Because Google discovers pages by following links. Without an HTML link pointing to your new /fr/, /de/, or /es/ page, the bot has no way to find it — unless it is explicitly submitted via a sitemap, which remains a crutch and not a sustainable strategy.

The internal link serves several critical functions: it signals the existence of the page, positions it within the site hierarchy, passes PageRank, and informs Google about the thematic context through the link anchor. Hreflang, on the other hand, does none of that. It assumes the page already exists, has been crawled, indexed, and understood — in other words, that the internal linking work has already been done.

Does hreflang transfer backlink value between language versions?

No. This is a point that Mueller explicitly makes. Hreflang does not move link juice from one version to another. If your /en/ page accumulates quality backlinks and you launch a /fr/ version with hreflang, this new page does not automatically benefit from this transferred authority.

For the /fr/ version to gain power, it must either earn its own backlinks or receive internal PageRank via links from other pages of the site — again, classic HTML links. Hreflang only comes into play at the display stage in the results, not in the distribution of authority.

• Hreflang = display signal in the SERPs by language/country, not a crawling or value transmission vector.
• Internal HTML links are mandatory for Google to discover, index, and understand the architecture of international pages.
• No backlink transfer via hreflang — each version must build its own authority or receive internal PageRank.
• XML sitemap can complement but never replace a structured internal linking.
• An isolated page with perfect hreflang but no internal link remains invisible to Google.

Is this statement consistent with observed practices in the field?

Absolutely. We regularly see multilingual sites that deploy hreflang impeccably — clean tags, bidirectional matches, sitemaps — and wonder why their new country versions stagnate in visibility. The answer boils down to one word: linking.

In most cases, these international pages are only accessible via a language selector in the header or footer, with no contextual link from the content. Google can technically discover them via sitemap, but without internal relevance signals, they remain on the periphery of the site architecture. Hreflang does not address this structural deficit.

What nuances should be added to this rule?

If an alternative page is already well crawled and indexed — for example, via direct backlinks obtained during a targeted link-building campaign — hreflang can work very well without a dense network of internal links being necessary. But this is a minority case.

The other nuance concerns very large sites with a tight crawl budget. Multiplying internal links to all language versions can dilute crawling if not done intelligently. In this context, a strategic linking — through navigation, breadcrumb, contextual links from strong pages — is preferable to a footlink overload to 15 versions of each page.

In what cases does this rule not fully apply?

On sites with a single targeted product or service page with strictly identical language versions, hreflang may suffice if each version receives its own flow of external backlinks. This is typically the case with localized advertising landing pages that exist independently.

However, as soon as we talk about a site with a complex structure — e-commerce, media, B2B portal — Mueller's rule applies without exception. Each new country page must be integrated into the site’s navigation, breadcrumb, and related content blocks. Hreflang alone will never replace this integration.

What should be done concretely when launching new country versions?

First step: integrate the new pages into the main navigation — either through a dropdown menu for language/country selection visible from all pages, or through contextual links in the equivalent page content. The footer can complement, but should not be the only access point.

Then, ensure that each page of the new version receives internal PageRank from the strong pages of the site. If your /en/blog/seo-guide/ has 50 backlinks and a good ranking, an internal link from this page to /fr/blog/guide-seo/ will pass value — unlike hreflang which only enables the swap in French SERPs.

What mistakes to avoid when implementing hreflang?

Never deploy hreflang before having a functional internal linking. Some sites add the annotations as soon as they launch a new version, while it is not linked to the rest of the site by any link — result: Google does not crawl, does not index, and hreflang becomes useless.

Another classic mistake: believing that hreflang will "push" a weak page to rank simply because it is linked to a strong page in another language. Hreflang does not boost anything. If your /de/ version of content is mediocre, poorly optimized, or duplicated, it will not rank better with hreflang — it will just be displayed instead of the /en/ version for German-speaking users, which will worsen your user metrics.

How to check if your international structure is compliant?

Audit your internal linking with Screaming Frog or Oncrawl: each language version must be accessible in 1 to 3 clicks from the homepage, and the equivalent pages must link to each other via clear anchors (“Read this article in French”, “Read this article in English”).

Then check that your hreflang annotations are bidirectional and consistent — the Search Console will alert you to common errors (missing self-referencing, broken links, incorrect language codes). But even without hreflang errors, if your alternative pages are not crawled, the problem lies with the linking, not the syntax.

• Integrate each new country page into the main navigation (menu, footer, breadcrumb).
• Create contextual HTML links from equivalent pages in other languages.
• Ensure that alternative pages receive internal PageRank via links from strong pages.
• Audit the internal linking with a crawler to ensure that all versions are accessible within 1-3 clicks.
• Deploy hreflang only once the internal linking is operational and the pages are indexed.
• Monitor the Search Console for hreflang errors and uncrawled alternative pages.