Blog
Google steals your international search movement using automated translations
Jun
Since March Core update, there has been a huge boost in Google’s efforts to automatically translate English -language websites to other languages. Hook? These newly translated pages are hosted in the Google subdomain, so the original content creators do not see any benefits from them.
This coincides with the huge implementation of AI reviews, which we saw next to March update. AI reviews are currently in 200 countries and 40 languages. It seems that when artificial intelligence reviews do not have enough native content, Google resorts to auto-translating content in English.
These translations on Google are common in artificial intelligence reviews, but also appear in distinguished fragments, other SERP functions and normal 10 blue SERP links. In other words: If you haven’t located your content, now you risk that Google will capture this local movement for himself.
As Patrick Stox notes, Google has been talking about improving the Hreflang system for years. Instead of continuing to facilitate creators of content in translating and locating their content, it seems that Google has decided that the best option is to recognize traffic as their own (something we see more and more often). This seems hypocritical, taking into account their long -lasting advice to avoid automatic content transfer.
Let’s take a closer look at what is happening, as well as many thanks to Metehan Yesiluyurt for being one of the The first people who emphasized this.
When Google cannot find a forceful source of local language, he now downloads the authoritative English side, and he translates it in flight and supports a copy under a subdomain belonging to Google, which looks like this:
www-your-site-com.translate.goog/path?hl=es&sl=enBecause HTML is cordial through Google, users never visit your domain. The site can then be quoted in Google serpts, including in AI reviews, which currently appear in 200 countries and 40 languages.
These pages look like this:
If we apply the AHREFS website explorer to analyze organic performance indicators for translator.google.com/TranslateWe can estimate which countries see most of these auto-translation of the pages:
| Location | Estimated monthly organic movement | The appearance of the AI review | Disturbed pages |
|---|---|---|---|
| All | 377m | 6.2 m | 50.9 m |
| India | 136m | 743K | 10.7 m |
| Indonesia | 39m | 997K | 9.3 m |
| Brazil | 36.9 m | 1.2 m | 6m |
| Turkey | 33.3 m | 162k | 5.3 m |
| Mexico | 28.3 m | 1m | 7.1m |
| Thailand | 23.4m | 50.6k | 3.4 m |
| Vietnam | 13.7m | 24k | 2.5 m |
| Argentina | 9.4 m | 398K | 3.8 m |
| Colombia | 8.3 m | 441K | 3.6 m |
| Peru | 6m | 209k | 1.8 m |
If you want to check if Google automatically overflows pages from your part, you can apply the search console and Ahrefs to find out:
- Search the console filter. Search appearance → Translated pages
- Ahrefs Explorer → Open a report from the best pages translator.google.com And apply the “URL contains” filter, entering the domain name.
- Domestic Towns. Incognito-Search Your brand/topic in target languages. Alternatively, simulate searching for the Ahrefs toolbar.
- Logarithmic file controls or GA4. Look for sessions in which the recipient is equal translator.google.com
When Google shows his version of proxy translation in SERP, the user lands translator.google.com. Clicking to your site will be registered as Google / Organic, but clicking that leads to translator.google.com Displaying your website is recorded as a translator.google.com / command. Your organic movement (and every sales he runs) is insufficiently reported.
Each internal link inside this side of the proxy also indicates translator.google.comSo the wrong attribution continues when users click.
Send even A 300-lone native version in languageIN Even if it is MVP. It gives Google a local URL for citing, usually displacing proxy.
Brisk steps for a plain solution (of course they may vary depending on the cases)
Scenario:
Your article lives at /Blog/How-to-Pick-A-VPN. Google is pouring it and sends Spanish -speaking search engines to translator.googleusercontent.com. You want visitors to come back (and analytical loan).
Translate your website. If you translate with AI, make sure you double checking the conditions of the brand, idioms, screenshots … etc.
Make sure you apply Hreflang tags to connect pages.
What changes in searching and analyzes:
Google now has a real Spanish URL for the ranking, so Link Proxy disappears from Spanish serpts in one or two days.
IN Search for console → search appearance → translated pages You will see the impressions for this page fall to zero.
GA4 stops registering the translator.google.com / command and assigns clicks to Google / Organic Restoring search statistics.
If you don’t do it or you can’t do it, you can Ask Google not to automatically send essential URLs Using X-Robots-Tag.
Tip
Only blocking the translation on the pages where the loss of the canonical URL (cash flows, lead general) hurts. Departure Notranslat Off blog content allows Google to continue to explain when it is helpful.
https://developers.google.com/search/docs/apperance/translate-resues
Bonus: Natzir came with his own script, how to solve it. Link to GitHub
Proxy Furge will not kill SEO, but prescribes a textbook in a multilingual SERP: “Be the best local answer Or be grateful. “Make sure your brand will land on the right side of this equation.
