"Site Not Ready to Show Ads":
What It Means & How to Fix It
This status appears in your AdSense account when ad serving is blocked on a specific site. It can mean your site is under review, has a policy issue, or has a technical configuration problem. Here's how to diagnose and fix each case.
What “Site Not Ready to Show Ads” Actually Means
The “Site not ready to show ads” message in Google AdSense is one of the most confusing statuses publishers encounter. Unlike a full rejection such as “Low value content” or a clear policy violation, this status is a catch-all. It doesn’t always mean you were rejected, and it doesn’t always mean something is “wrong” with your site.
What it does mean is simple: Google is not currently serving ads on your domain. The reason can be a normal review queue, a missing technical requirement (like ads.txt), a site URL mismatch, or a policy/compliance problem that paused ad serving.
Think of AdSense as two layers: your account can be approved while a specific site is still being evaluated. That’s why you can log into AdSense, generate code, and still see “not ready” for a particular website.
During a site review, Google checks both content and technical readiness. If Googlebot can’t crawl enough pages, can’t verify the correct domain version, or sees missing trust pages, AdSense often keeps the site in a “not ready” state until those issues are resolved (or until the review completes).
The key idea: this status is not a diagnosis—it’s a label. Your job is to identify which underlying category applies: review in progress, policy issue, ownership mismatch, ads.txt/ad code problem, or crawl/access problem.
The good news is that most causes are fixable in a single iteration—if you identify the correct root cause. The bad news is that many publishers waste weeks fixing the wrong thing because the message is vague. The sections below make the diagnosis and fixes extremely specific.
The real reasons AdSense shows “not ready”
“Site not ready” is a catch-all status that can be triggered by very different issues. The fastest way to resolve it is to work through the causes in a smart order—starting with the most common and easiest to verify.
1) The site is still under initial review
This is the most common cause. You added the site recently (or requested a re-review), and Google’s review is still ongoing. During this period, AdSense may show “Getting ready” or “Not ready to show ads.” If you see no specific violation in Policy Center, it’s often just a waiting game while Google crawls and evaluates the site.
2) ads.txt is missing or incorrect
Google expects you to publish an ads.txt file when you use AdSense. If your ads.txt is missing, returns a 404, is blocked, or contains the wrong publisher ID, Google can limit or pause ad serving. Sometimes AdSense shows a separate ads.txt warning, but in many cases the site stays “not ready” until it’s fixed.
3) Your site URL in AdSense doesn’t match the live canonical domain
AdSense treats domain variants differently: http vs https, www vs non-www, and sometimes even subdomains. If you added http://example.com but your site redirects to https://www.example.com, Google may fail ownership verification or detect inconsistency during review. This mismatch is a classic reason publishers remain stuck in “not ready.”
4) Ad code is not detectable on live pages
If Google can’t find your AdSense code on accessible pages, it may assume the site isn’t configured properly. This can happen when the script is missing, injected only for logged-in users, blocked by a consent tool misconfiguration, or included only on some pages instead of your global layout.
5) Missing compliance / trust pages
Some publishers have content but lack essential “trust” pages: Privacy Policy (especially important), About, Contact, and Terms. If these pages are missing, hidden, or blocked, Google may consider the site incomplete or noncompliant. This can contribute to “not ready,” especially for new sites in review.
6) Policy Center issues or restricted content
If your site triggered a policy issue—adult content, copyrighted material, misleading navigation, scraped text, dangerous content, or other restricted inventory—ad serving can be paused. Sometimes the Policy Center will show an explicit violation; other times you may only see “not ready” on the Sites tab.
7) Crawl/access problems (robots, 403s, geo blocks, interstitials)
Google must be able to crawl your pages. If you block bots with robots.txt, return 403/401 for some user agents, redirect aggressively, show a full-screen interstitial, or require cookies/JS for basic rendering, AdSense might not “see” the site properly and can keep it not ready.
In practice, “not ready” is rarely a single issue—many sites have a combination: an ads.txt problem plus a domain mismatch, or a missing privacy policy plus a review queue. That’s why the fix section below follows a specific order.
Real scenarios that trigger “Site not ready”
Google loves examples because they clarify what “not ready” looks like in real life. Below are the most common scenarios we see across new sites, blogs, tool sites, and programmatic SEO sites.
Example 1: New site under review (nothing is wrong)
You added your site two days ago. In AdSense → Sites, it shows “Getting ready” and your pages show blank ad slots. You check Policy Center and see no violations. This is normal: Google hasn’t completed the review yet. The site is simply waiting in queue while Google crawls.
Example 2: ads.txt returns 404 (or redirects to a 200 HTML page)
You created an ads.txt file but deployed it to the wrong path (e.g., /static/ads.txt). Visiting /ads.txt returns 404, or your framework returns a branded 200 HTML page instead of plain text. AdSense detects this and keeps the site not ready until the file is accessible at the root.
Example 3: Wrong domain version added in AdSense
You added example.com in AdSense, but your site forces www.example.com. In the browser it works, but in AdSense the verification is inconsistent. Google sees a mismatch and cannot confidently verify the site. Status remains “not ready.”
Example 4: Ad code only appears on some pages
You placed the AdSense script in a single template used only by blog posts, but your homepage and category pages (the ones Google crawls most) don’t include the code. Google can’t reliably detect the implementation and your site remains not ready.
Example 5: Consent banner blocks the AdSense script
You installed a cookie consent tool that blocks third-party scripts by default. Because the AdSense script is classified as advertising, it never loads unless the user clicks “Accept.” Google’s crawler may not accept the banner, so it never sees the ad code → “not ready.”
Example 6: Policy Center issue pauses serving
Your site was serving ads last month, then you added a section with copyrighted movies, adult content, or scraped content. A policy signal is triggered and ad serving is paused. The site now shows “not ready,” and Policy Center may show affected URLs—or it may only show a general serving limitation.
Example 7: Robots.txt blocks important pages
Your robots.txt disallows / or disallows your blog section, or blocks specific user agents. Search might still index some pages, but AdSense crawler can’t verify enough content, so review fails or stays stuck.
Notice the pattern: the site looks “fine” to you in a browser, but Google needs consistent crawlability, correct verification, visible trust pages, and detectable ad setup. If any of these are missing, “not ready” persists.
Step-by-step fixes (in the fastest order)
The worst mistake is randomly changing things and hoping the status disappears. Instead, follow this order. Each step either resolves the issue or narrows it down fast.
Step 1: Check the “Sites” tab status (Review vs Attention)
Open AdSense → Sites and click your domain. If it shows “Getting ready” or “Needs review,” you may simply be waiting for the initial review. If it shows “Requires attention,” look for any hints (ads.txt, policy, or verification prompts). This step tells you whether you should fix something now or avoid breaking things while waiting.
Step 2: Verify /ads.txt works correctly (not just “exists”)
Visit https://yourdomain.com/ads.txt in a private/incognito window.
It must return a plain text file (not HTML), with a valid AdSense line like:
google.com, pub-XXXXXXXXXXXXXXX, DIRECT, f08c47fec0942fa0.
Fix typos, ensure the publisher ID matches your account, and confirm it’s accessible over HTTPS.
If your site redirects non-www to www (or vice versa), confirm the final redirected URL still returns the correct ads.txt. Ads.txt issues are one of the fastest “wins” because Google updates this signal quickly.
Step 3: Fix domain mismatches (www vs non-www, http vs https)
Identify your canonical domain version (the one your site forces via redirects).
Example: if http://example.com redirects to https://www.example.com, then your canonical is
https://www.example.com.
Your AdSense site entry should match this as closely as possible.
Also check that your canonical tags, sitemap URLs, and internal links consistently use the same version. Mixed versions can confuse verification and review systems.
Step 4: Confirm ad code is on the live page and visible to crawlers
View source on your homepage and a top content page. You should see the AdSense script (adsbygoogle.js) in the HTML. If you load scripts conditionally (env flags, logged-in state, geo rules), make sure Google can see it on public pages.
If you’re using a cookie banner, verify it does not completely block the AdSense script for crawlers. A safer approach is to allow the script to load but manage personalization via consent mode.
Step 5: Ensure privacy policy and trust pages are present and linked
Your Privacy Policy should be reachable in 1 click from every page (footer link). It should mention third-party advertising, cookies, and Google’s role. Also add About and Contact pages. These improve trust and reduce friction during review.
If your policy page exists but is blocked by a redirect loop, 404, or noindex, fix that. Google must access it.
Step 6: Check Policy Center (and resolve anything active)
Go to AdSense → Policy Center. If you see violations or restricted ad serving, click in and read the affected URLs and issue category. Fix those pages first (remove restricted content, add moderation controls, rewrite thin sections, remove scraped text). Then submit a review in Policy Center.
Step 7: Wait for recrawl and re-check after 7–14 days
Even after fixes, Google needs time to recrawl. If you solved ads.txt and domain mismatch issues, you may see updates sooner. For policy and site review issues, it can take longer. Use this time to improve content quality and ensure the site looks complete.
If you do the steps above in order, you avoid the common trap: spending weeks rewriting content when the real problem was a missing ads.txt or a domain mismatch.
Site Readiness Checklist
Use this checklist before requesting review. If any item fails, “not ready” can persist.
- AdSense → Sites shows the correct domain (www/non-www) that matches your live redirects
/ads.txtloads as plain text and contains your correctpub-ID- Homepage and at least 3 key pages are crawlable without login, paywall, or blocked scripts
- AdSense script is present on live pages (not only behind consent or user state)
- Privacy Policy is accessible and linked from the footer on every page
- About + Contact pages exist and are accessible
- Robots.txt does not block important sections or user agents
- No major redirect loops or 403/401 responses for crawlers
- Avoid serving different HTML to bots vs users (cloaking signals)
- Avoid copyrighted/illegal/adult content that can pause serving
- Avoid thin doorway pages or scraped programmatic pages without value
Don’t guess—scan your site and find the exact blocker
The “site not ready” message is vague by design. Manually diagnosing it can take hours—especially if you’re dealing with redirects, ads.txt, missing trust pages, or hidden policy signals.
Instead of manually checking your site, run a free AdSense Audit. Our scanner checks the most common “not ready” causes automatically: ads.txt availability and correctness, privacy/trust pages, crawlability, domain mismatch signals, and content/policy risk flags.
You’ll get a clear report of what’s wrong, where it’s happening, and what to fix—so you can move from “not ready” to live ads faster.
Frequently Asked Questions
These are the most common questions publishers ask when ads aren’t showing even after “approval.”
Does “site not ready to show ads” mean my AdSense account was rejected?
Not necessarily. Your AdSense account can be approved while your site is still under review or blocked by a site-level issue. This status usually means ads are not being served on the domain yet, not that your entire account was rejected.
How long should I wait before assuming something is wrong?
If you just added the site, waiting 2–4 weeks can be normal. However, you should still verify the quick checks:
/ads.txt works, your domain version matches, and your privacy policy is accessible.
If those are correct and the status doesn’t change after a few weeks, investigate Policy Center and crawlability.
My ads.txt exists. Why am I still “not ready”?
“Exists” isn’t enough. The file must be accessible at the root (/ads.txt), load as plain text, contain the correct pub ID,
and not be blocked by redirects or caching that returns HTML. A common issue is hosting it at the wrong path or returning a soft 404.
Can a cookie banner block AdSense review?
Yes. Some cookie tools block ad scripts entirely until a user clicks “Accept.” Crawlers often don’t click banners, so AdSense cannot detect ad code or necessary signals. Consider configuring consent mode correctly so the script can load while respecting consent requirements.
What pages should I prioritize to get past “not ready” faster?
Prioritize your homepage, top traffic pages, and your trust pages (Privacy Policy, About, Contact). Make sure these pages are crawlable, load fast, and clearly demonstrate the purpose of the site. If your site is mostly tools, add helpful content that explains usage, examples, and FAQs.
My site used to show ads, then became “not ready.” What changed?
This usually indicates a site-level pause due to policy signals, invalid traffic risk, content changes, or a technical change (redirects, robots.txt, theme changes removing code, broken ads.txt). Check Policy Center first, then verify ads.txt and ad code detection.
After fixing issues, how do I trigger a re-check?
If you have a Policy Center item, fix it and click Request Review. If it’s an initial site review, you typically can’t “force” it—Google will recrawl on its schedule. Ensure your sitemap is correct, submit URLs in Search Console, and keep fixes stable so the next crawl sees the improvements.
What’s the fastest way to find the real cause?
Start with the high-signal checks: Sites tab status, Policy Center, /ads.txt accessibility, and domain mismatch (www/non-www).
If those look good, move to ad code detection and crawl/access issues. Or run an automated scan to catch them all at once.
Six reasons your site shows "not ready"
The message is a catch-all that can indicate very different underlying issues. Identify which one applies before spending time on the wrong fix.
Still Under Initial Review
You recently added your site to AdSense and the review is ongoing. This is the most common cause and requires no action—just patience of 2–4 weeks.
Missing Privacy Policy
AdSense requires a GDPR/CCPA-compliant Privacy Policy linked from every page. Missing or inaccessible policy pages immediately block ad serving.
Incorrect ads.txt File
Your ads.txt may be missing, malformed, or contain the wrong publisher ID. Google surfaces this as a site readiness issue, not a separate warning.
Active Policy Violation
Content, traffic, or inventory on your site triggered a policy flag. Check your AdSense Policy Center for any active violations or manual actions.
Site URL Mismatch
The site URL in AdSense doesn't exactly match your live domain—e.g., www vs non-www, or HTTP vs HTTPS. This breaks domain ownership verification.
Ad Code Not Detected
If Google can't find your AdSense code on live pages, it may show this status. Verify auto-ads are enabled and the snippet is in your page's <head>.
How to resolve each cause, in order
Check your AdSense account status
Go to AdSense → Sites. If the site shows "Getting ready," the initial review is underway. If it shows "Requires attention," there's a specific issue to resolve. Note which status applies before proceeding.
Verify your ads.txt file
Visit yourdomain.com/ads.txt directly. It should contain your AdSense publisher line: google.com, pub-XXXXXXXXXXXXXXXX, DIRECT, f08c47fec0942fa0. Fix typos, wrong IDs, or add the file if missing.
Audit your Privacy Policy
Ensure your Privacy Policy mentions third-party advertising (specifically Google/DoubleClick cookies), is accessible from every page via a visible footer link, and is not behind a login or redirect.
Check the AdSense Policy Center
Navigate to AdSense → Policy Center. Any active violations will be listed here with the affected URLs. Resolve each violation, then use the "Request Review" option.
Confirm your domain is correctly added
The domain in AdSense → Sites must exactly match your canonical URL. If your site redirects www to non-www, use the final destination URL and verify the redirect chain is clean.
Frequently Asked Questions
What does 'site not ready to show ads' mean in AdSense?
This message appears when your AdSense account is approved but your site hasn't yet passed Google's site review, or when ad serving has been paused due to a policy or technical issue. It's different from an account-level rejection—your account exists, but ads are blocked on the specific site.
How long does the AdSense site review take?
The initial site review after adding your site to AdSense typically takes 2–4 weeks. If your site was previously disapproved and you've made changes, a re-review can also take up to 4 weeks. During this period, 'site not ready to show ads' is normal and expected.
My AdSense account is approved but the site shows 'not ready.' Why?
An approved AdSense account doesn't automatically mean all sites are cleared. Each site you add must pass its own policy review. Additionally, if your site was active and then flagged for a policy violation, ad serving may be paused even on a previously approved site.
Can I speed up the AdSense site review?
You cannot directly accelerate the review queue. However, you can improve your chances of passing by ensuring your ads.txt file is correct, your Privacy Policy is accessible, your content meets quality standards, and there are no active policy violations. Fixing these before submitting saves a review cycle.
Do I need to reapply if my site shows 'not ready'?
If the status is due to an ongoing initial review, no action is needed. If it's due to a specific violation or issue, fix the problem and then click "Request Review" in the Policy Center—you typically don't need to start a new application from scratch.
Find exactly why your site isn't ready
AdSense Audit checks your ads.txt, Privacy Policy, policy violations, content quality, and technical setup—and tells you precisely what to fix.
Run a Free AuditRelated AdSense Guides
More resources to get your site approved