Step-by-step guide showing how to fix the ads.txt not detected issue in Blogger and Google AdSense, including ads.txt setup, verification, and successful authorization in 2026.

If you’re using Blogger and seeing the warning “ads.txt not detected” in your AdSense account, don’t panic. This is a common issue—and thankfully, it’s easy to fix once you understand how ads.txt works and how Blogger handles it.

This guide will walk you step-by-step through fixing the problem in 2026.

What Is ads.txt and Why It Matters?

ads.txt (Authorized Digital Sellers) is a simple text file that tells ad networks which companies are allowed to sell ads on your website.

Why it’s important:

  • Prevents ad fraud
  • Ensures you get paid correctly
  • Required by Google AdSense for full monetization

If it's missing or not detected, your earnings can be limited.

Why Blogger Shows “ads.txt Not Detected”

This error usually happens because:

  • You haven’t added your AdSense publisher ID to Blogger
  • The ads.txt file hasn’t propagated yet
  • There’s a formatting mistake
  • Your blog is using a custom domain incorrectly

Step-by-Step: Fix ads.txt Not Detected in Blogger

Step 1: Get Your AdSense Publisher ID

  1. Log in to your AdSense account
  2. Go to Account → Settings → Account Information
  3. Copy your Publisher ID

It looks like this : pub-1234567890123456

Step 2: Add ads.txt in Blogger

  1. Go to your Blogger Dashboard
  2. Click Settings
  3. Scroll down to Monetization
  4. Enable Custom ads.txt
  5. Paste this line : google.com, pub-1234567890123456, DIRECT, f08c47fec0942fa0

Replace with your own Publisher ID.

  1. Click Save

Step 3: Check Your ads.txt File

After saving, your file should be accessible at:

https://yourdomain.com/ads.txt

Open it in your browser. You should see your publisher line displayed.

Step 4: Wait for Detection

AdSense does not update instantly. It may take:

  • 24 hours (usually)
  • Up to 7 days (in some cases)

Be patient—this is normal.

Fix for Custom Domain Users

If you’re using a custom domain (like .com instead of .blogspot.com):

  • Make sure your domain is properly connected to Blogger
  • Check that:
https://yourdomain.com/ads.txt

is accessible (not redirected incorrectly)

If it doesn’t show:

  • Clear browser cache
  • Check DNS settings
  • Disable conflicting CDN or proxy temporarily

Common Mistakes to Avoid

❌ Wrong publisher ID
❌ Extra spaces or formatting errors
❌ Adding multiple incorrect lines
❌ Not enabling “Custom ads.txt” in Blogger
❌ Checking too soon (before propagation)

Bonus: Multiple Ad Networks

If you use more than AdSense, your ads.txt can include multiple lines:

google.com, pub-xxxxxxxxxxxxxxxx, DIRECT, f08c47fec0942fa0
example.com, 12345, RESELLER
anothernetwork.com, 67890, DIRECT

How to Verify ads.txt Is Working

You can confirm it’s fixed by :

  • Opening yourdomain.com/ads.txt
  • Using online ads.txt checker tools
  • Checking AdSense warning disappears

Final Thoughts 

The “ads.txt not detected” warning in Blogger is easy to fix once you know where to look. Most of the time, it comes down to simply adding your publisher ID correctly and waiting for AdSense to verify it. If you’ve followed all steps and still see the warning after a week, the issue is likely related to domain setup or formatting.

Related Posts

No comments:

Post a Comment

Bottom Ad [Post Page]

| Designed by Colorlib