Site status
Needs attention
It is a status on one site, not a judgment on your account. Google checked the site, found something to fix, and parked it until you do. The useful part: Google sorts the cause into one of four buckets, and each bucket has a different fix.
By Mario Bailey · Published
Google's definition is one line: "You need to fix some issues before your site is ready to show ads." It shows on the Sites page in AdSense, against the one site it applies to, and Google's status table pairs it with a link to its article on sites that are not ready. Your other sites are unaffected unless they carry the status too.
The four site statuses
Every site on your Sites page has one of four approval statuses. In Google's words:
- Requires review: "Your site hasn't been checked yet." It also covers a site that went inactive and needs a fresh review.
- Getting ready: "We're running some checks on your site." Google says this usually takes a few days, sometimes two to four weeks. That one is a waiting status, covered on our Getting ready page.
- Needs attention: "You need to fix some issues before your site is ready to show ads."
- Ready: "Your site is ready to show ads."
The difference that matters: Getting ready means Google is working. Needs attention means Google is waiting on you.
Where to find the reason
Sign in, click Sites, and find the site in the list. Google's instructions then say to click the site "to get more details about its status." Read that detail before you change anything.
The Policy center is a separate screen for issues that affect ad serving. For each issue you click Fix in the Action column, which opens an Issue details page describing what Google found. If your site appears there too, that entry names the exact policy, which narrows the search fast.
The four reasons Google lists
Google's article for this status, What to do when your site is not ready to show ads, names four causes. Here they are in its wording, with what each usually comes down to.
"Your ad code is missing or incomplete." Google could not find what connects the site to your account. It asks whether the code is in your HTML, between the head tags, on the same site you signed up with. The code snippet is one of three ways to connect a site; the others are an ads.txt line and a meta tag, and Google also accepts ownership verified in Search Console. It is the easiest bucket to miss. Two sites in our own review queue were serving no AdSense markup at all, because the loader was gated on environment variables that would not all be set before approval (the field note). If you connected with ads.txt, read ads.txt Not found.
"Your site is unreachable." Google's checklist: the URL you entered is correct, the site is live, it needs no password, robots.txt does not block the AdSense crawler, and on HTTPS the certificate comes from a recognized authority (not self-signed) with HTTP redirecting to HTTPS. A mistyped URL is fixed by removing the site and adding it again with the right address.
"Your site doesn't have enough unique content or provide a good user experience." Google wants pages with "enough unique content so that we can determine what your site is about," no scraped or duplicated content, and navigation a visitor can actually use. Its content and user experience article is the rubric.
"Your site has policy violations." Something on the site breaks the AdSense Program policies or the Google Publisher Policies. The Policy center is where the specific policy gets named.
If you searched for needs attention plus low value content: Google's article for this status does not use that phrase, and the content bucket above is the closest match. Google's Publisher Policies glossary does define low-value content, more narrowly, as "Unintelligible content that has no value to the user," such as filler text. It feeds a policy whose exact name is Google-served ads on screens without publisher-content, and a named policy belongs in the fourth bucket.
Reason to page
| If the detail points at | Google's bucket | Read next |
|---|---|---|
| Missing code, unverified ownership, or the ads.txt line you connected with | Ad code missing or incomplete | ads.txt Not found, the field note |
| Wrong URL, downtime, a login wall, a blocked crawler, a certificate problem | Site unreachable | Site down or unavailable |
| Thin, unoriginal, or hard-to-navigate pages | Not enough unique content or user experience | Low value content |
| Copied or embedded content with nothing added | Content, or policy once it is named | Replicated content |
| Ads on screens with no content: under construction, error, thank-you, auto-generated | Policy violations | Without publisher-content |
| More ads or paid promotion than content | Policy violations | More ads than content |
| Any other named policy | Policy violations | Every violation, by name |
Fix it, then request the review
- Fix the bucket you were given, not the one you fear. A crawler that cannot reach your pages is not helped by rewritten articles, and a thin site is not helped by a new robots.txt.
- Check from the outside. Load the site logged out, on a phone network, and view the source of a live page to confirm the AdSense code is there. Our free site scan and readiness check cover the mechanical part.
- Request the review on the Sites page. Click Sites, click the site, confirm the AdSense code is placed, click Next, then Request review. Google says the review "usually takes a few days," sometimes two to four weeks, and that it will tell you when the site is ready.
- Leave it alone while it is checked. Google's note on the Getting ready status warns against removing a site and resubmitting it, because "this can delay the process." The one exception Google gives is a wrong URL, which you fix by removing the site and adding it again.
What Google says about resubmitting
The site-approval article asks you to submit "When you've addressed the above points," and publishes no limit on how often you can ask. The Policy center is stricter: its Start review process button goes inactive if a site "has been reviewed and rejected several times recently," and shows a date when you can ask again. A rejected Policy center review comes back by email, and Google's advice is to re-read the violation details before trying again. Both point the same way: one review per real change.
What Needs attention is not
It is not Getting ready, which only asks you to wait. It is not an account problem either. An account that was not approved gets reasons that apply to the whole account, such as a duplicate account, and a suspended account is another situation entirely: Google says site reviews are "paused until the suspension is lifted." If your notice is about the account, start at account disabled. And it is not an enforcement on a site that is already Ready; those show in the Policy center as Restricted or Disabled ad serving.
Three of the four buckets are really about the reader: a site that loads, says something of its own, and is easy to move around. Fixing it for them is the same work as fixing it for the review.
Run the readiness check Every violation, by name
Sources: Google, Check the status of your AdSense sites; What to do when your site is not ready to show ads; Fix policy issues that affect ad serving. Quotations are Google's. Current as of October 2026.