Google Doesn't Translate Your Site — It Ignores It. Here's the Proof.

I've heard some version of this sentence in almost every meeting about international strategy:

"Google translates pages automatically in the browser now. We don't really need a translation layer."

It's the most confident wrong opinion in SEO. Let me show you what's actually happening.

What Google Translate in Chrome actually does

When a visitor hits your English page in a non-English browser, Chrome may show a banner offering to translate the page client-side. That's a browser feature. Google the company has nothing to do with it beyond shipping the button.

Here's the critical part. That translation happens after the page is already indexed, served, and rendered. It lives in the visitor's browser tab for one session. Googlebot never saw it. Your server never sent it. Search Console can't measure it. Nobody else's browser has any clue it existed.

Ask yourself: if your site is translated on-the-fly by the browser, what does Google's index contain? One answer: your English page. Just the English one. That's the only version that exists for search ranking purposes.

What Googlebot sees when you have no translation layer

It sees your English page. That's it. No Spanish version. No French version. No German. Googlebot is a crawler, not a translator. It reads what you serve.

This matters because search rankings are computed per-language. When someone in Madrid searches software de facturación, Google picks a ranked list of Spanish results. Your page doesn't exist in that list. It isn't "de-ranked." It isn't "buried." It simply isn't a candidate at all.

You are competing on English SERPs only. Then hoping Chrome's translate-this-page button saves you after the click.

The click-through reality

Let's even grant the optimistic case. Your English page ranks in a non-English SERP because no competitor bothered to rank in that language. A visitor clicks.

They see English. They see the translate banner. Maybe they click it. Maybe they don't. Here's what research has repeatedly shown:

• Click-through rate on SERP results in a non-native language is dramatically lower than same-language results — roughly 40–60% lower in published CTR studies
• Of the visitors who do click, fewer than half accept the translate-this-page prompt
• Of those who accept, conversion rate is still worse than for a site served natively in their language, because machine-translated content in Chrome renders over your existing page — forms, buttons, error messages, checkout steps — with no designer oversight

You're losing visitors at three stages in a row: the SERP doesn't even show you, the few who click see English, and the few who translate see a Frankenstein'd version of your page with the "Subscribe" button now reading "Suscribir" in Comic-Sans-height glitchy type.

Why hreflang + real translation fixes this

When you actually translate your pages and declare them with hreflang, three things happen in order:

1. Google indexes each language version as a separate page
2. hreflang tells Google which URL to surface for which audience
3. The Spanish speaker in Madrid sees your /es/ URL on the Spanish SERP, clicks, and lands on a page already in Spanish

This is the only configuration where Google actually routes traffic the way you want. Everything else is hoping the browser saves you after the sale is already lost.

The "but we tried translation and it didn't move rankings" objection

Almost always, when I hear this, one of three things is going on:

• The translated pages weren't indexed because of a robots.txt block on the language subdirectory
• hreflang was set up but the handshake was broken (87 out of 100 sites get this wrong)
• The translations existed but Googlebot was being served the English version because of a botched user-agent detection

Translation working at the infrastructure level isn't hard. Translation working as an SEO asset requires that all three — content, hreflang, and how Googlebot experiences your server — line up cleanly. When they don't, the translations are invisible and you conclude "it didn't work."

What doing nothing actually costs

Every month you don't translate, you cede the non-English SERPs to a competitor who did. Once they rank, they'll build backlinks, accumulate engagement signals, and become the default answer for those queries. Catching up is harder than starting.

The five-minute version of "start": add SiteDialect. Visitors from non-English locales see your site in their language. hreflang is emitted correctly. Googlebot, if it crawls with a non-English Accept-Language, can index the translated version. You stop leaking traffic starting tomorrow.