Cloaking brand name sites vs. risk of Blacklising from SEs

Cloaking Newbie looking for ways to reduce cloaking risks

[Drack_Ma]

I work for a company that has designed and launched several well known websites. I am interested in using cloaking methods to promote site and protect code.

Challenge: website address = company name and it would be a Very bad thing to get their domain blacklisted from SEs for using cloaking.

Proposed solution: Register a "throw away" domain name that includes keywords and relates to client website address. Cloak the "throw away" page. Then mirror most content from the client page onto the "throw away" domain. Add in a hearty sprinkling of keywords into the surrounding page text, short of spamming of course.

The original page that was mirrored from the client site would be a product index page that has all its links set to land people on the real client site.

All this in the hopes of insulating the client "name brand" domain address from having a chance of being blacklisted.

My question: Is this type of idea already in use?
Is it effective in achieving better rankings?
Are there variations of this idea ( or a completly different idea) that will accomplish the goal of insulating the "name brand" domain name from being blacklisted?

Any input around this issue would be very helpful.

[miles]

There is nothing new under the sun, it is called no frames pages. As far as picking a domain you are on the right track. Just remember to load the page with relevant text.

[Drack_Ma]

Thanks for the response Miles.

After rereading my post I believe it may not have been to clear. In a nutshell I am working for a client (ie namebrand.com). I am registering a throw away domain name (containing keywords relevant to namebrand.com like quality-widget.com)

Quality-widget.com will contain a cloaked mini-site (to hit the theme based engines)of pages optimized to the topic of Namebrand.com. The human side of Quality-widget.com will JS redirect users to namebrand.com.

Alternative two for the human page: Mirror content from namebrand.com onto quality-widget.com. All product links on quality-widget.com will forward viewers to detail pages of that product on namebrand.com

Alternative two is quite a bit more work intensive but is done in an effort to further insulate namebrand.com from being blacklisted.

The questions:
1. Is one method better than the other? Why?
2. Is there a better way to both cloak namebrand.com and insulate it from being blacklisted by SEs?

Opinions are appreciated, Experiences are Golden.

[Drack_Ma]

[tedster]

>> Alternative two for the human page: Mirror content from namebrand.com onto quality-widget.com. All product links on quality-widget.com will forward viewers to detail pages of that product on namebrand.com

Exact mirror pages can also cause problems if they are not done with some finesse.

I understand that Inktomi and AltaVista work to eliminate ALL duplicates and near-duplicates from their databases; they don't let even one copy of a detected duplicate remain.

I'd suggest varying the content on each quality-widget.com page by a good percentage, and not just changing a few words on the brandname.com pages to create the new page.