Help with cloaking adwords accounts

Hi, So what I was hoping to do is set up lets say a widget silo site. Within the widget silo site I will add CPA offers like email submits etc. The thing I was wondering was, if I'm using throw away adword accounts ($150 per account) and hammer the adwords campaign to direct straight through to the CPA offer, should I be cloaking the offer link so Google cant see me directing straight through to the offer, or is this even needed?

WhatI'm trying to figure out is, should I be cloaking all my links (and any instructions on this would be VERY helpful) so Google doesn't link the throwaway account with the widget site I'm creating, and therefore, if I start a new adwords account they wont ban me for linking to the same site CPA offer as before but on a different account?

If anyone has any info on how to best implement a Google adwords CPA strategy using different adwords accounts would be great. I have all the steps in place, all I need now is the steps to go from the CPA offer page and add this into my newly formed throwaway adwords account without getting in trouble with either google or my affiliate manager.

Hope this makes sense

Thanks

Link to a page in adwords, make sure the domain link and the domain url are the same.

When your ads are approved, use a Javascript redirect on the HTML of the domain link to your CPA page. Dont modify the ad at any point as the google crawlers will crawl your link and disable your ad.

So for example

PPC AD -> http://www.dummydomain.com/INDEX.HTML

AD APPROVED

http://www.dummydomain.com/INDEX.HTML -> JS REDIRECT -> http://www.cpadomain.com/INDEX.HTML

Voila.

Actually, in my experience this is not as safe as doing some form of cloaking -- could be a server side redirect, a content replacement, etc.

If you are going to serve javascript the landing page HAS to have an external javascript call to "file.js" initially. Initially file.js does not do the redirect. Then after the ads are approved you change the contents of file.js to do the client side redirect.

The point here is that you will get spider activity of some kind with Google throughout the campaign running. You do not want to give the bot two different versions of the destination page ideally.

Serve google bots diferent redirection and u wont get caught

qcp860 said:

Actually, in my experience this is not as safe as doing some form of cloaking -- could be a server side redirect, a content replacement, etc.

If you are going to serve javascript the landing page HAS to have an external javascript call to "file.js" initially. Initially file.js does not do the redirect. Then after the ads are approved you change the contents of file.js to do the client side redirect.

The point here is that you will get spider activity of some kind with Google throughout the campaign running. You do not want to give the bot two different versions of the destination page ideally.

Click to expand...

So you recommend just using the wpcloaker? I looked through it, and it seems like the answer. However, if im sending traffic to a cpa offer landing page, and cloaking using wpcloaker, how would this pass the manual verification from google (human checking the ad)?

SEM_Blackhat said:

firstly, let the ads get approved, then use any cloaking software such as wpcloaker to redirect to the cpa offer for the visitor whereas spider/crawler to the other page.

i am also working on it, please share your experience on it.

Click to expand...

thinking about using wpcloaker, looks like the cheapest and easiest tool to use. S youd recommend making 2 separate landing pages, 1 for google, 1 for viewer?

Get yourselves a good cloaker. Unless you know how things work at the programming level, then you're going to have a bad time trying to do this yourself.

However, if im sending traffic to a cpa offer landing page, and cloaking using wpcloaker, how would this pass the manual verification from google (human checking the ad)?

There is no magic method here. The two biggest risks are passing manual reviews and dealing with competitors filing complaints (which are really another manual review). Remember, no matter what you do, cloaking will always be risky.

The simplest thing to do is to set up a compliant campaign and not cloak initially until the manual review is likely over. You can monitor your stats traffic for this or with a mature account just wait 1-2 days, etc. Then turn cloaking on and adjust bid prices, etc. accordingly. I've had customers also use variations other than IP detection with success.

Try use iframe on all of page. In this page load your page dummydomain. /index.html

mrblackjack said:

For Adwords cloaking you don't need referral checks nor updated IP lists, there is an ingenious method to cloak Adowrds, 100% safe just right under their nose and I'm doing it for a long time. Hit me with a PM and I might help you.

Click to expand...

Can you PM me? I have not enough posts.

if you dont have much knowledge about how programming works, you must get yourself a good cloaker.

WP Link Engine.

User Agent -

kw-lp-suggest
*msnbot*
Python-urllib/1.17
*Python*
alexa
askjeeves
bluecoat
fast
firefly
froogle
google
infoseek
inktomi
looksmart
mediapartners
nationaldirectory
rabaz
scooter
sogou
spade
tecnoseek
teoma
webbug
*galaxy.com
zyborg
bot
*Android* OPtional
*iPhone* Optional
*im.so.uberleet.org* - xhamster
*MarketDefenderBot* - Internal






IP Table - Organization
61.0.0.0-61.255.255.255 Asia Pacific Network Information Centre (APNIC)
217.0.0.0-217.255.255.255 RIPE Network Coordination Centre
208.80.192.0-208.80.199.255 Websense, Inc
192.132.210.0-192.132.210.255 Websense, Inc
206.169.148.0-206.169.148.255 Websense, Inc
204.15.64.0-204.15.71.255 Websense, Inc
208.87.232.0-208.87.239.255 SurfControl, Inc.
150.1.0.0-150.101.255.255 APNIC
65.208.151.112-65.208.151.119 Kintiskton LLC
66.249.64.0-66.249.95.255 Google
115.0.0.0-115.255.255.255 APNIC
70.90.219.72-70.90.219.79 Google
216.104.0.0-216.104.31.255 Trend Micro Incorporated
209.85.128.0-209.85.255.255 Google
64.233.160.0-64.233.191.255 Google
74.125.0.0-74.125.255.255 Google
72.14.192.0-72.14.255.255 Google
70.32.128.0-70.32.159.255 Google
113.0.0.0-113.255.255.255 APNIC
70.90.219.48-70.90.219.55 Google
70.89.39.152-70.89.39.159 Google
76.74.152.0-76.74.159.255 ServerBeach
216.239.32.0-216.239.63.255 Google
173.194.0.0-173.194.255.255 Google
65.167.144.64-65.167.144.79 Google
65.170.13.0-65.170.13.15 Google
63.166.17.128-63.166.17.255 Google
65.171.1.144-65.171.1.159 Google
64.9.224.0-64.9.255.255 Google
63.161.156.0-63.161.156.255 Google
199.87.241.32-199.87.241.63 Google
65.214.112.96-65.214.112.127 Google
66.192.134.32-66.192.134.47 Google
65.196.235.32-65.196.235.47 Google
64.128.207.160-64.128.207.175 Google
63.84.190.224-63.84.190.255 Google
65.221.133.176-65.221.133.191 Google
65.223.8.48-65.223.8.63 Google
65.211.194.96-65.211.194.111 Google
65.214.255.96-65.214.255.111 Google
64.124.229.168-64.124.229.175 Google
209.249.73.64-209.249.73.71 Google
64.124.112.24-64.124.112.31 GOOGLE
114.0.0.0-114.255.255.255 APNIC
207.46.0.0-207.46.255.255 Microsoft Corp
65.52.0.0-65.55.255.255 Microsoft Corp
157.54.0.0-157.60.255.255 Microsoft Corp
64.233.160.0-64.233.191.255 Google
216.239.32.0-216.239.63.255 Google
111.13.8.0-111.13.8.100 APNIC
72.8.185.215
150.70.172.109
204.111.103.32 Shentel Service Company
216.119.147.213 Hosting Services, Inc.
24.102.195.210 PenTeleData Inc
64.12.116.80 AOL
8.28.16.254 Level 3 Communications, Inc.
204.236.226.210 Amazon.com
123.125.71.43 APNIC
69.28.58.26 Los Angeles Internet Exchange
76.226.226.17 PPPox se5.sfldmi
150.70.172.206 APNIC
180.76.5.0-180.76.6.255 Baidu
192.41.0.0-192.41.101.255 Facebook
76.72.165.0-76.72.165.127 Facebook
66.93.78.176-66.93.78.183 Facebook
65.204.104.128-65.204.104.143 Facebook
66.92.180.48-66.92.180.63 Facebook
67.200.105.48-67.200.105.51 Facebook
65.201.208.24-65.201.208.31 Facebook
66.220.144.0-66.220.159.255 Facebook
69.171.224.0-69.171.255.255 Facebook
74.119.76.0-74.119.79.255 Facebook
204.15.20.0-204.15.23.255 Facebook
173.252.64.0-173.252.127.255 Facebook
67.220.103.240-67.220.103.255
192.41.0.0-192.41.101.255
199.19.248.0-199.19.255.255 bluecoat

Hostname -
*as13448*
*websense*
*blackspider*
*amazonaws*
*sprintlink.com
*microsoft.com
*msnbot*
*trendnet.org
wtp-g3-maya3.sjdc
*bluecoat*
*marshal.com
*hinet.net
*syndigonetworks.com*
*yahoo.net
*teliacarrier.com
*1e100.net
*yahoo.com
corp.yahoo.com
wa.comcast.net Microsoft checks for cloaking with WA Comcast
quadranet
metricsdirect
friendfeed-media.com
*fb.com*
*Tfbnet.net*
*tfbnw.com*
*thefacebook.com*



Referer -
*websense*
http://www.google.com/url?sa=D&q=*
http://www.google.com/search?hl=en&q=*
*AccountBulkReviewUpload.aspx MSN
*charter.net Optional
*maya*
*click.scour.com
*scour.com
*charter.net Optional
dev.facebook
cs.facebook
/intern/ads/review.php
ads/adboard
cstools
intern.facebook
url?sa=d

Organisation
180
bluecoat
blue coat
dublin
facebook
google
microsoft
peak
services platform
trend
yahoo
websense
amazon
Precision Response
oneeighty


Referrer To Allow Through
http://www.facebook.com/ajax/emu/end.php*
http://apps.facebook.com/ajax/emu/end.php*

CPA Redirector 2

i was also thinking about the CPA redirector 2.. It works really well.