googletranslate2

Google Penalizes Bad Machine Translation

Planning to translate your business website into another language? Free, automatic translation tools like Google Translate might seem tempting, but here’s one more reason to avoid relying on them: Google doesn’t like it. And if Google doesn’t like it, you’d better not do it, at least not if you value your website traffic.

It seems odd that the search engine gods would issue penalties for using Google’s own product, but apparently search engine spammers have been publishing lots of awkward, error-laden machine translated content.  To keep their results as accurate as possible, Google classifies automatically translated content as “automatically generated content,” which violates their webmaster guidelines.

That means that poorly translated content could seriously impact your rankings.  Also,  as Ariel Hochstadt pointed out in Search Engine Land, if you’ve monetized your site using AdSense, your account could be disabled for including “websites with gibberish content that makes no sense or seems auto-generated.”

Ironically, Google itself has started using automatically generated content on its own properties, like the Google Play store. However, as Search Engine Land points out, it appears that Google is using some sort of new and improved Google Translate that’s not available to the general public.

Why not release the latest and greatest Translate tool? Hochstadt speculates:

My best bet is that Google is afraid of mass spamming that could be hard to identify. Nevertheless, if they think it is good enough for them to publish it on their Android and Chrome stores, why wouldn’t they allow others to do the same in Google Translate? Knowing Google, you probably are aware that their rules sometimes oblige us, but don’t apply to those located in Mountain View.

Fair or not, at least for the time being, you’re better off using a professional translator, or at the very least having the final product reviewed by someone who is fluent in your target language and able to correct any mistakes.

2 replies

Leave a Reply

Want to join the discussion?
Feel free to contribute!

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>