The fastest way to add translation to a website is Google Translate. Either the "Translate" button in the browser or a widget. It seems that the problem is solved. For users, this works, for search engines - it doesn't.
Three Options and Why Each Doesn't Work for SEO
1. Browser Translation Button
The Chrome browser offers to translate a page if it is in a foreign language. The user clicks “Translate” — and sees the translated version directly in the browser.
For SEO, this does nothing. Google indexes the original HTML of the page. The translated version exists only in the specific user's browser: it is not saved, it has no URL, it cannot be indexed. The search engine does not know that the translation exists.
2. Google Translate Widget on the Page
Many websites embed the Google Translate widget: a small dropdown menu with languages. The user selects a language — and the page is “translated.”
Technically, this works the same way as the button in the browser: the translation is performed in the user's browser via JavaScript. The page URL does not change (or only the hash changes: #googtrans(en)). For Google, this is the same page in the original language.
Result: there is no English version of the site in the search, no German, no French. There is only one page in one language, to which the user can apply a translation in the browser. This is not a multilingual site.
3. Google Translate API for Server-Side Translation
This is a different story. The Google Translate API can be used for automatic content translation on the server — then the translated pages are saved and have their own URLs. The search engine sees them.
The problem here is different: the quality of machine translation via a general API and specialized models for specific domains (legal, medical, technical) are different things. Plus, infrastructure is needed to store and update translations.
Why One Translation Is Not Enough
Technical SEO for a multilingual website includes more than just the text itself. You need:
- Separate URLs for each language version
- hreflang attributes so Google knows which version is for which language
- Translated meta tags: title, description, Open Graph
- Correct sitemap structure with language versions
The Google Translate widget does not cover any of these points.
What to do instead of the widget
A multilingual site with SEO results means separate URLs for each language. Either folders (/en/, /de/), or subdomains, or separate domains. Each version is indexed by the search engine as an independent page.
The translation can be automatic — but it must happen on the server, not in the browser. Then Googlebot sees the translated text on the very first request for the page.
If the widget is already installed
If a site uses the Google Translate widget now, it's not a disaster — there's just no SEO effect from multilingualism. A Russian-speaking audience will find the site in Russian search, but the site will not be visible in search to a German or English audience.
Transitioning to full multilingualism with separate URLs will require setup, but it's a one-time job. Afterward — each language version begins to accumulate positions in its regional search.
Frequently Asked Questions
Does it even make sense to use the Google Translate widget?
For UX — maybe, if the audience is non-technical and never switches the language in the browser themselves. For SEO — no. This is a tool for quick reading, not for creating a full-fledged multilingual website.
If users translate via the browser — does Google count this?
No. Browser translation is a local action of a specific user. Google indexes the page in its original state. What the user does with it in the browser does not affect indexing.
Does Yandex also not see widget translations?
Correct. Yandex.Browser and other browsers offer page translation — this is a similar client-side function. Yandex as a search engine indexes the original HTML, not its browser translation.
