Cloaking is a high risk black hat process done by some web developers. Well, let’s put it all on simple words. Cloaking happens when the server gives the user one page and when Google Bot requests this very same page, the server gives Google a different page. Not only is this risky, but it is totally unethical and breaks Google rules! In fact, this whole process is a violation of Google quality guidelines and can get you and your webpage banned from Google search result pages.
But why is cloaking so bad? Well, Google considers cloaking bad because users might request a page about food and actually get a page about porn. Not only is this deceptive but it is also extremely annoying for people. After all, if you are looking for specific content you might as well open a page that is about it, and not about something different. Even if your server does cloaking and is not returning porn, or other bad things, there is no such thing as White-hat Cloaking, therefore all kinds of cloaking are against Google quality guidelines and general rules.
There are some good ways to keep you and your website away from this thing. First of all if you access Google Webmasters help you will b able to check your server with a tool that works just like Google Bot. Then you will be able to know if your page is under risks or if it is showing trustworthy content to both the public and Google Bot. Some people wonder if showing content in different languages and sending users to pages where their content is in fact in other languages is cloaking. Well do not worry, this is not considered cloaking, so go ahead and continue giving your public what they really want to see on the web!
(YouTube Release: August, 2011)