Understand Adsense TOS and Stop violating Adsense Policies:
Invalid Clicks:
This is where the maximum Adsense account get into danger zone. Most of publisher who starts with Adsense, they usually ask their friend to click on Ads or click on their Ads from different I.P. If Adsense team detect such activity, they put your account in disable mode to ensure and safeguard their Advertisers.
Also, many new publishers ask their readers to click on ads, which is also discouraged by Adsense as stated in their program policies.
Using Adsense on unsupported language blog:
At the time of writing, Google doesn’t support all the languages to qualify for Adsense program. If you have approved AdSense account and you are using it to show it on the blog whose language don’t qualify Adsense TOS, then make changes asap. Eespecially, if you are using any method to make your blog multi-lingual and serving Ads on it, this will be consider as violation. That’s the reason; I removed Global Translator plugin some time back.
Maximum Adsense unit on a single page:
AdSense work on simple rule of 1-2-3 to define the maximum number of ad unit on a single page. Though, this is not any violation of Adsense policies as this could be a mistake, and AdSense won’t show more than three content ad unit unless you are a premium Adsense publisher.
Sending ads on Email:
Many publishers started the trend of sending AdSense adverts within email, and sometimes it goes viral. Google find it against the program policies.
Advertisement label:
Many publisher started using trick like click here, Click to see hot babe, and this also helped to encourage click. Encourage click? Oh, time to look at point 4. Or you use pop up script to show Adsense in pop-up and readers have to click on it to read the content, Ahh big no!
Competitive contextual advertisement:
Make sure you don’t use any other contextual advertisement program. Let Google ad sense by your only and favorite advertisement program. Though for monetization you can use many other ad networks and here are some which I have used, and they comply with Adsense TOS.Infolinks, BuySellads, Technorati Media, Viglink.
Altering the Adsense code:
So you are a programmer? Huh! doesn’t matter. Changing your Adsense code in any ways is not permitted by Google.
Shading with Image: Placing Google Adsense Image ad unit with adjacent image can be a great and smart move, but guess what? Do it and Google AdSense might ban you. Google TOS doesn’t allow use of shading your AdSense image ads with adjacent image.
Hosting Copyright content:
If you are running Adsense on a site which distribute copyright content like Movies, songs or any other files, you are most likely to get an instant ban. Adsense doesn’t allow putting Adsense on the site which distribute copyright stuff.
Linking to site who distribute Illegal and copyright content:
This is something which I got to know about in 2012 and one of the reasons why most of the sites are getting Adsense ban. If you are linking to sites like (Streaming movie), illegal or pirated software, Keygen sites, your AdSense serving might be disabled for that particular site. Here is the other type of content, which is not allowed for Adsense sites:
- Porn, Adult material
- Violent content
- Racial content
- Hacking/Cracking
- Gambling/Casino
- Pages selling Drugs, Alcohol (Beer or hard alcohol)
- Pages selling Weapons and ammunition
- Distribution of course work. Eg: Student essays
Above are just an example, and there could be more. So, you should avoid putting any such content on your blog or at least avoid serving Adsense on those pages.
Paid Traffic:
If you are buying traffic for your Adsense enabled sites, it’s not permitted according to AdSense TOS. Also, consider reading Adsense landing page Quality guidelines, which will give you ample amount of idea, what Google expect from your pages.
Making ads look like part of content:
You are free to make your ads blend with the content by changing the color or size, but don’t make it look exactly like content. In below image you can see what kind of mimicing is not acceptable:
