Is your Google Ad Manager site approved, but ads still aren’t appearing on your website? Site approval is an important step in monetization, but it doesn’t guarantee that every ad request will return an ad or that every eligible creative will render successfully.

The cause could be an incorrect ad tag, a line item that isn’t eligible to deliver, an ad-serving restriction, an empty demand response, or a browser-side problem. The right fix depends on where the delivery process is failing.

In this guide, we’ll walk through how to troubleshoot a Google Ad Manager (GAM) site that is approved but not showing ads, using the checks available to publishers and ad operations teams.

1. Confirm Your Google Ad Manager Site Status

Start by confirming that the site is actually marked as ready. A website that appears in your inventory isn’t necessarily approved to serve ads.

1. Sign in to your Google Ad Manager account.
2. Navigate to Inventory → Sites.
3. Find the domain you want to monetize.
4. Review the available site status information and any associated warnings or issues.
5. If the site has a policy or approval issue, open Admin → Policy center and review the details shown for your account.

Google documents site statuses such as Getting ready, Ready, and Needs attention in its Manage sites in Ad Manager guide. A site marked Ready is eligible to serve ads, but that does not mean every request is guaranteed to receive an ad.

If the site is still under review, investigate the approval issue first. For a broader walkthrough, see our guide: Google Ad Manager Website Disapproved? How to Fix It .

2. Check Whether Ad Serving Is Restricted or Disabled

A site can be approved while ad serving is affected by a separate policy issue or account-level restriction. Don’t assume that the site approval status tells the whole story.

Check the Policy center and look for the exact status and issue details. Depending on what Google reports, you may see a situation such as:

• Disabled ad serving: Advertising is blocked on the affected site or app because of a policy issue.
• Restricted ad serving: Fewer advertisers or demand sources may be eligible to bid, which can reduce the number of ads available.
• Ad serving at risk: The issue needs attention to help prevent a future impact on serving.
• No site-level issue: You may need to investigate ad tags, inventory configuration, line-item eligibility, or demand.

These statuses are not interchangeable. Follow the action specified for the exact issue shown in your account rather than making unrelated changes. Google’s guide to policy issues and ad-serving statuses explains the available statuses and their effects.

3. Verify the Google Publisher Tag on Your Website

If the site is ready and no relevant restriction explains the problem, check whether the page is sending the expected ad requests.

Common implementation problems include:

• The wrong ad unit path or ad unit code is used in the tag.
• The requested ad size doesn’t match the configured slot or available creatives.
• The Google Publisher Tag (GPT) JavaScript fails to load or execute.
• The page calls the wrong ad slot, or a slot is defined but never displayed.
• A content security policy, browser extension, consent tool, or other script prevents the ad request or creative from loading.
• Recent website changes have broken the placement or altered the order in which scripts run.

How to check the ad tag

1. Open the affected webpage in a desktop browser.
2. Open the browser’s developer tools and select the Console tab.
3. Look for JavaScript errors related to Google Publisher Tag, the ad slot, or other scripts required by the placement.
4. Open the Network tab and reload the page.
5. Check whether the expected ad-related requests are made and whether they return errors or are blocked.
6. Compare the ad unit path and sizes in the page implementation with the inventory configuration in Ad Manager.

If you use a content management system, tag manager, header-bidding wrapper, or a third-party ad server, check the complete implementation rather than only the Google Ad Manager interface.

4. Use Google Ad Manager’s Delivery Troubleshooting Tools

If requests are being made but the expected ads don’t appear, use the available delivery tools to investigate which ads are eligible and why particular line items did or didn’t deliver.

For a webpage placement, Google’s troubleshooting tools can help you investigate questions such as:

• Which ads were eligible to deliver to the placement?
• Which ad or line item was selected?
• Why did another line item fail to deliver?
• Are the configured inventory, targeting, and creatives consistent with the request?

Use Google’s Inspect webpage ad delivery guide to get started with the webpage ads inspector and related delivery tools.

5. Check Line Items, Creatives, and Targeting

If your website is sending ad requests, the next question is whether an eligible line item can serve to those requests. A correctly installed tag does not guarantee that a campaign matches the request.

Review the following settings in Ad Manager:

• Line-item status: Confirm that the line item is active and isn’t paused, completed, or awaiting a required setup step.
• Flight dates: Verify that the campaign’s start and end dates include the current date.
• Targeting: Check ad units, geography, devices, key-values, inventory, and any other targeting criteria.
• Creative status: Confirm that the expected creative is associated with the line item and is eligible to serve.
• Creative sizes: Verify that the creative dimensions match the sizes requested by the ad slot.
• Delivery constraints: Review frequency caps, exclusions, competing line items, and other restrictions that could affect eligibility.

