japanese - 2:12 pm on Mar 8, 2005 (gmt 0)

RETALIATION METHOD AVAILABLE AGAINST A SKYSCRAPER SITE

Bobby,

Good question about IP banning.

Stargeek,

Absolutely correct about robots having no referrer. And the IP banning method does not work. But if google implemented that googlebot must carry the referrer if a 302, 301 or meta refresh is involved, then we may have the answer. This is a brilliant suggestion and the best alternative yet.

The referrer can indeed be detected and presented with a 404. It would then be oh so simple by removing the hijack via the URL-CONSOLE BOT. Alas, the url-console will not accept the removal of a 302. I managed to block the IP of the console bot at .htacess, presented it with a 404, making it think the target page does not exist, it accepted the removal request, but google manually then denied the process. YOU CANNOT WIN. I wrote back in anger and they wrote back that they cannot comment about it.

======================

So, I think a top serverside expert is required here to explain exactly the process that takes place upon delivery of a 302 directive to googlebot.

Sure, there are a few ways to ban a referrer like a php script

<?

if(strstr($_SERVER['HTTP_REFERER'], 'badguy.com'))
{
header("Status: 404 Not Found");
header("HTTP/1.0 404 Not Found");
exit();
}

?>

The above php at the very top of your index page only stops a referrer and presents a magnificent 404 PAGE NOT FOUND but unfortunately googlebot has no referrer so we are back to square one.

.htaccess also provides some means to play a few tricks but again, prevention of googlebot accessing your site is not what you want.

In extreme cases where a site is completely damaged and you get ZERO hits a day and you see no hope after exhausting every means to correct the problem. There is a mega retaliation method that you can apply to the offending SKYSCRAPER that blasts out 302 directives.

I will not say where to get, or put up the script here, but a dos script on a refreshing dynamic IP can go to a skyscraper site and actually demand its results from its PAY PER CLICK AFFILIATES, the script is then presented with results for the scripts first random keywords. The script now clicks all pay per clicks results, it simultaneously demands another result for another keyword and again clicks the results presented. The cycle is fast and continues until the SKYSCRAPER sites bandwidth, msql functions are overloaded and depleted. Costing the affiliates thousands of dollars of damage to its customers. The spider script cannot be blocked because it will refresh its dynamic IP. The skyscraper webmaster normally is unavailable, probably in th bahamas enjoying his clicks revenues so the spider is totally free to do its job.

You arm yourself with a friends computer abroad also on a dynamic IP via remote access to his computer, you then point your spiders to the AFFILIATE COMPANIES that where feeding the SKYSCRAPER site with pay per click results and demand they stop providing the skyscraper. Make sure that their entire network is spidered 6 levels deep before you threaten them with 302 redirects. Give them 10 minutes to stop the feed.

Your spiders are not doing anything wrong because you are only looking for information on a mass scale. You are a fast reader and you like visiting the phenomenal skyscraper sites.

You now demand from the affiliate companies the removal of all 302 redirects used by the skyscraper site. You do not wish to communicate with the webmaster because it will be contradictory in terms. It is the affiliates duty to make sure that their feeds are not tampered with. Also spider the companies entire network of html pages and prepare your dead website to pump out 302 directives to all of the pages within their network. Don't forget to submit to search engines the vast numbers of internal pages of the affiliate companies networks, but be shure that it is not their pure html that you are submiting, you submit the deadly directives just like they done to you. Thousands of [ttccdeadsite.com...] ....and so on.

Many software exist that will do this automatically any level deep.

You will be threatened with legal action for causing 302 redirects to them. If you reply saying that they done it to you, they will say that they are a public company and you are not allowed to do a redirect to them.