Quote:
Originally Posted by ssandecki
Basically it's the practice of displaying one web page to one set of people and a totally different web page to another set of people. A more commonly usage is to show one web page to viewers and another to search engines crawlers.
|
Just to be a stickler for details, 'cloaking' usually means doing this in bad faith. If you use code to figure out whether the user agent ( browser, spider , feed reader ) supports Flash, and then send down an html version to people who don't, most people wouldn't call that cloaking. Or, if you figure out where the user is, geographically, by their IP address and send a version of the page in what you assume to be their language by default, or just adjust to the local time zone, that's probably not cloaking, either.
A real world example is experts-exchange.com: a forum about software development. They score well in Google, but where the answers to the question that starts each thread would go, there's an image of blurred text. A 'payment wall;' to get the answer, you need to join. If you click
cached from the serps, you get the answers.
Technically that's not a very different thing from defaulting collapsible lists to display: block when you know a browser doesn't support javascript to expand the list. That's perfectly legit ... just like putting a bunch of second level navigation links in a hidden div, as long as there's a way to unhide it. Like most menu systems.
In a seo sense, cloaking means tricking Google into thinking you have something really good, and then sending real people a give-me-money page. You would do this by using server-side code to sniff out the user agent string and then send down whatever version of the page you want that person/software to see. If you like free search engine traffic, though, tread lightly.