Welcome to WebmasterWorld Guest from 126.96.36.199
Forum Moderators: open
It looks like really sloppy cloaking job. The Google cache shows what should be the cloaked page. The publicly displayed pages look very similar to the actual client site, but when one clicks "view source" it shows the code the spider sees. When you have a page displayed in the browser, how is it possible to hit view source and see the code that does not make up that page you are viewing, but is fed to Google and the rest of the engines?
The cloaked pages showing up in Google cache are just a bunch of link spamming techniques with lots of anchor text pointing back to the doorway it's located on and of course repeated link text to the other couple hundred doorways in the network. Seems like if they are gonna cloak, they ought to hide the spider food from the view source button and the Google cache, no?
disadvantages - duplicate content in top results :( the real site already ranks better than this massive frame site (in most places) so it may get flaged through human review and tossed. No directory except for LookSmart:) is likely to take the mirror. It's only showing up in one engine, except for a few pages in the BOW. ODP shot it down. It's not going to get much link pop, likely to be the reason the real site without all the frame stuff and link spam is ranking better on most phrases.