Skip to content
Approvalens

Guides8 min read

"Site Down or Unavailable" in AdSense: Causes and Fixes

Why AdSense says your site is down or unavailable when it loads fine for you, how to test it the way Google's crawler sees it, and how to fix each cause.

Fixes these report findings

  • Site is reachable
  • HTTPS certificate
  • HTTP to HTTPS redirect
  • Google crawlers can open the site
  • Bot check on the homepage
  • AdSense crawler allowed in robots.txt
  • robots.txt is reachable
  • Content behind a login
  • +2

"Site down or unavailable" means the AdSense crawler tried to load your site during the review and didn't get a usable page back. Your site may work perfectly in your browser. What counts is what Google's crawler received, from its own network, with its own user agent, at the moment it checked. The cause is nearly always technical (DNS, the certificate, a redirect, a firewall, robots.txt, a login or maintenance page, or plain downtime), which makes this one of the easier rejections to fix.

What the message means

There's no help article with this exact title. Google covers the same ground under "Your site is unreachable" in What to do when your site is not ready to show ads, as a list of questions:

  • "Did you provide the correct URL?"
  • "Is your site up and running? Make sure your site is published and live on the web."
  • "Can AdSense access your site without a password?"
  • "Can the AdSense crawler access your site? Make sure you're not blocking our crawler in your robots.txt file."
  • "Does your site have a valid SSL Certificate from a recognized certification authority (not a self-signed certificate) and does it also redirect HTTP to HTTPS?"

The add a site article names the crawlers involved: changes must be "published and accessible by the AdSense ads crawler (Mediapartners-Google and Google-Display-Ads-Bot)".

So the rejection is not a judgement about your content. The reviewer may never have seen it. Every one of those questions is a gate the crawler has to pass, in roughly this order:

Diagram of six gates the AdSense crawler passes: DNS resolves, TLS certificate is valid, redirects end in one place, firewall lets Google through, robots.txt allows it, server answers 200 with real content; each gate has its typical failure such as NXDOMAIN, certificate error, redirect loop, 403 or challenge page, Disallow slash, and timeout or placeholder
Six gates between the crawler and your content. One closed gate at review time is enough for this rejection.

Match the symptom to the cause

Before you test anything, think about what changed around the time you applied. Then use this table to narrow it down.

What you notice Most likely gate Where to look
You use Cloudflare or another CDN with bot protection 4, firewall Security events for blocked Google user agents
www version gives an error, bare domain works (or the reverse) 1, DNS DNS records for both names
Browser shows a padlock warning on one version 2, certificate Certificate host names and expiry date
http:// opens a different or old site 3, redirects Server or host redirect settings
Your host or a plugin blocks "foreign" traffic 4, firewall Country rules, geo-blocking options
You copied a robots.txt from a tutorial 5, robots.txt The Mediapartners-Google group
A "coming soon" or maintenance plugin is installed 6, content The page a logged-out visitor sees
Shared hosting that's slow or sometimes down 6, server Uptime history around the review date
You typed the URL into AdSense by hand before gate 1 The URL on your AdSense Sites page

Geo-blocking deserves a note. Google's documentation says "the default IP addresses of the Googlebot crawler appear to be based in the USA" (locale-adaptive pages). If your host or a security plugin blocks US traffic to cut spam, you're very likely blocking Google too.

Test the site the way the crawler sees it

Your browser is the worst test: it carries cookies, a challenge it solved last week and your local network. Use one of these instead, from quickest to most thorough.

1. Quick check in a browser tab

Run your home page through the free Googlebot access checker. It requests the page as a browser, a phone, Googlebot, the AdSense crawler (Mediapartners-Google) and AdsBot, and compares the status codes and word counts.

Approvalens Googlebot access checker result for delayatlas.com: browser, phone, Googlebot, AdSense Mediapartners-Google and AdsBot-Google all received status 200 and 1156 words, with the message Google bots see the same page as visitors
A healthy result: every user agent gets a 200 and the same 1,156 words. A 403, a 503 or a much lower word count for the Google rows is the red flag.

A pass is encouraging, but it comes from our servers, not Google's IP addresses, so a firewall that trusts or distrusts specific IP ranges can still behave differently for the real crawler.

2. Check from Google's own network

If the site is verified in Search Console, use URL Inspection on your home page and click Test live URL. Google says the live test "fetches and examines the URL in real time", and View tested page shows the HTTP response and a screenshot (URL Inspection tool). This is Googlebot, not the AdSense crawler, but it does come from Google's network, which is exactly what a firewall or geo-block cares about. If the screenshot shows a challenge page or an error, you've found your problem.

3. Raw responses in a terminal

For each gate, one command:

# Gate 1: both names resolve
dig +short example.com
dig +short www.example.com

# Gate 2: certificate host names and expiry
curl -vI https://example.com/ 2>&1 | grep -E "subject|issuer|expire"

# Gate 3: http goes to https in one hop
curl -sI http://example.com/ | head -n 3

