Last May 26, Google announced that its Google Translate API, one of the most popular APIs of the search giant, has been officialy deprecated.
The Translate API is extensively used by a wide array of Web publishers and applications focused on the creation of multilingual contents. It seems that this use was so huge that even the Palo Alto behemoth was “burdened”, as the official note states:
Important: The Google Translate API has been officially deprecated as of May 26, 2011. Due to the substantial economic burden caused by extensive abuse, the number of requests you may make per day will be limited and the API will be shut off completely on December 1, 2011. For website translations, we encourage you to use the Google Translate Element.
In fact, as one can read in the note, the translation services won’t be entirely shutdown, only its API. Google Translate Element will be an option for those who will still want to use the Google translation services. It allows the automatic translation of Web sites without using the API directly.
Nevertheless, plugins like WordPress Global Translator will not be able to access the Google Translate API, from December on. Luckily, in this case, the plugin already offers Babel Fish, Promt, and FreeTranslations engines as alternatives to Google translation services. The same can’t be told about other plugins though.
Anyway, it’s bad news for anyone who strongly bets on the cloud and its so-called advantages.
Together with the Translate API, Google has also deprecated and scheduled for shutdown on December other APIs (though those are not so popular as the Translation API):
Another seven APIs have been deprecated by Google, but still not scheduled for shutdown:
Which one will be next on queue? Google Maps? Make your own bet.