Use Chrome DevTools to troubleshoot issues with your ads not showing

Chrome DevTools is a set of web developer tools built directly into the Google Chrome browser. These tools let you inspect the rendered HTML (DOM) and network activity of your pages. You can use DevTools to troubleshoot ad serving issues.

Check that ad requests are being sent

The following steps show you how to use DevTools to check if ad requests are being sent from your page:

1. Visit the page that you want to investigate.
2. Open DevTools by right-clicking on the page and clicking Inspect. Alternatively, you can press Command+Option+C (Mac) or Control+Shift+C (Windows, Linux, Chrome OS).
3. Click the Network tab.
4. Enter ads? into the 'Filter' field.

   Any AdSense or Ad Manager ad requests that have been sent from your page are listed in the table of requests.

   
5. Review the list of ad requests:

   If you find:	It means that:
   An ad request that starts with ads?client	An AdSense ad request was sent from your page.
   No ad requests	No ad requests were sent from your page which means no ads will be returned to your page. Or there was an issue on the client side which prevented the ad request from being sent. We recommend that you: Review the code implementation guide to make sure that you've correctly implemented your ad units. Check for client-side errors as described below.
   An ad request in red that has a 'Status' of 403	The server received the ad request but responded that an ad shouldn't be served on your site or account. 'Status' 403 is usually returned due to policy enforcements or because your site hasn't been approved. We recommend that you: Verify that there are no policy enforcements on your site through your AdSense Policy centre. Check that your site has a status of 'ready' on your Sites page.
   An ad request that has a 'Status' of 200 but your ads are still not showing	You likely have problems with your ads.txt implementation. To resolve the issue, visit our ads.txt troubleshooter.

Check for client-side errors

Even if you've correctly implemented the AdSense ad code, it's possible that ad requests aren't being sent from your page due to a client-side error. This could be due to the browser (e.g. extensions) or errors from the validation checks implemented in the AdSense JavaScript (adsbygoogle.js).

The following steps show you how to use DevTools to check your page for client-side errors:

1. Visit the page that you want to investigate.
2. Open DevTools by right-clicking on the page and clicking Inspect. Alternatively, you can press Command+Option+C (Mac) or Control+Shift+C (Windows, Linux, Chrome OS).
3. Click the Console tab.
4. Check for the following errors:

   If you find:	It means that:
   ERR_BLOCKED_BY_CLIENT	The browser prevented adsbygoogle.js (the JavaScript used by AdSense to show ads) from being downloaded. Typically, this is due to an extension (e.g. an ad blocker) installed in the browser. Example: GET https://pagead2.googlesyndication.com/ pagead/js/adsbygoogle.js net::ERR_BLOCKED_BY_CLIENT
   An adsbygoogle.js error	The validation checks in adsbygoogle.js returned an error. These validation checks make sure that if an ad request is matched to an ad, then the ad can be placed. A common error occurs if AdSense tries to place a responsive ad on your page but there isn't enough available space to place the ad. Example: adsbygoogle.push() error: Fluid responsive ads must be at least 250px wide: availableWidth=0