How to Technically Fix AdSense ads.txt Issues on Blogger

How to Fix AdSense ads.txt Issues on Blogger (Custom Domain Guide for Myke Educate Readers)

If you’re using Blogger with a custom domain, there’s a high chance you’ve seen this frustrating message inside AdSense:

“Earnings at risk – You need to fix your ads.txt file to avoid severe impact to your revenue.”

 

Annoying, right?

Many bloggers on Myke Educate have asked the same question:
“Why does AdSense say my ads.txt is missing when I already added it?”

Don’t worry — this is one of the most common issues for Blogger users with custom domains. And in this article, I’ll break down:

• Why AdSense keeps saying ads.txt is missing
• How Blogger handles ads.txt differently
• The real reason it fails on custom domains
• Step-by-step fix that works 100%
• Mistakes you must avoid

Let’s get into it.

Why AdSense Says Your ads.txt Isn’t Set Up (Even When It Is)

Here’s what most bloggers don’t realise:

1. Blogger and Your Custom Domain Don’t Always Match

Example:

• Your custom domain: something.net
• Blogger internal domain: blog.something.net

AdSense only checks the root domain — so it expects to find:

https://something.net/ads.txt

If it's only available inside:

https://blog.something.net/ads.txt

AdSense won’t see it.
Result? ❌ “ads.txt missing” warning.

One user fixed it instantly by adding ads.txt to BOTH locations.

2. It May Take Several Submission Attempts

Many users report:

• 3 to 4 rechecks
• Repeated “needs attention” messages
• Delay before AdSense accepts it

This is normal.
AdSense just takes time to crawl and verify the new file.

But it will fail permanently if your root domain is not secure.

3. HTTP vs HTTPS Misconfiguration

Here’s a major reason ads.txt fails:

Your main domain is not HTTPS, even if it redirects to your secure Blogger blog.

AdSense checks the root first, not the redirect.

So if:

• http://something.net/ads.txt is insecure
• and only the subdomain is secure

AdSense fails the verification.

Fix:
Make sure your custom domain has HTTPS enabled inside Blogger → Settings.

4. You Cannot Add AdSense Code Manually

This confuses many bloggers.

Unlike WordPress, Blogger has its own AdSense integration.

If you try:

• pasting AdSense code manually
• adding ad units via HTML
• using the standard setup method

You will break things and cause the ads.txt warning to reappear.

Blogger wants you to connect AdSense through the Earnings tab only.

How to Fix AdSense ads.txt Issues on Blogger (Working Solution)

Here’s the exact fix that works for 99% of bloggers.

Step 1: Disconnect AdSense in Blogger

Go to:

Blogger → Earnings tab
→ Remove any connected AdSense account.

Step 2: Remove All Manual AdSense Widgets

Go to:

Layout → Remove all AdSense widgets

Never add ad code manually in Blogger.

Step 3: Add Your Correct ads.txt File

Go to:

Settings → Search Preferences → Custom ads.txt
→ Turn it ON
→ Paste your official AdSense ads.txt record

It should look like this:

google.com, pub-xxxxxxxxxxxxxxxx, DIRECT, f08c47fec0942fa0

(Get this from your AdSense account.)

Step 4: Make Sure HTTPS Is Enabled

Go to:

Settings → HTTPS
→ Enable both options:

• ✓ HTTPS Availability
• ✓ HTTPS Redirect

This is critical.

Step 5: Wait for Google to Re-Crawl Your Domain

Most people see the error disappear in:

⏱ 2–24 hours
⏱ Sometimes 48 hours

This is normal.

When fixed, AdSense will show:

✔ “No issues with your ads.txt file”
✔ Ads start running normally

Extra Tips That Helped Many Blogger Users

Here’s what others discovered while fixing their sites:

✔ Add ads.txt to BOTH your custom domain and your Blogger internal domain

(Useful if you use subdomain setups.)

✔ Make sure your DNS records are correct

Wrong DNS settings = AdSense can't verify ads.txt.

✔ Don’t add multiple ads.txt versions

Only ONE file should exist.

Final Thoughts: Yes, This Problem Is Fixable

If you’re running your blog on Blogger with a custom domain and you're seeing ads.txt errors, you're not alone. Every Myke Educate blogger has run into it at least once.

The good news?

The fix is SIMPLE:

• Remove old AdSense connections
• Remove ad widgets
• Add correct ads.txt
• Enable HTTPS
• Wait for verification

Follow this guide, and your ads.txt issue will disappear, and your AdSense account will be fully active again.