|
That's my stand too. But if hotlink protection is turned on, what we're basically doing is cloaking.
If we take a regular html page as an example. You serve Google one thing and the surfer will see something else, big fat ban from Google.
If we do the same thing for images (hotlink protection turned on), will we sooner or later go the same route as with serving different text content? Banned from the SE.
I can see how it will become that. If we don't want the images to be crawled by the SE, we should've add a block for them in robots.txt.
|