Do internal links between language versions really transfer PageRank?

Does Google treat each language as a distinct site?

Yes, and this is a point that is often overlooked. Each language version of the same content is evaluated as a separate page, with its own ranking history, its own backlinks, and its own engagement metrics.

This means that translating a high-performing article into English does not guarantee any automatic performance transfer to the French version. The engine does not mix languages: if the page /en/article-x is in first position, its translation /fr/article-x starts from zero—or almost.

What role do internal links between language versions play?

This is where Mueller's statement becomes interesting. By creating a link between the performing version and the new translated version, a partial redistribution of ranking signals is triggered.

We are talking about signals in the broad sense: internal PageRank, topical authority, possibly even behavioral signals transferred through user journey. It’s not just a matter of crawling or discovery—it's a real lever for boosting.

What is the difference with hreflang tags?

Be careful not to confuse them. Hreflang tags tell Google which version to serve to which user based on their language and location. They do not transfer any ranking signals.

The traditional internal links between language versions, on the other hand, play a structural role: they circulate link juice, help to contextualize the new version, and speed up its indexing and authority rise. These are two complementary mechanisms, not interchangeable.

• Each language version is treated as an independent page by Google, with no automatic performance transfer.
• Internal links between languages allow for the distribution of some ranking signals from the source version to the target version.
• This mechanism is distinct from hreflang, which only serves to indicate which version to display to which user.
• The signal transfer works best if the source page already has an established authority—otherwise, the effect remains marginal.
• This is an underestimated lever to accelerate the launch of a multilingual site.

Is this statement consistent with what we observe in the field?

Yes, and it's even a welcome confirmation. We have long known that internal linking distributes PageRank, regardless of the context—why would it change between two language versions?

What’s interesting is that Mueller doesn't just say, "pages are linked for navigation." He explicitly talks about signal transfer. This validates that Google does not neutralize link juice just because it passes between two languages. It’s a classic link, with the same properties.

What is the limit of this mechanism?

Let’s be honest: if the source page has low authority, the transfer will be weak. It’s not a miracle worker. Linking a mediocre FR page to a mediocre EN page is not going to create magical traffic.

And you should also be wary of a rarely mentioned point: if the translated version is of poor quality (unreviewed machine translation, content unsuitable for the local target), it may not rank even with link juice. Google assesses linguistic and cultural relevance—it’s not just a matter of technical signals.

Is there a risk of cannibalization between language versions?

No, and this is an unfounded concern that we sometimes hear. Google does not pit two pages in different languages against each other for the same query, except in very marginal cases (ambiguous queries, users without defined language).

The hreflang, precisely, serves to clear any ambiguity. If you have correctly indicated that /en/ targets English speakers and /fr/ targets French speakers, there is no risk of conflict. [To be verified]: it remains to confirm that this principle also applies to sites that mix translated content with unique local content—there, it can get complicated.

What should you do concretely on a multilingual site?

Start by identifying your top-performing pages in each language. Those that already generate organic traffic, backlinks, and engagement. These are the ones that have the most juice to transfer.

Next, make sure that these pages explicitly link to their translated counterparts. Not just through a language selector hidden in the footer—a real link in the body of the page, or at the very least, a visible banner at the top of the page.

What mistakes should be avoided in language linking?

Don’t automatically link all versions to each other if you have 10 languages. Prioritize links from high-traffic source versions to the new versions you want to boost. A star-shaped linking, not a grid linking.

Also avoid creating orphan links: if you link /en/article → /fr/article, remember to make the reverse link too. This facilitates bidirectional crawling and strengthens the coherence of the language cluster.

How can you check if signal transfer is working?

Monitor the evolution of organic traffic on the new language versions after implementing the linking. A faster startup than normal, positions gained more quickly, is a sign that it’s working.

Also use crawling tools to ensure that the translated pages are being discovered and indexed quickly. If they remain in "Detected, currently not indexed" for weeks, it means the link wasn’t sufficient—or there is a quality issue.

• Map the top-performing pages in each language and their translated counterparts
• Install clear and visible internal links between language versions (not just a footer selector)
• Check that the hreflang tags are properly in place and consistent
• Track the indexing and traffic of new versions to measure the transfer effect
• Prioritize the quality of translations—the transfer of signals will never compensate for mediocre content
• Avoid over-linking: concentrate links from high-authority versions only