Javascript redirect
I write a lot about javascript redirects, and some may not understand why they’re significant.
So this page is to explain them to those who are lost.
Javascript is easy to use for spammers, because all graphical browsers will understand the simpler functions.
And search engine spiders ignored javascript totally in the past. Maybe they still do, but the spammers are taking no chances, so their javascript redirects are usually broken up into little pieces that are then reassembled so they’re hard to put together for a dumb bot.
I’m sure the search engines are wise to redirect cloaking, so the bots may be looking for that.
When you check a spamvertized page, you’ll see the page the spammer wants you to see, when a javascript redirect is in effect. That means they’ll try to fool you into thinking the site is removed, non-active or any variant in between - if you click on the spam link from your blog or stats. But if you access the same page from a link on a search engine, or even fake the referrer, you’ll see the page the spammers intend to show the end visitor.
The search engine spiders will never see that page. They’ll see the originally spamvertized page, which is usually full of text - search engine spider meat.
Cloaking can get you penalized in the search engines, and spamming can get you banned.
For that reason, spammers try to hide the real pages they’re spamming as best they can, with redirects, cutout locations for affiliate ID’s etc. That’s in addition to javascript redirects to fool bloggers…