I already stopped using the Global Translator plugin for WordPress. For several days already, this Make Money Online blog was running without that plugin.
The Global Translator plugin for WordPress was actually generating pages of the blog by saving the translated pages into the server. Everyday, the blog automatically got more hundreds of pages. Most of these pages were indexed by Google and other search engines.
Some of the translated pages actually topped the several SERPs of Google. And from these SERPs our blog got more traffic and also it earned money through Adsense.
In other words, Global Translator plugin for WordPress has helped our blog earn money and increase our blog’s alexa ranking from 100,000Â to its current ranking which is 58,200 (current as of writing this post).
However, of these advantages of the said plugin, it also brought problems into our blog that might end up to a penalty from Google that would also lead to the lost of income, or it might end up being banned by the webhost or anything else.
Here are the problems caused by the said WordPress plugin:
Eats Up Server’s Space
The Global Translator plugin normally generate hundreds (thousands) of pages for your blog depending on how large is your blog. And those pages generated are being saved by the plugin into your server’s disk. In my blog’s case, each of the pages is about 1 MB in size.
For an account that only has limited disk space, saving hundreds of files of 1MB each could really mean a problem.
I was just fortunate that my webhost, the DreamHost, offer unlimited disk space to my account. That’s why I haven’t seen it yet as a threat to my webhosting account.
But who knows ifÂ one day, DreamHost will change their mind and ban me from their webhosting service just because my account is eating up too much disk space.
Slowed Down the Site or Blog
On Friday, April 9, 2010, Google revealed that the speed of loading of a site is now being considered by Google when ranking websites at the Google SERP. It’s not actually the only one signal used by Google but it’s one of the 200 signals considered by Google in deciding which website or webpage should be ranked first, then next, and so on.
Because of this new development in Google Search Engine algo, I immediately checked the loading speed of the blog. And I found out that the flags (images of different flags) of different nations displayed on the blog by the Global Translator plugin contributed the slowing down of the blog.
Now if I will allow this plugin to slow down the loading speed of this blog, then I might lose important SERPs that will lead to the decrease of the blog’s traffic. And losing traffic would also mean losing blog’s income.
Google Search Engine Penalty
It’s not yet proven that the continued use of the Global Translator plugin leads to the penalty imposed by the Google search engine to the blog that is using it. But I think, time will come that that it will really happen.
To let you know, through my Google Webmasters account, I found out that Google discovered at least 56,000 “404 error” that have been caused by this plugin. It happens when Google followed a link generated by this plugin leading to the untranslated page.
But this huge number of “404 error” was not just my problem that made me worry that Google might penalized my blog. Last April 14, 2010 Google emailed me through my Google Webmasters account telling that the Googlebot experienced problem in following a large number of links within the site.
Here’s the email that I received:
Googlebot encountered problems while crawling your site http://www.selaplana.com/.
Googlebot encountered extremely large numbers of links on your site. This may indicate a problem with your site’s URL structure. Googlebot may unnecessarily be crawling a large number of distinct URLs that point to identical or similar content, or crawling parts of your site that are not intended to be crawled by Googlebot. As a result Googlebot may consume much more bandwidth than necessary, or may be unable to completely index all of the content on your site.
Google provided me the list of pages that Google thought are not necessarily be crawled. And all the pages listed are those generated by the Global Translator plugin.
There are other two issues that have talked by bloggers around the world regarding this plugin.
- The terms and conditions provided by the Google’s Language API prohibit anyone to save translations into the disk or any form or device more than a certain period.
- Some languages are not supported by Google Adsense.
But these two didn’t worry me because I made sure that the settings I set for the Global Translator plugin are in accordance with the Google terms.
Only the three problems caused by the plugin that I have discussed above really made me decide to stop using the said plugin.