How to: fix “blank ads” Google AdSense

How to fix Rejected ad requests or “blank ads ”Google AdSense.  This problem happens one of my blogs/website. If this happen to your blogs with a thousand of post big money will losses to your website a day.

How to fix rejected ad request errors

When you see rejected ad request errors, it means your ad unit is crawling and targeting the wrong URL. This occurs when our URL detection has determined our ad unit is within an iframe, and has no content. This results in lower relevancy for your ads and lower revenue as we do not know the actual content of your page. When we are not able to determine the correct site information for an ad request, we serve “blank ads” that blend into the background of your pages.

According to support.google.com/adsense Reasons why you see rejected ad request errors:

Here are some possible reasons you're seeing these errors:
This occurs when the URL of the server from which the ad unit has been served differs from the URL of the actual page where the ad will be displayed.
Your ad code is nested within multiple iframes.
If your ad code is nested within multiple iframes, we are not able to determine the correct site information for an ad request.
You’re using a Supply-Side Platform (SSP).
If you make use of a Supply-Side Platform (ad servers, yield managers, etc.) for ad optimization and you're receiving rejected ad request errors with their URLs, please contact the Supply-Side Platform to determine the best way to ensure that the correct site information is passed in your ad requests.

Ways to fix rejected ad request errors

The method for fixing targeting depends on the domain that triggers the ad request error. In general, to fix these errors in AdSense and Ad Exchange, you will need to pass to AdSense and Ad Exchange, the URL of the actual page where your ad unit is located in the ad request.
If using DoubleClick for Publishers, please look into the following solutions:

• If using DART, you can pass the correct URL using the dc_ref parameter in conjunction with the google_page_url parameter in AdSense and Ad Exchange. For more information, access the DART for Publishers Help Center .

• If using Google Ad Manager, you can pass the correct URL by adding the following syntax to your DFP ad call:

GA_googleAddAdSensePageAttr("google_page_url", "URL");

• If using Google Publisher Tags, you can pass the correct URL by adding the following syntax to your DFP ad call:

googletag.pubads().set("page_url", "URL");

• If you have a mobile app, and are running AdSense and/or Ad Exchange web tags, you’ll need to switch those tags for the AdMob SDK.

If you have tag.admeld.com errors within your report, please contact your Admeld representative and ask for JavaScript tags as opposed to iFrame tags. This will remove the nesting iframe effect and should improve the targeting.
For all other domains, you will need to use google_page_url to target the correct URL.

Typical ad code:
<script type="text/javascript">
google_ad_client = "ca-pub-XXXXXXXXXXXX";
/* 728x90, creado 14/04/08 */
google_ad_slot = "XXXXXXXXXXXX";
google_ad_width = 728;
google_ad_height = 90;
</script>
<script type="text/javascript"
src="//pagead2.googlesyndication.com/pagead/show_ads.js">
</script>
Ad code with google_page_url added:
<script type="text/javascript">
google_ad_client = "ca-pub-XXXXXXXXXXXX";
/* 728x90, creado 14/04/08 */
google_ad_slot = "XXXXXXXXXXXX";
google_ad_width = 728;
google_ad_height = 90;
google_page_url = "http://myurl.com/fullpath";
</script>
<script type="text/javascript"
src="//pagead2.googlesyndication.com/pagead/show_ads.js">
</script>