When you are logged in and go to the frontend of your website you will see the Ad Health menu item. It has a few features and warns you about possible issues with ads. This page lists all features and describes the error messages.

The default no-issue state looks like this:

Ad Health menu item

When an issue occurs, the menu is highlighted, and the error is displayed:

ad health with error

Some of the errors also link to the page where you can either fix the problem or read more about it.

If you don’t see the toolbar

You can go to your Users > Your Profile and enable the Toolbar option.

toolbar option

Not every theme supports the admin bar, which I find very unfortunate since it not only includes helpful links and shortcuts but plugins like Advanced Ads also have a chance to help you identify issues. If the Toolbar option doesn’t help then please reach out to your theme developer and ask for Toolbar support.

Features

The Ad Health bar comes with some handy features.

Highlight Ads

Click this to highlight current ad positions. Useful to spot ad spaces that are created with Advanced Ads but not showing up, e.g., when the ad network failed. It does currently only work with ads injected through placements.

Debug DFP ads

This option only shows up when you are using ads managed with DoubleClick for publishers on your site. When you click on it, the DFP debug parameter will be added to the URL and the debug console will open.

Issues

The following list gives some more information about possible issues.

Ad blocker enabled

Problem: Your browser or firewall includes an ad blocker, and neither ads nor any ad related scripts load.

Solution: Switch off the ad blocker.

Ads are disabled in the content of this page

Problem: You enabled the option to hide ads in the content of the current page in the Ad Settings meta box.

Solution: Follow the link in the Ad Health menu to go to the correct box and disable the Disable ads on this page option.

Ads are disabled on all pages

Problem: No ads show up at all.

Solution: Go to Advanced Ads > Settings > General and disable the option to hide ads in the frontend.

Ads are disabled on non-singular pages

Problem: No ads show up on archive pages.

Solution: Go to Advanced Ads > Settings > General and disable the option to hide ads from non-singular pages.

Ads are disabled on this page

Problem: You enabled the option to hide ads on the current page in the Ad Settings meta box.

Solution: Follow the link in the Ad Health menu to go to the correct box and disable the Disable ads inside the content option.

Ads are disabled on 404 pages

Problem: You are currently seeing a 404 page, and no ads show up. It is a good thing, but we kept the warning in case you are wondering why no ads show up.

Solution: Go to Advanced Ads > Settings > General and disable the option to hide ads from 404 pages.

AdSense violation: Ad is hidden

This warning appears if an AdSense ad is technically loaded but hidden from the visitor. This is a violation of the AdSense terms because the impression is counted and an advertiser might have to pay for it.

The warning could be caused by a wrong setup in Advanced Ads, by a theme or another ad management plugin. Please use the ad unit ID given in the warning to identify the problematic ad.

In order to solve this, you should

  • not use AdSense ads in a slider
  • not use AdSense ads in positions that don‘t appear right away (Sticky and PopUps with the delay option enabled)
  • reach out to us directly if this is coming from another setup in Advanced Ads
  • manage all ads with Advanced Ads, if the ad that causes the warning is currently managed through your theme or another ad plugin

We are still investigating the impact on themes causing this problem and whether we are able to solve it on our end or together with theme developers. Please contact us if you see this warning and only use Advanced Ads to deliver your ads.

You can also disable AdSense-related warnings with the Disable violation warnings option in Advanced Ads > Settings > AdSense.

Auto ads code found

This message is not warning, because nothing should be wrong when you see it. It only lets you know that an AdSense Auto ads code was found.

This code is used to verify your AdSense account and to add Auto ads to your site.

You can change this in Advanced Ads > Settings > AdSense > Verification code and Auto ads.

It is also possible that you added this code through another plugin or directly in your theme.

For more details about AdSense Auto ads see this page.

Click Fraud Protection enabled

This warning appears if you enabled Click Fraud Protection in Advanced Ads > Settings > Pro and got banned from clicking too often on your own ads. This does not necessarily mean that other visitors also don’t see ads.

You can either delete all cookies in your browser or disable the CFP module in the settings.

Consent not given

The consent method was enabled in Advanced Ads > Settings > Privacy and you didn’t confirm that. You might not see ads due to the missing consent. You’ll find more information on this feature here.

Random AdSense ads

Problem: Ads from AdSense appear in random positions. These are set up automatically by AdSense.

Solution: Remove the Verification Code & Auto Ads option from Advanced Ads > Settings > AdSense or the Auto Ads feature in your AdSense account. Find more information about this here.

You can also disable AdSense-related warnings with the Disable violation warnings option in Advanced Ads > Settings > AdSense.

Set Disable Level Limitation to show more ads

Problem: You are using a content injection placement (e.g., Content, Below Content), but no ads are injected even though there are enough elements (e.g., paragraphs). It mostly happens when a plugin is wrapping the main content into multiple containers.

Solution: Go to Advanced Ads > Settings > General and activate the option Disable Level Limitation.

The current post ID is 0

Problem: The ID of the current page is 0, which means that no plugin can do anything with it. This can only be caused by a serious coding issue in a plugin or your theme.

We know that BuddyPress has plenty of pages that throw this error and it still seems to work in most cases. We still consider this an issue and reported it.

Solution: Find the causing plugin or theme and contact their developers about it.

The dom extension(s) is not loaded

Problem: Ads are not injected into the content of your page.

Solution: We rely on the common dom extension to inject ads. You can ask your hosting company to switch it on to fix the issue.

The following responsive AdSense ads are not showing up

You will see this warning if an AdSense ad is placed in a container that has a float CSS rule and therefore won’t show up since AdSense can’t determine the available size. Your theme developer should know how to fix it.

the_content filter does not exist

Problem: Ads cannot be injected automatically into the content of your site.

Solution: Read this section.

Visible ads should not use the Header placement

This warning appears (with the IDs of the ads behind them) if an ad is using the Header Code placement. This placement type is meant to deliver codes that are in the part of your site’s code where only invisible scripts and meta values belong to and not for visible ads at the top of the site.

Technically, visible ads go into between <body></body> tags, while scripts often belong between  <head></head>  tag. The Header Code placement uses the latter and should therefore not deliver images, text, or other visible elements and tags. It could still work as expected but would then create invalid HTML code.

If you believe that this message is wrong then please reach out.

There are a couple of methods to deliver visible ads in the header. Please follow this tutorial.

You look like a bot

This warning appears if the so-called User Agent of your browser is wrong and looking as if you are not a human. It could have been modified by a third party service or a plugin.

You might either want to fix the cause or just ignore the warning. The only real consequence is that you won’t see ads if they are disabled for bots or have impressions or clicks being tracked with the Tracking add-on.

Your website is using HTTPS, but the ad code contains HTTP and might not work

Problem: If your website uses HTTPS (which is good), all external resources should also use it or might not work.

Solution: Ask the ad provider if they have an ad code for HTTPS sites available. Learn more.

 Troubleshooting