Introduction
Many Blogger users connect a custom domain from GoDaddy and later
discover an AdSense warning that says:
.webp "How to Fix Ads.txt Issues in Blogger Custom Domain Websites (GoDaddy + AdSense Complete Guide)")
The AdSense
Warning
⚠ Earnings at risk – You need to
fix some ads.txt file issues to avoid severe impact to your revenue.
At
first glance, everything may appear correct. The ads.txt file is added in
Blogger, AdSense Auto Ads are enabled, and the website is working normally.
However, Google still fails to detect the ads.txt file.
I
recently faced this exact issue on a Blogger website using a custom GoDaddy
domain. After several hours of troubleshooting DNS records, redirects, HTTPS
settings, and Blogger configurations, I found the root cause and successfully
fixed it.
This
guide explains the complete process step by step.
What is Ads.txt?
Ads.txt (Authorized Digital Sellers) is a text file that helps
prevent advertising fraud by allowing website owners to declare which companies
are authorized to sell their ad inventory.
A typical AdSense ads.txt file looks like this:
google.com, pub-XXXXXXXXXXXXXXX, DIRECT,
f08c47fec0942fa0
Google recommends implementing ads.txt to maximize advertising
revenue and avoid warnings inside AdSense.
Common AdSense Warning
Most Blogger users see a message similar to:
Earnings at risk – You need to fix some ads.txt file issues to avoid
severe impact to your revenue.
Even after adding the ads.txt file correctly, the warning may
remain.
Step 1:
Enable Custom Ads.txt in Blogger
Navigate to:
Blogger → Settings → Monetization
Enable:
Custom ads.txt
Add your AdSense publisher ID:
google.com, pub-XXXXXXXXXXXXXXX, DIRECT,
f08c47fec0942fa0
Screenshot:
Step 2: Verify Ads.txt
URL
Open:
https://www.yourdomain.com/ads.txt
If configured correctly, you should see your AdSense publisher ID.
Step 3: Test Root
Domain Ads.txt
Now check:
https://yourdomain.com/ads.txt
This is where many Blogger users discover the real problem.
Common issues include:
·
404 Not Found
·
Redirect errors
·
GoDaddy parked pages
·
SSL issues
Step 4:
Check Blogger Publishing Settings
Open:
Blogger → Settings → Publishing
Verify:
Custom Domain
www.yourdomain.com
Redirect Domain
Enabled
yourdomain.com
→ www.yourdomain.com
HTTPS Availability
Enabled
HTTPS Redirect
Enabled
Screenshot:
Step 5: Check
GoDaddy DNS Records
Many users discover that their root domain is still pointing to
GoDaddy parking servers instead of Blogger.
Incorrect configuration:
Parked
or
15.197.225.128
3.33.251.168
These records are commonly used by GoDaddy forwarding and parking
services.
Correct Blogger
DNS Configuration
Replace root domain A records with:
216.239.32.21
216.239.34.21
216.239.36.21
216.239.38.21
TTL:
600 seconds
Screenshot:
Required CNAME Records
Keep these records:
CNAME
www →
ghs.google.com
Blogger Verification Record
xxxx → gv-xxxx.dv.googlehosted.com
Do not delete
these records.
Step 6: Remove
GoDaddy Parking
Many users discover that GoDaddy still displays:
This domain is parked free, courtesy of GoDaddy.com
If this page appears, your root domain is not pointing correctly to
Blogger.
Screenshot:
If you
do not see these records, first remove the custom domain from Blogger and save
the changes. Then add the custom domain again and save it. After reconnecting
the domain, you should see the records shown in the image above, and the old
parked record can be removed. Once the DNS records are updated correctly, the
GoDaddy parked page should disappear.
Step 7: Verify Redirects
After DNS propagation:
The following should work correctly:
Homepage
https://yourdomain.com
Redirects to:
https://www.yourdomain.com
Ads.txt
https://yourdomain.com/ads.txt
Redirects to:
https://www.yourdomain.com/ads.txt
Step 8:
Wait for Google AdSense Recrawl
Even after fixing everything, AdSense may continue showing the
warning temporarily.
Google usually takes:
·
24–48 hours
·
Sometimes up to 7 days
to recrawl and verify the updated ads.txt file.
This is completely normal.
Additional Blogger SEO Checks
While troubleshooting ads.txt, I also verified:
Canonical Tags
Example:
<link href='https://www.yourdomain.com/post-url.html' rel='canonical'/>
Sitemap
Submit:
https://www.yourdomain.com/sitemap.xml
Avoid submitting URLs containing:
?m=1
HTTPS
Always enable:
·
HTTPS Availability
·
HTTPS Redirect
inside Blogger settings.
Final Checklist
Before waiting for AdSense verification, confirm:
✅ Custom ads.txt enabled in Blogger
✅ ads.txt opens on www domain
✅ ads.txt redirects correctly from root domain
✅ Redirect domain enabled
✅ HTTPS enabled
✅ GoDaddy parking removed
✅ Blogger A records configured
✅ Correct CNAME records present
✅ Sitemap submitted
Conclusion
Most
Blogger ads.txt problems are not caused by Blogger itself. The real issue is
usually incorrect DNS settings, GoDaddy parking records, forwarding conflicts,
or root-domain redirect problems.
By
updating Blogger settings, replacing GoDaddy parking records with Blogger’s
official A records, enabling HTTPS, and verifying ads.txt accessibility, you
can resolve the issue permanently and restore AdSense compliance.
If
you recently made changes, allow a few days for Google to recrawl your website
before expecting the warning to disappear.
