AdSense "Site Down or Unavailable": Causes and How to Fix It
By Ramón Martínez · Updated 28 Oct 2026 · 7 min read
You open AdSense and it says your site is "down or unavailable", yet it loads fine in your browser. Or AdSense tells you it "couldn't verify" your site even though you pasted the code. Here's the reassuring part: this rejection is almost never about content quality. It's an access problem, and you can usually fix it in an afternoon.
Keep one thing in mind throughout: you seeing your site doesn't mean Google's crawler can. Google visits from its own servers, with its own user agent, without your cookies or logged-in session. If anything blocks or breaks that visit, as far as AdSense is concerned your site doesn't exist.
Two messages, two different problems
| Message | What it usually means |
|---|---|
| "Site down or unavailable" | Google tried to load the site and failed: server error, DNS, a block, a timeout or a broken redirect. |
| "We couldn't verify your site" | The site loads, but Google can't find your AdSense code or verification (or finds it on a different domain from the one you added). |
Work out which one you have, because the troubleshooting differs. The exact wording in the dashboard can change over time, so focus on the meaning rather than the phrasing.
The most common causes
- Wrong domain or wrong version. You added
example.combut the site lives onwww.example.com(or vice versa) and the redirect is broken. Typos and subdomains cause this too. - Recent DNS changes. If you just moved hosts or pointed the domain, propagation takes time. Google may have visited while the domain still pointed nowhere.
- Overly strict firewall or bot protection. Security plugins, WAF rules, JavaScript challenges or "under attack" modes can stop legitimate Google crawlers. This is one of the most frequent and least obvious causes.
- Country or IP blocking. If you only allow visitors from certain countries, Google may crawl from somewhere you've blocked.
- Maintenance mode, "coming soon" or password protection. Many site builders show a holding page to logged-out visitors. You see the real site; Google sees the placeholder.
- robots.txt blocking the AdSense crawler. A leftover
Disallow: /from development, or rules that blockMediapartners-Google. - Intermittent server errors. Overloaded hosting, 5xx errors, very slow responses or an expired SSL certificate.
- Ad code in the wrong place. For verification: the snippet isn't in the
<head>, a cache or optimization plugin strips it, or it only appears on some pages.
Troubleshooting, step by step
Go in this order — quickest checks first.
- Check the exact URL in AdSense. Under Sites, see which domain you added. Open it in a private window exactly as written, with and without
www, onhttpandhttps. Every variant should land on the same page with a single redirect. - Test from outside your network. Use your phone on mobile data (no Wi-Fi) in a private tab. If it fails or shows a maintenance page there, you've found the culprit.
- Run Google Search Console's URL Inspection. The live test shows how Googlebot sees the page. An error, a block or a different page confirms the problem from Google's side.
- Open
yourdomain.com/robots.txt. There should be no blanketDisallow: /. To be explicit, you can add a block that allows the ads crawler:User-agent: Mediapartners-Google Disallow: - Review your security layer. Check your security plugin, firewall or CDN logs for blocked requests from Google crawlers. Relax aggressive challenges or add an exception for verified bots if your provider supports it.
- Check server health. Ask your host for recent downtime and make sure your SSL certificate is valid.
- For "couldn't verify": view the homepage source (Ctrl+U / Cmd+Option+U) and search for
adsbygoogleor yourca-pub-ID. If it's missing, clear caches, check the plugin that injects it, or paste it directly into your theme's<head>.
Checklist before you resubmit
- The URL in AdSense matches the one your site actually serves.
- The site opens in a private window, on another network and on mobile — no password, no holding page.
- Search Console URL Inspection shows the real page with no errors.
robots.txtdoesn't block Googlebot or Mediapartners-Google.- Your firewall or CDN isn't blocking verified Google crawlers.
- No geo-blocking that could shut Google out.
- HTTPS is valid and there are no long redirect chains.
- The ad code or verification meta tag appears in the homepage source.
- If you use ads.txt, it loads from the root domain and includes your publisher ID.
See your site the way a reviewer would
MonetizeReady checks things like your AdSense code, ads.txt, robots.txt and legal pages right on the page and flags them with a traffic light. Free for Chrome.
Add to Chrome — freeRequesting a new review
Once the cause is fixed, go back to Sites in AdSense, confirm you've resolved the issues and request a review. A few practical tips:
- Don't resubmit within minutes. Give the site a few stable days, especially after DNS or hosting changes.
- Freeze your setup during review. Re-enabling maintenance mode or swapping security plugins mid-review can trigger another rejection.
- Check everything else while you wait. Once Google can get in, it will evaluate content and policies. Run through the AdSense approval checklist so you don't stack a second rejection on top of the first.
FAQ
My site works fine — why does Google say it's down?
Because Google doesn't visit it the way you do. It comes from its own servers, without your session, sometimes from another country. Bot protection, geo-blocking or a maintenance page for anonymous visitors is enough to hide everything.
How long does a new review take?
Google doesn't publish a fixed timeline. It can take days or a few weeks. In the meantime keep the site reachable and avoid major technical changes.
Can Cloudflare or another CDN cause this?
Yes, if it's configured very restrictively. CDNs typically let verified crawlers through, but custom rules, challenges on all traffic or country blocks can still catch them. Check your firewall events.
Does this rejection mean my content is bad?
Not necessarily. It means Google couldn't reach or verify the site, so it probably hasn't judged your content yet. Once access is fixed, quality will matter — read up on "low value content" to get ahead of it.
Should I delete the site and add it again?
Usually not. Only if you added a misspelled domain or the wrong version does it make sense to add the correct one. Otherwise, fix the issue and request a review of the same site.
MonetizeReady is an independent tool, not affiliated with Google. AdSense is a trademark of Google LLC.