Violation Detected On Pages Targeted by Google. Here’s How To Fix It.

Pages with Google ads may not include

  1. Adult themes in family content
  2. Pornography, adult or mature content
  3. Shocking content
  4. Content that threatens or advocates for harm on oneself or others
  5. Content that harasses, intimidates or bullies an individual or group of individuals
  6. Content that incites hatred against, promotes discrimination of or disparages an individual or group on the basis of their race or ethnic origin, religion, disability, age, nationality, veteran status, sexual orientation, gender, gender identity, or other characteristics that are associated with systemic discrimination or marginalization
  7. Excessive profanity
  8. Hacking/cracking content
  9. Software or other content that violates the Unwanted Software Policy
  10. Malware or adware
  11. Illicit drugs and drug paraphernalia content
  12. Content that promotes, sells or advertises products obtained from endangered or threatened species.
  13. Online sale of alcoholic beverages
  14. Sales of tobacco or tobacco-related products
  15. Sales of prescription drugs
  16. Sales of weapons or ammunition (e.g., firearms, firearm components, fighting knives, stun guns)
  17. Instructions on the enhancement or self-assembly of weapons (e.g., 3D printing of weapons, conversion kits, 80% finished parts)
  18. Sales or distribution of coursework or student essays
  19. Content regarding programs which compensate users for clicking ads or offers, performing searches, surfing websites or reading emails
  20. Any other content that is illegal, promotes illegal activity or infringes on the legal rights of others

See: https://support.google.com/adsense/answer/48182

How to Address the Issue?

Note: there are times when the controversial words cannot be found in the site content itself because it may also appear in the script, style tags, or in inline comments. In this case, right click on your webpage and view page source to find the words being flagged.

You have 2 options: (2) Delete the violating webpages; or (2) deploy Key-value pairs (KVPs):

Watch this quick tutorial on how to stop Google from Serving on pages with violations:

Step 1: Open your Ad Manager account

Step 2: Go to Inventory > Key-Values

Step 3: Add a key “google” + values: no, 0, off

key-values google

Step 4: Open each of your Google line items (Ad Exchange and/or AdSense).

Step 5: Add a Key-value targeting “google” IS NOT “0, no, off’.

google values

Step 6: On your webpages where the violation is detected, deploy the Key-value in the HEADER:

ONpage setup (sample):

<script async=’async’ src=’https://www.googletagservices.com/tag/js/gpt.js’></script>

<script>

var googletag = googletag || {};

googletag.cmd = googletag.cmd || [];

</script>

<script>

googletag.cmd.push(function() {

googletag.defineSlot(‘/2602542/af2_article_btf_600x257’, [600, 257], ‘div-gpt-ad-1544046962927-0’).addService(googletag.pubads());

googletag.pubads().enableSingleRequest();

googletag.pubads().setTargeting(‘google’, [‘0’, ‘no’, ‘off’]);

googletag.enableServices();

});

</script>

OFF-page setup:

Implement this right above your Header Bidding header script.

window.m2hb = window.m2hb || {};

window.m2hb.kvps = {‘google’: ‘no’};

To target specific Article IDs:

Deploy right above your Header Bidding script, change the 1, 2, 3, 4 to be the article IDs.

<? if (in_array(get_the_ID(), array(1, 2, 3, 4))) { ?>

<script type=”text-javascript”>

window.m2hb = window.m2hb || {};

window.m2hb.kvps = window.m2hb.kvps || {};

window.m2hb.kvps.google = ‘no’;

</script>

<? } ?>

In case of multiple Key-value pairs (KVPs):

Implement right above your header script, edit “key” and “value”.

<script type=”text/javascript”>

window.m2hb = window.m2hb || {};

window.m2hb.kvps = window.m2hb.kvps || {};

window.m2hb.kvps[‘key’] = ‘value’;

window.m2hb.kvps[‘key’] = ‘value’;

window.m2hb.kvps[‘key’] = ‘value’;

</script>

Step 7: Google line items will then stop serving on pages where Key-value pairs (KVPs) are deployed since the setting was set to ‘IS NOT’ (See Step 5)

Back to Notification Center