Guest digilution Posted May 27, 2006 Share Posted May 27, 2006 Thought I would give my 2 cents Never Worry About Getting Banned from Adsense because You “Accidentally†Clicked On Your Own Ads It has come to our attention that invalid clicks have been generated on the Google ads on your site(s). We have therefore disabled your Google AdSense account. Please understand that this step was taken in an effort to protect the interest of the AdWords advertisers. A publisher's site may not have invalid clicks on any ad(s), including but not limited to clicks generated by: - a publisher on his own web pages - a publisher encouraging others to click on his ads - automated clicking programs or any other deceptive software - a publisher altering any portion of the ad code or changing the layout, behavior, targeting, or delivery of ads for any reason Practices such as these are in violation of the Google AdSense Terms and Conditions and program polices, which can be viewed at: https://www.google.com/adsense/localized-terms?hl=en_US https://www.google.com/adsense/policies?hl=en_US Publishers disabled for invalid click activity are not allowed further participation in AdSense and do not receive any further payment. The earnings on your account will be properly returned to the affected advertisers. Adsense and contextual advertisements are driven primarily by Javascript. Basically, in order for Adsense or contextual ads to load, your browser needs Javacript enabled! Permanently block Adsense ads (or any other contextual ad you choose) from ever loading on your computer … no matter which browser, software program, or anything you use! Here’s how it works: Windows uses what’s known as a “hosts†file to determine the relationship between IP addresses and hostnames. In layman terms, it simply means that your computer will associate an “IP address†to a particular “hostname†(like pagead.googlesyndication.com) within the “hosts†file. Normally, your “hosts†file should be empty, except for the following line: 127.0.0.1 localhost Basically, the above IP address and hostname combination tells your computer that “localhost†points to 127.0.0.1 (your computer’s IP address). Now, how can you use this to your advantage? Solution: Assign every known “hostname†that your Adsense or contextual ads are loading from to your computer’s IP address (127.0.0.1). So instead of “loading†the hostname by visiting the actual IP address, your computer will go to 127.0.0.1… and the actual ads will NEVER get retrieved from Adsense’s servers. Now, this might seem complicated, but don’t worry. Here’s where you can find your “hosts†file for different operating systems: Windows XP: C:\WINDOWS\system32\drivers\etc Windows 2000: C:\WINNT\system32\drivers\etc Windows 98 or ME: C:\WINDOWS\ Once you locate your “hosts†file, right-click and choose “Openâ€, then choose “Notepad†to open the file. There’s only 1 entry in your “hosts†file – the default “127.0.0.1 localhost†entry. Here’s what you want to do: Go to the last empty line in your “hosts†file and add a list of “IP Address – Hostname†combinations you want It’s as simple as typing in “127.0.0.1†and then following it with 2 spaces and the “hostname†of the contextual advertising service you want to block. # Copyright © 1993-1999 Microsoft Corp. # # This is a sample HOSTS file used by Microsoft TCP/IP for Windows. # # This file contains the mappings of IP addresses to host names. Each # entry should be kept on an individual line. The IP address should # be placed in the first column followed by the corresponding host name. # The IP address and the host name should be separated by at least one # space. # # Additionally, comments (such as these) may be inserted on individual # lines or following the machine name denoted by a '#' symbol. # # For example: # # 102.54.94.97 rhino.acme.com # source server # 38.25.63.10 x.acme.com # x client host 127.0.0.1 localhost 127.0.0.1 adwords.google.com #[Gmail ads] 127.0.0.1 pagead.googlesyndication.com 127.0.0.1 pagead2.googlesyndication.com #[Google AdWords] 127.0.0.1 syndicate.googlesyndication.com 127.0.0.1 syndicate2.googlesyndication.com 127.0.0.1 googlesyndication.com 127.0.0.1 adservices.google.com 127.0.0.1 syndicate.google.com 127.0.0.1 syndicate2.google.com 127.0.0.1 ssl.google-analytics.com 127.0.0.1 www.google-analytics.com #[Google Analytics] 127.0.0.1 google-analytics.com 127.0.0.1 imageads.googleadservices.com 127.0.0.1 imageads1.googleadservices.com 127.0.0.1 imageads2.googleadservices.com 127.0.0.1 imageads3.googleadservices.com 127.0.0.1 imageads4.googleadservices.com 127.0.0.1 imageads5.googleadservices.com 127.0.0.1 imageads6.googleadservices.com 127.0.0.1 imageads7.googleadservices.com 127.0.0.1 imageads8.googleadservices.com 127.0.0.1 imageads9.googleadservices.com 127.0.0.1 www.googleadservices.com 127.0.0.1 apps5.oingo.com 127.0.0.1 oingo.com 127.0.0.1 www.oingo.com 127.0.0.1 service.urchin.com #[urchin Tracking Module] 127.0.0.1 ads.chitika.net #[iE-SpyAd] 127.0.0.1 ads1.chitika.net 127.0.0.1 blogads.chitika.net 127.0.0.1 ca.chitika.net 127.0.0.1 mm.chitika.net 127.0.0.1 scripts.chitika.net :wub: Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.