Ad Manager Site "Needs Attention": Causes and Fixes

Adding a site to Google Ad Manager is quick. Getting it to Ready is the part that tests your patience. If your site is stuck in Needs attention or has sat in Getting ready longer than you expected, this guide explains what each status means, the three causes behind most stuck sites, and how to request another review once you have fixed things. For a broader look at why a whole account may not be ready yet, see our guide on common reasons an account is not ready yet. This one sticks to the mechanics of the site review itself.

The three statuses: Needs attention, Getting ready, Ready

When you add a site under Inventory > Sites, Google reviews it for compliance with Ad Manager policies. Google's help center describes three statuses:

MCM child sites added by a parent under Manage Inventory have one more status, Requires review, which simply means the child site has not been checked yet and the parent needs to start the review.

For standard publishers, Google also asks you to place a Google Publisher Tag (GPT) on the live site, even a 1x1 tag, so the crawler is triggered. It must be on the real site, not a test page, and called on page load without waiting for another event. A site with no working tag can sit unreviewed simply because nothing tells Google to look.

How long review normally takes

Google publishes two windows:

• Sites in Ad Manager: usually a few days, but it could take up to 2 to 4 weeks.
• MCM child sites (Manage Inventory): usually a few days, but in some cases up to 2 weeks.

Two habits make reviews slower, not faster. Google specifically warns that removing a child site and resubmitting it can delay the process. And repeated failed requests can lock the review button for a time, as explained below. When the clock is inside those windows, the right move is usually to wait.

If you are planning a full move to Ad Exchange, our AdSense to AdX timeline shows how the site review fits with the other steps.

Cause 1: ads.txt

Ownership verification through ads.txt is one of the named reasons for Needs attention, and it is the easiest one to fix.

Check these points:

• The file is at the root domain. Open https://yourdomain.com/ads.txt in a browser. You should see plain text, not a 404 page or your home page.
• Your publisher ID is in it. For a standard account, that is your own google.com, pub-... line copied from your account.
• Under MCM, the partner's line is there too. For Manage Inventory child sites, Google runs an automatic ownership check that looks for an ads.txt file with the parent's publisher ID. If it is missing, the parent can copy the required text from the site's page and send it to you.
• Crawlers can reach it. No geofence, robots.txt rule or bot challenge in front of the file.

Google notes that ads.txt changes for child sites can take a few days to process. Once the line is in place, the parent can use Check for updates on the child site while its status is Requires review or Needs attention.

Our step-by-step guide to fixing ads.txt "Not found" covers redirects, platforms and crawl errors in detail.

Cause 2: policy or content issues

The second group of causes is policy. Google lists policy violations and low-value content among the reasons for Needs attention.

To find the specific problem, go to Admin > Policy center and click Fix in the "Action" column next to the site. The Issue details page describes what Google found, and the "View issue" column can show screenshots of examples. Read the description carefully: issues can also come from ad requests on pages you have embedded into other sites.

The most common content-level problems for sites moving up from AdSense include:

• Low-value or thin content. Google Publisher Policies do not allow Google-served ads on screens without publisher content, with low-value content, under construction, or used mainly for alerts or navigation. Our guide to low-value content explains what reviewers tend to flag.
• Ad placement. Ads that overlay or sit next to navigation or action items in a way that may cause unintended clicks, or that push content off the screen.
• Restricted or prohibited content that conflicts with Google's publisher policies.

Fix the actual pages, not just the examples in the screenshots. A reviewer will look at the site as a whole.

Cause 3: ownership and site access

The third cause is that Google cannot confirm the site is yours to monetize, or cannot read it at all.

• Crawl access. Google's child-site instructions are blunt: if robots.txt disallows all agents or Google's crawlers, the site review will fail. Google also notes that the site status does not explicitly say when a crawl failed, so this is easy to miss. The same applies to firewalls, country blocks or login walls in front of your pages.
• Ownership checks for MCM child sites. Under Manage Inventory, ownership can be verified in one of three ways: an ads.txt line, a GPT tag that includes both the parent's and the child's network codes, or an HTML meta tag with the parent's publisher ID or network code.
• Right domain, right account. Add the top-level domain, such as example.com, without prefixes. If the site was already added elsewhere in Ad Manager, Google shows a warning, and moving it may disrupt serving and require retagging.

MCM policies also require that a child owns all of its child inventory, including root domains, and that the inventory has not been previously disapproved by Google. If either is in doubt, sort that out before you request a review.

Requesting a review after fixing

Fixing the issue is only half the job. Google states that you must request a review for each site with a policy enforcement in your Policy center for ad serving to continue on that site.

The steps, from Google's help center:

1. Sign in to Ad Manager and go to Admin > Policy center.
2. Click Fix next to the site.
3. In the "Issues found" section, click Start review process.
4. Pick the reason that applies: you removed the ad code, you fixed the violations, or you believe the violations are not present on the page.
5. Tick the confirmation box and click Request review.

Some points worth knowing before you click:

• Only request a review when the fix is live. If a site has been reviewed and rejected several times recently, the Start review process button becomes inactive, and Google shows a date when you can try again.
• "Not present" is for genuine mistakes. Use it when you believe the site was labeled incorrectly, not as a shortcut.
• Removing ad code is an alternative. If you choose not to show ads on a site, you can remove all ad code instead of requesting a review. Google says the issue stops showing in the Policy center within 7 to 10 days but remains in its system, and you can ask for a review later if you put ads back and fix the problem.

MCM child sites: who adds and verifies them

Under Multiple Customer Management (MCM), who does what depends on the delegation type.

Manage Inventory. The parent adds child sites in Ad Manager 360 under Inventory > Sites > Child sites, runs the ownership check, and requests the review. Your job as the child is to add the ads.txt line, tag or meta tag the parent sends you, keep the site crawlable, and fix any policy issues they pass on. If the parent disagrees with a disapproval, Google says they should request another review in their account. Google also asks parents to wait at least 2 hours after a child site becomes Ready before updating the GPT tags on the live site.

Manage Account. The inventory stays in your own Ad Manager account. If you signed up for Ad Exchange through the self-service flow, Google says you need to add your sites under Inventory > Sites before you can serve. Your parent can help, since they have access to your account, but the sites and their reviews are in your network.

In both cases, one rule from Google's MCM setup instructions matters most: do not enable Ad Exchange until approval is complete for all the sites you are monetizing. If you enable it before approval, ad serving stops on sites that are not approved in AdSense.

When to wait and when to act

A simple way to decide:

• Getting ready, inside Google's window: wait. Do not remove the site, change domains or resubmit.
• Getting ready, well past the window: check robots.txt, firewalls and the GPT tag, since crawl failures are not always shown. Then ask your MCM partner, if you have one, to check the status from their side.
• Needs attention: act. Open the Policy center, read the issue details, fix the pages, then request a review once the fix is live.
• Needs attention after several rejections: stop and reassess. Make sure you understand the issue before trying again, because repeated requests can lock the review button for a while.

Next step

A site in Ready status is the foundation for everything that follows in Ad Manager and Ad Exchange. If your sites are clean, crawlable and approved, eligible publishers may receive an MCM invitation, subject to Google's policies, and our team can explain what the partner will need from you.

Check the requirements or Get AdX access.