Is it true that you must fully translate a multilingual site to rank well?

How does this clarification change the game for multilingual sites?

Many SEOs believe that a multilingual site must be fully translated to be considered by Google. This belief leads to massive investments right from the launch of a language version. Mueller debunks this myth: Google does not expect perfect parity between language versions.

Each page is indexed and evaluated in its own language, independently of other versions. If you translate 20 pages out of 500, those 20 pages can very well rank in their target language. The other 480 do not affect their performance.

How does Google technically manage this independence?

The hreflang — a tag that signals alternative language versions — works page by page. You do not need to create a complete link structure between all pages in all languages.

Specifically? A page \/fr\/produit-a can point to \/en\/product-a and \/de\/produkt-a via hreflang, even if \/fr\/produit-b has no English or German version. Google does not penalize this asymmetry.

What pitfalls should you avoid despite this flexibility?

This flexibility does not mean total improvisation. A poorly thought-out partial translation can create user experience inconsistencies: broken internal links, hybrid navigation, mixed signals for crawlers.

If you translate strategic pages but leave support pages (T&Cs, FAQs) in the original language, you risk a high bounce rate from non-French-speaking users. Google will not make this a direct de-ranking criterion — but low engagement can indirectly affect your rankings.

• Google evaluates each language separately: no need for total parity between versions.
• Hreflang works at the page level: no need to translate the entire site to use it.
• A gradual approach is valid: start with high ROI pages.
• User experience remains crucial: a partial translation must still be coherent.

Is this statement consistent with field observations?

Absolutely. In the audits I conduct, I regularly see sites translate only their main categories and their best-sellers — and rank perfectly in the new target languages. The rest of the catalog remains in the original language without measurable negative impact.

What works less well? Sites that translate at random — a product page here, a blog article there — without a user journey logic. Google does not penalize them directly, but users flee, which degrades engagement metrics.

What nuances should be added to this rule?

Mueller does not specify a crucial point: the indirect impact of missing pages. If you translate a product page but not the parent category page, you break the internal linking in the target language. Result: the translated page becomes orphaned from a crawl perspective.

Another rarely discussed limitation: brand signals. A site with 500 pages in French and 10 in English sends a signal of low investment in the English-speaking market. Google does not algorithmically punish it — [To be verified] — but users and potential backlinks perceive it.

What practical steps should you take to translate gradually without losing effectiveness?

Start by identifying high ROI pages: those that generate traffic, conversions, or serve as strategic entry points. Translate these pages first, then gradually expand to the necessary support pages for their user journey.

Ensure that each translated page has a coherent environment: navigation menu in the correct language, functional internal links, hreflang properly implemented. An isolated page, even if well translated, will perform poorly.

What mistakes should you avoid during a partial multilingual deployment?

Do not translate pages randomly without considering the user journey. If you translate a product sheet but not the category page, the user will land on a dead end. Google will index the page, but it will be orphaned from a crawl perspective.

Avoid incomplete hreflang. If a French page has 3 language versions but you only declare 2, Google may misinterpret your signals and display the wrong language in the SERPs.

• Prioritize strategic pages: flagship products, landing pages, high-traffic content.
• Ensure a coherent user journey: translate related support pages (categories, FAQs, T&Cs if necessary).
• Implement hreflang page by page, even for partial translations.
• Check the internal linking: no translated page should become orphaned.
• Monitor engagement metrics by language: if the bounce rate skyrockets, it indicates that partial translation creates friction.
• Document your progressive translation strategy to avoid inconsistencies over time.
  A progressive translation is a perfectly viable strategy, but it requires rigorous planning. Between managing hreflang, multilingual architecture, internal linking, and editorial priorities, these deployments can quickly become complex. If you lack internal resources or technical expertise, the support of an SEO agency specialized in international can help you avoid costly mistakes and accelerate your time-to-market.