| 8:44 pm on May 21, 2008 (gmt 0)|
Effective cloaking requires server-side solutions, and you must "keep up" with *all* of the search engine's IP address ranges and user-agents (some of which are exact browser user-agent spoofs).
| 9:29 am on May 22, 2008 (gmt 0)|
Thanks for reply,
I was intending to redirect real visitors to a different page but google would read the page and hopefully not realise that the page redirected. :)
| 8:56 pm on May 22, 2008 (gmt 0)|
That's not a very effective technique to use for Google. It's a good way to suffer a penalty.
| 3:26 pm on May 23, 2008 (gmt 0)|
eval( unescape( "%20... bunch of junk here..." ) );
You can try to hide it this way, it used to work pretty good, but not so much anymore.
| 8:43 pm on Jun 29, 2008 (gmt 0)|
Google sees EVERYTHING!
So if you think that you can hide a CD's worth of your fave group in your web space to share with your mates, think again as you are sharing it with the world.
Nothing in the google world is hidden, I spent about 3 weeks google hacking as its called. I didn't need to touch p2p networks for a while!
| 12:23 am on Jul 1, 2008 (gmt 0)|
*** I was intending to redirect real visitors to a different page but google would read the page and hopefully not realise that the page redirected. :) ***
Google specifically warns to NOT do this. It comes in the section about "sneaky redirects".
| 11:23 pm on Sep 19, 2008 (gmt 0)|
server side calling of a JS is better idea rather to display on the page.