To identify the specific reason for non-delivery, open Delivery → Line items, select the affected line item, and review its Troubleshoot tab when available. Check Health history and Non-delivery causes for clues about recent changes and delivery blockers.

See Google’s official Troubleshoot Ad Manager line item delivery documentation for the available diagnostics and explanations.

6. Understand No Fill and Empty Ad Responses

Sometimes the ad request works, but no eligible ad is returned. This is commonly described as no fill. It is different from a page that never sends an ad request or a creative that fails to render after being selected.

Possible reasons include:

• No eligible demand is available for that impression.
• Targeting or creative-size restrictions leave few eligible candidates.
• Programmatic buyers do not bid on the request.
• Policy, privacy, consent, or ad-serving restrictions limit eligible demand.
• A line item or creative is not eligible for the particular request.

The right next step depends on the request and its delivery diagnostics. Check reporting and delivery tools to determine whether requests are being sent, whether ads are selected, and whether impressions are recorded. Don’t treat every empty response as a site-approval problem.

7. Check Consent, Browser Extensions, and Rendering Issues

If ads appear for some users but not others, or requests appear to succeed without a visible creative, compare the behavior across browsers and environments.

• Test the page in a clean browser profile without ad-blocking extensions.
• Check whether the consent management platform is blocking or delaying ad requests under the current consent state.
• Review console errors, blocked network requests, and JavaScript conflicts.
• Check whether CSS, lazy loading, or responsive layout changes are hiding or collapsing the ad container.
• Test the placement on the affected device and viewport size.

A creative may be selected or code may be served but fail to render successfully. Google discusses this distinction in its line-item delivery troubleshooting guide .

8. Check Reporting Before Making More Changes

Use Ad Manager reporting to compare ad requests, impressions, and other relevant metrics for the affected inventory. Where available, segment the report by ad unit, device, country, or another useful dimension to find patterns.

These are diagnostic clues, not definitive diagnoses. Use the actual request and delivery information in your account to confirm the cause.

9. When Should You Contact Google Ad Manager Support?

If the site is marked Ready, your implementation appears correct, and available diagnostics don’t explain why ads aren’t serving, prepare a concise troubleshooting record before contacting support.

Include the following information where relevant:

• The affected domain and page URL.
• The Ad Manager network and ad unit identifiers.
• The approximate time and timezone when the issue occurred.
• Whether the problem affects all placements, certain pages, or particular devices.
• Relevant ad-request errors, delivery-tool findings, and policy messages.
• Recent changes to tags, targeting, line items, or consent settings.

Use the support options available to your account. Google’s Google Ad Manager support guide explains available troubleshooting and support routes.

Frequently Asked Questions

Why are ads not showing even though my Google Ad Manager site is approved?

Approval makes a site eligible to serve ads, but actual delivery depends on factors such as valid ad requests, eligible demand, line-item targeting, creative configuration, and any applicable policy or serving restrictions. Diagnose the request and delivery path to find the specific cause.

Does a Ready status guarantee that ads will appear?

No. Ready indicates that the site has been approved and is eligible to serve ads. It does not guarantee that every ad request will receive an eligible ad or that every selected creative will render successfully.

How can I tell whether the problem is my ad tag or my line item?

Check whether the page sends the expected ad request. If no request is sent, investigate the tag and page implementation. If the request is sent, use Ad Manager’s delivery tools and line-item troubleshooting information to investigate eligibility and non-delivery causes.

Can policy issues stop ads on an approved site?

Yes. Site approval and the account’s current ad-serving status are separate checks. Review the Policy center and the specific status or issue details shown for the site or account.

What does no fill mean in Google Ad Manager?

No fill generally means an ad request did not receive an eligible ad. The cause may be limited demand, targeting, creative eligibility, or restrictions. Confirm the situation using available delivery diagnostics rather than assuming the site has lost approval.

Final Checklist

• Confirm that the site status is Ready.
• Review the Policy center for active restrictions or issues.
• Verify that the expected ad requests are being sent.
• Check ad unit paths, sizes, line items, and creative eligibility.
• Use the delivery tools to investigate non-delivery causes.
• Check browser errors, consent behavior, and creative rendering.
• Compare reporting data before making further configuration changes.

When a Google Ad Manager site is approved but ads aren’t showing, avoid changing multiple settings at once. Start with site and policy status, confirm that requests are being sent, and then follow the delivery diagnostics to isolate the problem. This approach helps publishers and ad operations teams find the actual cause instead of treating every serving issue as an approval problem.

Last reviewed: October 2026. Google Ad Manager interfaces and available troubleshooting options may change. Refer to the official Google documentation linked above for the latest instructions.