New answers tagged

2

"Cloaking" in this situation would be fine. When the user agent contains bot|crawl|slurp|spider you should not use session id parameters or check for cookies. You are delivering the same content to users and bots. Google won't have a problem with this particular cloak. I use a similar technique for deciding whether or not to use Data URI for the images ...


-1

If you are trying to hide something from Google crawler and want to show text only to the users of your website then this will be consider as clocking. Do not try this if this is the case.


2

Cloaking is when you present one page to a search engine that is different than what you present to users. What you are describing is something entirely different. I will explain. I describe in several answers here that Google does not match search terms directly to content. While it may seem that it does, the reality is that this notion derives from ...


2

Based on a strict reading of Google's webmaster guidelines and definitions it is considered cloaking, it may not have been designed to present alternate content to Google over the users but as it has that effect Google needs to treat it as such.


2

Per Google's definition, this could be considered cloaking. It really depends on how much the content varies and if it's consistent otherwise. There's bound to be some give but Google is the only one who can tell you if you've crossed it. Check Search Console for any Manual Actions.



Top 50 recent answers are included