# Gate 4 and 6: what the AdSense crawler's user agent gets
curl -sI -A "Mediapartners-Google" https://example.com/
curl -s -A "Mediapartners-Google" https://example.com/ | head -c 600

# Gate 5: the robots file
curl -s https://example.com/robots.txt

What you want to see: an address for both names, a certificate that lists both names and hasn't expired, a single 301 or 308 to https://, a 200 with your real HTML, and no Disallow: / in a group naming Mediapartners-Google. HTML that contains Just a moment... or /cdn-cgi/challenge-platform means a bot challenge is sitting in front of your site.

Fixes by cause

Firewall, CDN and security plugins

On Cloudflare, check Security Events for blocked or challenged requests from Google user agents, and review Bot Fight Mode, "I'm Under Attack" mode, country rules and custom WAF rules. The Cloudflare guide walks through each setting. On WordPress, security plugins (Wordfence, Solid Security, All In One WP Security) and server firewalls (Imunify360, ModSecurity) can rate-limit or block crawlers; look in their logs for blocked requests whose user agent contains Google. Allowlist verified Google crawlers rather than switching protection off.

robots.txt

Remove any Disallow: / under a Mediapartners-Google group. Google's crawler documentation says that for Mediapartners-Google "The global user agent ( * ) is ignored" (Google special-case crawlers), so only a group that names it can block it. A User-agent: * block doesn't stop the AdSense crawler, but it does stop Googlebot, which causes other problems. A safe minimum:

User-agent: Mediapartners-Google
Disallow:

User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php

Sitemap: https://example.com/sitemap.xml

Test any change with the free robots.txt tester, and see the robots.txt guide for how groups are read.

Domain, www and redirects

Pick one main address (for example https://example.com) and 301-redirect every other variant to it: http://example.com, http://www.example.com and https://www.example.com. Make sure both DNS names exist, otherwise one variant fails outright. If you submitted the wrong URL, Google's instruction is to "remove the site from your sites list and add a new site with the correct URL".

Certificate

Use a certificate from a recognised authority (Let's Encrypt is fine) that covers both example.com and www.example.com. Turn on automatic renewal and check the expiry date before you resubmit.

Hosting, uptime and geo-blocking

Set up a free uptime monitor that checks every few minutes from several regions, including the US. Repeated short outages mean the review may have landed on one. Remove country blocks, or at least exempt verified Google crawlers from them. If your host blocks foreign traffic by default, ask support to switch it off. If the site is down for everyone and not just for Google, start with is my website down. An expired certificate has its own fix: SSL certificate expired.

Maintenance mode and logins

Turn off "coming soon" and maintenance plugins before you apply, and check that the home page and articles are visible to logged-out visitors. Google's wording for login-protected sites: "consider temporarily removing the login so that we can reach your site." Once the account is active you can set up a crawler login for members-only pages.

Resubmit, and keep the setup stable

When every test passes, open Sites in AdSense, open the site, confirm you've fixed the issues and request a review. Leave the AdSense code, meta tag or ads.txt line in place. Google says the review "usually takes a few days, but in some cases can take 2-4 weeks".

Don't switch DNS, hosting, CDN or security settings while the review runs. A site that's reachable today and blocked next week is the usual way people get this rejection twice. If the status sits at "Getting ready" for a long time, the Getting ready guide explains what's normal. For the rest of the pre-application list, see the approval checklist.

Rule out the access problems in one go

A free Approvalens scan fetches your home page and internal pages as a browser and as Google's crawlers, follows every redirect, reads robots.txt, checks both www variants and the certificate, and flags challenge pages. See whether the crawler can reach your site.

FAQ

My site loads fine for me. Why does AdSense say it's down?

Your browser isn't Google's crawler. Firewalls, geo-blocks and bot protection often treat the two differently. Test with the crawler's user agent, and from Google's network with the Search Console live test.

Does a User-agent: * disallow cause this rejection?

Not directly, because Google says Mediapartners-Google ignores the * group. It does block Googlebot, which can stop ads.txt from being read and makes your content harder to evaluate, so remove it unless you have a reason for it.

How soon after fixing should I resubmit?

As soon as the tests pass. If you changed DNS or the certificate, give it a day to settle everywhere first.

Can I get this rejection if my site was down for only a few minutes?

Yes, if the check happened in that window. That's why uptime monitoring and a stable setup during the review matter.

Do I need to remove Cloudflare?

No. Cloudflare works fine with AdSense when Google's crawlers aren't challenged. Adjust the bot and firewall settings instead of removing the service.

Spotted something out of date or wrong? Tell us and we'll correct it.

Read this guide in Turkish →

Check it on your own site. Free, no sign-up.

Free tools for this

Free scan

Check your own site

The free scan reads your first 50 pages and checks them for Site is reachable, HTTPS certificate, and HTTP to HTTPS redirect, along with everything else in the report.

First 50 pages free · no sign-up · no card