Stupid noob question.

proxyweb07

Newbie
Joined
Jan 31, 2008
Messages
20
Reaction score
3
I have a question that may seem stupid to some, but I will ask anyway.

Lets say you have a white hat site. whitehate.c0m
You want to create some cloaked pages on another domain cloaked.c0m
Now, if you just redirect the cloaked page to your whitehat site, search engines would be able to tell that you are cloaking, right?
What if you redirect the cloaked page to another redirect and put a robot.txt in it?
Code:
User-agent: *
Disallow: /
on redirect1.c0m
Then redirect that website to your whitehat site. I know that robot.txt is just a suggestion, but don't most crawlers follow it?
For even more security you could even redirect again redirect2.c0m


cloaked.c0m -> redirect1.c0m -> whitehate.c0m

or

cloaked.c0m -> redirect1.c0m -> redirect2.c0m -> whitehate.c0m


Would that drive in the traffic? Or just get whitehat.c0m delisted from SE's?
 
Lol.. I shouldn't post and copy+paste when I drink. whitehat.c0m

But seriously... Have any of you tried this? Will it work? I'm going to try it as soon as I finish the whiteHAT part of my SEO.
 
I'm not sure the way you're describing would be safe enough to protect your white hat site if its a good site that you really want to protect... personally, I like to use Web 2.0 sites as buffers for this.

For example, have your cloaked pages redirect to a Squidoo Lens or Weebly page, that then links back to your white hat site.

This way your white hat site is safe, yet you can still flow traffic and link juice down to it. And if any of your Web 2.0 pages gets flagged/penalized/whatever then who cares, just make another 1 or 100 of them tomorrow and you're still in business.
 
thanks scb335, was just looking into something like this myself. squidoo and weebly looks like a safe solution.
 
The method you are describing is not foolproof, there are better methods that can be found on this forum.
 
Back
Top