Your AdSense account passed 2 years ago. Site #1 is earning. You added Site #2 last month. AdSense → Sites → Site #2 says “Getting ready” and won’t budge. You think “but my account is approved” — that’s the misunderstanding. Account approval is not per-site approval. Since 2018, Google reviews each domain independently for serving ads, even on accounts in good standing. Your existing earnings are untouched; the new domain just goes through the full review queue.
Fastest answer: If the site shows “Getting ready” (not “Requires review” or “Needs attention”), and your ads.txt status is “Authorized” and the AdSense snippet is on every page, you are most likely just waiting. Per Google’s own docs (as of June 2026), per-site review “usually takes a few days, but in some cases can take 2-4 weeks.” Do not remove and re-add the site. Confirm the four checks below, then wait. If 8+ weeks pass with everything correct, escalate via the policy contact form.
This article maps the exact 2026 status labels, what each one means, what AdSense actually checks on a new site, and how to legitimately shorten the wait.
First: read the exact status, it tells you what to do
In AdSense → Sites, each domain shows two separate statuses: a site review status and an ads.txt status. People conflate them. Find your domain in the list (use the filter at the top), then match the labels below.
| Site status | What Google means | Your move |
|---|---|---|
| Requires review | ”Your site hasn’t been checked yet.” Review has not started. | Click Request review. Nothing happens until you do. |
| Getting ready | ”We’re running some checks on your site.” Review is in progress. | Wait. This is the expected state. Don’t remove/re-add. |
| Needs attention | A specific issue (policy, ads.txt, or verification) blocks ads. | Read the inline hint and fix the named problem. |
| Ready | ”Your site is ready to show ads.” | Done. Ads serve once ads.txt is Authorized and code is live. |
| ads.txt status | Meaning | Fix |
|---|---|---|
| Not found | No /ads.txt file detected at the root. | Publish ads.txt at the domain root (see Step 2). |
| Unauthorized | File exists but your publisher ID line is missing/wrong. | Add the exact AdSense line; check for typos. |
| Authorized | Your publisher ID is present and valid. | Nothing to do. |
| Not applicable | A host platform manages it for you. | Nothing to do. |
Two things people miss in 2026: (1) “Getting ready” appearing after “Requires review” is a positive signal — it means the initial checks passed and you cleared the first gate. (2) The site can read “Getting ready” while ads.txt still reads “Unauthorized”; ads will not serve until ads.txt flips to “Authorized” even after the site itself is approved.
Common causes
Ordered by hit rate, highest first.
1. Site is too new
A domain registered or first crawled by Google less than 1-3 months ago is harder to evaluate. Even with great content, AdSense often holds new domains in queue.
How to spot it: whois yourdomain.com | grep "Creation Date". If under 30 days, expect a long wait. Under 7 days, very long.
2. Site has under ~25 substantial articles
AdSense doesn’t publish a minimum, but in practice indie publishers report ~25-40 substantial articles is the threshold for passing per-site review.
How to spot it: Count your published articles. Substantial = 800+ words, original, not auto-generated.
3. Site is not fully crawlable
robots.txt blocks, noindex meta tags, basic-auth login wall, password-protected sections, or CDN bot challenges all prevent AdSense’s review crawler from seeing your content.
How to spot it:
curl -sA "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)" https://yourdomain.com | head -50Should return real article HTML, not a login or challenge page.
4. New site has no organic traffic yet
AdSense partly uses search traffic as a “Google has indexed and ranks this site” signal. Zero impressions in Search Console = AdSense can’t verify the site has real users.
How to spot it: Search Console → Performance → last 28 days. If 0 impressions, this is a factor.
5. New site duplicates content from your other approved site
If you copy-pasted content from Site #1 to Site #2 (a common mistake when building a portfolio), AdSense’s duplicate detection flags it. Even paraphrased content gets caught.
How to spot it: Pick 3 random paragraphs from new site, paste into Google with quotes. If your other approved site comes up, you have duplicates.
6. Ownership not verified or AdSense code not installed
You added the site in AdSense but never completed verification (TXT record, HTML file, or meta tag), or the AdSense snippet isn’t on every page.
How to spot it: AdSense → Sites → click your site. If verification badge is missing, that’s it. Also curl -s https://yoursite.com | grep ca-pub- should return your publisher ID.
7. Site has a noindex meta tag (often accidental)
Many starter templates default to <meta name="robots" content="noindex"> and you never flipped it. AdSense respects it: noindex pages cannot host ads.
How to spot it:
curl -s https://yoursite.com | grep -i 'meta name="robots"'Should not contain noindex.
8. ads.txt is missing or “Unauthorized”
A separate, very common 2026 blocker. The site review can pass while ads.txt is still wrong, and ads never serve. The status column in AdSense → Sites shows this independently.
How to spot it:
curl -s https://yoursite.com/ads.txtIt must return plain text (not an HTML page or a 404) containing your exact AdSense line. See Step 2 for the format.
9. Thin author signals (E-E-A-T)
A factor AdSense reviewers weigh more heavily since 2025: pages should show a real human behind the content. Listing an email address (or no name) as the author, with no about/contact page and no editorial accountability, reads as low-trust and can stall a borderline site.
How to spot it: Check whether each article has a named human author, and whether the site has a populated About and Contact page with a real name or organization.
Shortest path to fix
Step 1: Verify ownership completes
In AdSense → Sites → click your site → “Verify ownership.” Use:
- HTML file method: download the file, place at site root, redeploy.
- Meta tag: add to root layout
<head>. - TXT record (preferred for static sites): add to your DNS.
After deploying, click “Verify.” Should show ✓.
Step 2: Confirm AdSense code and ads.txt are correct
First, the snippet must be on every page:
for path in / /about /privacy $(curl -s yoursite.com/sitemap.xml | grep -oE 'https://[^<]+' | head -10); do
echo -n "$path: "
curl -s "$path" | grep -c "ca-pub-"
doneEach should print 1 or more. If 0, the snippet isn’t there.
Then publish ads.txt at the domain root with the exact AdSense line (replace the zeros with your real publisher ID):
google.com, pub-0000000000000000, DIRECT, f08c47fec0942fa0The constant f08c47fec0942fa0 is Google’s certification authority ID and is the same for every AdSense publisher. Confirm it serves as plain text:
curl -sI https://yoursite.com/ads.txt | grep -i content-typeYou want text/plain, not text/html. Then in AdSense → Sites, the ads.txt status should change to Authorized within a day or two (Google re-crawls ads.txt on its own schedule).
Step 3: Remove crawl blocks
Check:
curl -s https://yoursite.com/robots.txt
curl -s https://yoursite.com | grep -i 'noindex\|nofollow'robots.txt should NOT have Disallow: / for * or Mediapartners-Google. Pages should NOT have noindex.
Step 4: Confirm Search Console has indexed pages
GSC → Indexing → Pages. Should show 20+ “Valid” pages. If 0, request indexing for the top 10 URLs and wait.
Step 5: Differentiate from your other approved sites
If you suspect duplicate content with another property, rewrite at least 80% of the overlapping articles. Add unique angles, original data, or first-person experience.
Step 6: Don’t churn the Request review button
If the status is “Requires review,” click Request review once. If it’s already “Getting ready,” there is nothing to re-trigger. Removing and re-adding the site:
- Resets your queue position.
- Does not speed up review.
- Looks like manipulation to AdSense.
Note: after a site has been reviewed and rejected a few times recently, the Request review / Start review process button goes inactive and shows a date when you can try again. Spamming it does nothing. Per-site reviews on established accounts resolve in a few days to 2-4 weeks once the eligibility criteria above are met (Google’s own range), though stubborn cases run longer.
Step 7: How to confirm it’s fixed
You are done when all three of these are true in AdSense → Sites:
- Site status reads Ready (not “Getting ready” or “Needs attention”).
- ads.txt status reads Authorized.
- A live page actually serves an ad unit, or in
AdSense → Ads → By sitethe site shows impressions.
If the site says “Ready” but ads are blank, that’s a different problem — see AdSense script installed but ads are blank and AdSense ads not showing.
Step 8: After 8 weeks, contact support
If the setup is verified-correct, you have 25+ substantial articles, the site is indexed in GSC, and 8 weeks have passed in “Getting ready”: use the policy contact form with your publisher ID, site URL, and the date you added it. Reference the official site status guide so support sees you’ve already checked the labels.
When this is not on you
AdSense per-site review timing is opaque and has no SLA. Some sites approve in days, some sit for weeks for no visible reason. The criteria are not deterministic, so a correct, well-stocked site can still wait out the full window. That is normal; it does not mean you’ve done something wrong.
Easy to misdiagnose as
Reapplying repeatedly does not help. The account was approved separately; the per-site review uses different signals (domain age, crawlability, content depth, ads.txt, author trust) that don’t shortcut just because your account is in good standing. Likewise, “Getting ready” is not a rejection — only “Needs attention” or a disapproval email is.
Prevention
- Build any new site to 25+ substantial articles before adding to AdSense.
- Wait until the domain is 1-3 months old before submitting.
- Get at least some organic traffic from Search Console first.
- Don’t duplicate content across your AdSense-monetized sites.
- Verify ownership, publish ads.txt, and place the code immediately after adding — don’t wait.
- Use a real author name and a populated About/Contact page from day one.
FAQ
- Does my approved account auto-approve new sites? No. Each domain is reviewed independently, even on an account that’s been in good standing for years.
- Is “Getting ready” a rejection? No. It means the review is in progress. It’s a neutral-to-positive state, especially if it followed “Requires review.” Only “Needs attention” or a disapproval email signals a problem.
- How long does “Getting ready” take in 2026? Per Google’s site-status docs, usually a few days, in some cases 2-4 weeks. Stubborn cases run longer, with no SLA.
- Can I show ads while the site is pending? No. The ad slot returns
unfilled(no fill) until the site status reads Ready and ads.txt reads Authorized. - My site says “Ready” but ads.txt says “Unauthorized” — why no ads? The two are independent. Ads won’t serve until ads.txt is Authorized. Fix the
ads.txtline (Step 2) and wait for Google to re-crawl it. - Will deleting and re-adding the site restart it faster? No. It resets your queue position and can look like manipulation. Leave it alone and wait.
Related
- AdSense site needs review
- AdSense low value content rejection
- Duplicate site / domain confusion during review
- Many pages but still too thin for review
Tags: #AdSense #Monetization #Troubleshooting #Pending review