How to Make the Global Translator Plug-in compatible with Adsense?

The Global Translator Plug-in makes your blog reach more people as it automatically translates your blog to other languages. However, be vary of using the Global Translator plug-in especially when using Google Adsense.

The Global Translator Plug-in can translate your blog into 34 languages (if you are using Google Translation service). In terms of getting your pages indexed in Google, that would mean, all your current pages can be seen in 35 languages (English or default language included). That would be a lot of pages and the more pages you have in Google, the better they always say.

However, I would like to warn you about this clause in the Google Adsense Policy. Based on the question, “What languages does Adsense support?” It is stated that,

Please also be aware that placing the AdSense code on pages with content primarily in an unsupported language is not permitted by the Adsense Program Policies

With this new info, I was shocked and was afraid of defying Google once again, so I cross checked the list and filtered out the languages that Adsense supports. Then I disabled the languages that adsense does not support.

Based on that, here is a list of the languages that Adsense supports and what I suggest you leave in your Global Translator Plug-in (disable the other languages).

Chinese (Simplified)
Chinese (Traditional)

I’m not really sure what happens but I’m just being paranoid after getting my pagerank back. ^_^

20 thoughts on “How to Make the Global Translator Plug-in compatible with Adsense?

  1. I didn’t know they had a global translator plug-in. Have to look into it. Thanks for the tip, Allen. And I hope you get a lot of Greeks and Croats and Serbians visiting your site. You’ll be needing a translator to understand what they’re syaing. 🙂

  2. Oh my mama! lol. Thanks sa info Brother! I never thought we are breaking the rules! Thanks thanks! Need to work this out!

    Ambos last blog post..Bloggers Project for Flash Flood Victims in Cagayan De Oro City

  3. Thanks for this info… And I already change mine.. and follow marhgil suggestion about the robots.txt

    Dexter | Tech At Hand Dot Nets last blog post..Help Raise Funds for Cagayan De Oro City Floods

  4. The translator plugin is really cool but we really must be alert on the terms and conditions attached to everything. Like what happened to one of my accounts in Digg. I was just using that account to give favors to my friends from other websites. They send shouts and I’d comply by digging their stories. I was not much of a ‘digger’ but one day my account was banned. I asked Digg what’s wrong but all I got were automated answers. My messages, which I composed carefully and differently from each other, were not even read by a human being. What did I do? I abandoned Digg. I won’t waste my time on such a pesky website. Sorry for leaving such a long comment here. Many thanks.

    • @Thompson Outdoor Supply, Thanks for the experience. I also got banned in StumbleUpon. But, it is just easy to create another free account right? So I hope you did since social bookmarking sites are really helpful.

  5. hi
    thanks for the experience its really easy to create another free account ..thanks for sharing………….

  6. I got to know that when you have the google translater, it’s messes up with search engine ranking and PR, are you having any problems with this or it’s fine. I wanted to use this but not to sure yet.

    • Hi, Hmm so far, it gives me more indexed pages due to the same page being indexed in many languages… no problems with PR and rankings though. ^_^

  7. Is there any update on any languages that adsense support? Just now I read on other blog comment about ROMANIAN actually was ads supported. Is it true?

  8. This is a wonderful piece of innovation, not so? Just like many WordPress bloggers, I installed this plugin with the hope of multiplying the number of my posts in Search Engine indexes by 34 and hopefully increasing my traffic from non-English speaking countries tremendously. Three weeks later, I discovered that the amount of traffic from non-English speaking countries started increasing rapidly. But I have now sadly uninstalled this plugin from my blog. And here are the four major reasons behind this action:

    1. While traffic from non-English speaking countries increased rapidly, the overall amount of traffic did not increase significantly. The bounce rate was also very high. My understanding was that with the increase of traffic from the non-English Speaking countries, I would be getting not less than twice my usual traffic but that was not the case. After carefully examining the traffic on my blog, I discovered that some of the posts that used to bring me a lot of traffic from Google were now no longer doing so. A look at my pages pages indexed by Google and links to my site showed that the number of indexed pages had been reduced from 240 to 105 and links to my site had been reduced from 279 to 166 respectively. This led me to conclude that the Global Translator plugin was doing something fishy behind the scenes. Brooks and Mark A lamented about the same problem in their comments on John Chow’s post about this plugin. To which, Paul A responded by saying that Google do not treat translated pages as duplicate content. But the trouble comes when the translation service errors out a 302 because of automated abuse. The spider gets served that and breaks the linking structure of your site and destroys any internal linking strategy you may be using. The collapse of the site’s linking that causes PR drop and other content to stop being indexed.
    2. Most of these translators are not that good. For in stance, I usually use the Google Translator in order to translate emails from Japanese to English and vice versa. Even though what I get is far from perfect I understand that this translator is a work-in-progress. This, however, might not be the case with a visitor, from say Portugal, landing on your will not know that the page has been translated automatically and that the imperfections in the content are not necessarily coming from you but rather from the translator. Therefore, your online reputation is at stake. Carlton Bale went through a funny experience which left me in stitches of laughter. He says a native-speaker de-translated the “about me” page of his site. It stated that his gender was “little man” and that he “really like young goats but don’t have them yet”.
    3. Not all the 34 languages in this plugin are supported by Google Adsense. If you do not limit the number of languages, you might get penalized by Google Adsense. Marhgil lists the languages NOT supported by Google Adsense that you have to disable on the Global Translator Plugin to make your Google Adsense in full compliance with their TOS. Although this a good development, it erodes the benefits of the plugin by limiting the its capability and, consequently, the reach of your blog.
    4. Finally, but not least, Google MIGHT penalize your site thinking that you’re setting up mirror sites in order to artificially inflate the number of links to your site. Google is so clever. Maybe they have already implemented a system to detect new links created by this plug in. Google can easily detect this by noticing that the number of pages on your site has increased by a factor of 34 in just one day.

    In light of the four reasons, I have decided to unistall the Global Translator plugin from my blog until further notice.

    • Hello Adnan,

      After reading this comment, I have decided to uninstall the plug-in from my blog too. As an alternative,I’ll just add something that will translate my blog via a query to google translate or babelfish.

      Thanks very much for your inputs. Would you mind if I repost this as a post citing you, your blog if you tell me?

      I realized that the comment I replied too is just copied from a blog. tsk tsk tsk

  9. […] today, I saw a comment in my post, “How to make Global Translator Plug-in compatible with adsense” that explains why this plug-in is bad for your blog with regards to search engine […]

  10. Thanks for this. It solved the mystery of why my Translate widget disappeared. You’d think Google would mention this in the help somewhere…

  11. […] Below are the problems faced by one blogger, Adnan who shared his experience through comment on the blog, silkenhut  […]

  12. Eu gosto deste blog, isso me mantém entretido

  13. thank you mutch
    but pls how i can delete plugin Global Translator safe 🙂

Leave a Reply