We Fixed a 'Site Down' and AdSense Rejection Issue in 24 Hours

This is the story one of my client—let's call him Alex. Alex had a perfect tech blog. It was fast, it had 30 high-quality articles, and it had a clean design. He applied for AdSense and waited. Two weeks later, the rejection email came:

"Status: Site down or unavailable."

Alex was confused. He opened his phone—the site loaded fine. He asked his friends in the UK and India to check—it loaded fine. He checked his uptime monitor—100% uptime.

He applied again. Rejected. Same reason.

He came to me frustrated. "My site is NOT down!" he shouted. "Google is broken."

I told him what I tell everyone: Google isn't broken. You are blocking them.

Here is exactly how we diagnosed the problem and the "weird" technical fix that got him approved in less than 24 hours.

The Diagnosis: Who is "Google"?

When you visit your website, you are a human. When AdSense visits, they are a robot—specifically, the AdSense Crawler.

Most people don't know that the AdSense Crawler often comes from servers in the United States.

We dug into Alex's server logs (the raw data files that show every visitor). We looked for "Googlebot." We saw something shocking. Every time Googlebot tried to access his homepage, the server responded with a 403 Forbidden error.

To a human, the site said "Welcome!" To Google, the site said "Get out."

The Culprit: A Paranoid Security Plugin

Alex was using a popular WordPress security plugin (I won't name names, but it rhymes with "WordFence").

He had turned on a setting called "Block Traffic from Specific Countries" because he was getting spam comments from certain regions. He didn't realize that by blocking huge chunks of the world, he had accidentally blocked the IP range that Google uses to crawl new sites.

Furthermore, he was using Cloudflare. Cloudflare has a "Bot Fight Mode." Sometimes, if this is set to "High," it challenges Googlebot with a CAPTCHA.

Robots cannot solve CAPTCHAs. So, the bot gave up and reported "Site Down."

The 5-Minute Fix

Here is exactly what we did to solve it:

1. Whitelisted Google IPs: We went into his security plugin and explicitly whitelisted the User-Agents Googlebot, AdsBot-Google, and Mediapartners-Google.
2. Disabled Geo-Blocking: We turned off the country blocking feature temporarily for the approval period.
3. Cloudflare Check: We went to his Cloudflare Dashboard -> Security -> WAF and created a rule to "Allow" known bots.

The Result

We made these changes at 4:00 PM. We resubmitted the AdSense application at 4:15 PM.

The next morning at 9:00 AM, Alex got the email: "Congratulations! Your site is now ready to show AdSense ads."

Checklist: Is Your Site Blocking Google?

If you are getting the "Site Down" error but your site works for you, check these three things immediately:

1. Check your robots.txt: Go to yourdomain.com/robots.txt. Does it say Disallow: /? If yes, delete that line.
2. Turn off "Under Construction" Mode: Some plugins show a "Coming Soon" page to visitors who aren't logged in. Google isn't logged in, so they see a blank page.
3. Check Your Firewall/CDN: If you use Cloudflare, Ezoic, or a security plugin, check your "Firewall Events" log. If you see Googlebot being blocked, that is your smoking gun.

Don't let a hidden setting cost you revenue.