How to Cloak (stealth)

swiftmoney

swiftmoney

∞
Sep 14, 2011
999
8
0
I am wondering if anyone is familiar with a type of redirect that is undetectable by Google.

The point of the redirect will be to keep my main page indexed and to redirect all visitors to a landing page on a different domain, whilst remaining as undetectable as possible by both the visitor and Google.

Any help will be greatly appreciated.

P.S. A few hits on Payday Loans (UK) and you will see them in action. Would love to know how they do this as it would make my life a lot easier, at least for a while.

Cheers.
 


The common way is to have an iframe that takes up the entire screen, which loads the remote page. This is easily detectable by Google though, because they just look at the HTML code of your page, and see it's nothing more than one huge iframe.

The only real way is to have a PHP script or something that acts as a proxy, and fetches & displays the contents of the remote page. This is a bit more involved though, because it would have to scan the HTML code of the remote page for links to CSS, JS, images, etc... and change those to route through the proxy script as needed, etc.
 
It's not worth doing this type of cloaking. The only real way is to know what IPs Google use and that is a whack a mole game you'll eventually lose.
 
Look up the stuff fantomaster has posted over the years, he's at least the most outspoken cloaker in the industry. But as Alex said, you need a really good, up to date IP database of Google's spiders to make this work correctly.
 
Kiopa_Matt said:
The common way is to have an iframe that takes up the entire screen, which loads the remote page. This is easily detectable by Google though, because they just look at the HTML code of your page, and see it's nothing more than one huge iframe.

The only real way is to have a PHP script or something that acts as a proxy, and fetches & displays the contents of the remote page. This is a bit more involved though, because it would have to scan the HTML code of the remote page for links to CSS, JS, images, etc... and change those to route through the proxy script as needed, etc.
Click to expand...

XSLT - Wikipedia, the free encyclopedia
 
Depending on your setup, why redirect at all ?
Do it like OpenBH, show them your LP and hide the content with jquery.
 
mattseh said:
XSLT - Wikipedia, the free encyclopedia
Click to expand...

And your point is? What does that have to do with anything? Once I get this backlogged work out of the way, I'm starting a devel competition, with the winner getting bragging rights to being WF's best developer. Can't wait to mop the floor with you guys. :)

Anyway, for the rest, why wouldn't a simple proxy script work? If you visit http://domain.com/lp.php for example, it'll grab the HTML contents of the remote page, change the JS, CSS, image, etc... links to route through the proxy script as well, and display it?

There'll be an issue if there's any forms on the page that check the referring URL, but otherwise should be fine, no? Bit of a pain-in-the-ass project to change all links / references in real-time, but it should work, no? There's no way Google can detect that, as it's all happening on the server side. The page would load a bit slowly, but you can throw in caching features to get around that.
 
Kiopa_Matt said:
And your point is? What does that have to do with anything? Once I get this backlogged work out of the way, I'm starting a devel competition, with the winner getting bragging rights to being WF's best developer. Can't wait to mop the floor with you guys. :).
Click to expand...

10 PRINT "I WIN!"
20 GOTO 10
 
Kiopa_Matt said:
And your point is? What does that have to do with anything? Once I get this backlogged work out of the way, I'm starting a devel competition, with the winner getting bragging rights to being WF's best developer. Can't wait to mop the floor with you guys. :)

Anyway, for the rest, why wouldn't a simple proxy script work? If you visit http://domain.com/lp.php for example, it'll grab the HTML contents of the remote page, change the JS, CSS, image, etc... links to route through the proxy script as well, and display it?

There'll be an issue if there's any forms on the page that check the referring URL, but otherwise should be fine, no? Bit of a pain-in-the-ass project to change all links / references in real-time, but it should work, no? There's no way Google can detect that, as it's all happening on the server side. The page would load a bit slowly, but you can throw in caching features to get around that.
Click to expand...

What you're describing and what the OP is asking for are completely different things...I honestly have no idea where this tangent of yours came from.

Cloaking is a redirect game, not a proxied content game. You have two places to direct visitors: if they're a bot, show them your highly optimized content, if they're a human, redirect them to your product or offer.

That's literally it.
 
To go back to the original question...

You only want to redirect people who could take up your offer - how do they access the internet?

How about - if this is really about Uk payday loans - find out the top ten ISPs in the UK.

Then find out which IP ranges they use.

Then only redirect within those ranges.

You'll probably cover 80% of your demographic and I think googlebots won't be using those ranges.
Even a manual check should be ok? (especially if from india, US, etc).
 
Crispin said:
To go back to the original question...

You only want to redirect people who could take up your offer - how do they access the internet?

How about - if this is really about Uk payday loans - find out the top ten ISPs in the UK.

Then find out which IP ranges they use.

Then only redirect within those ranges.

You'll probably cover 80% of your demographic and I think googlebots won't be using those ranges.
Even a manual check should be ok? (especially if from india, US, etc).
Click to expand...

Also, most cloakers will drop a cookie and not redirect a second time. This will prevent (well, at least slow down) a manual checker just going back to the site again to figure out what just happened. The second time they load the site, they see the site...no redirect.

You can also not redirect direct traffic as well.

Lot's of fun things you can do really.
 
I agree with the point that you should cover only those IPs that google is using. Thats actually going to save time and efforts as well. Its simple and will work for atleast a small time.
 
You need to come up with a huge list of ips that google owns. The problem is that google will sometimes use other ips that you do not have in your list, to access your site.. meaning they will end up seeing what you are cloaking.
 
You must log in or register to reply here.
Top Bottom
Back