How to Fix Ads.txt Status Not Found Error in Google AdSense (Solved)

Ads.txt Status Not Found even after uploading the file? Fix Cloudflare cache, encoding issues, SPA routing conflicts, and .htaccess blocks step by step.

Ekin Yalgın

November 28, 2025·5 min read

How to Fix Ads.txt Status Not Found Error in Google AdSense (Solved)

You upload the required file, check the URL in your browser, and it loads fine. But the AdSense dashboard still shows Status Not Found. The crawler is failing for a different reason entirely.

- Standard Crawl Time: 24 to 48 hours
- Required Protocol: HTTPS only
- Target Path: root-domain/ads.txt
- Common Blockers: Cloudflare cache, UTF-8 BOM, SPA routing

Decoding AdSense Error States

Google provides different warnings for different crawler failures. Treating them all as a missing file wastes time.

Status Not Found vs. No File

No File means the crawler reached your server but got a 404 response. Status Not Found often indicates a timeout, a 403 Forbidden block, or a redirect loop. The file exists, but the bot cannot read the contents.

Unauthorized

The crawler reads the file successfully. However, your publisher ID does not match the active AdSense account. This also happens when advertisers cross-reference your site with the sellers.json database and find discrepancies.

Invalid Format

The text file contains syntax errors: missing commas, incorrect spacing, or hidden HTML tags mixed into the plain text. Each line must follow this exact format:

google.com, pub-0000000000000000, DIRECT, f08c47fec0942fa0

The four fields are: ad network domain, your publisher ID, relationship type (DIRECT or RESELLER), and the IAB certification authority ID.

The Hidden Culprits Behind Crawler Failures

You see the file in your browser. The crawler sees a broken response.

File Encoding Errors

Creating the file in Notepad or Word often adds invisible byte-order marks. Save the document strictly as UTF-8 without BOM using a plain text editor like VS Code or Notepad++. Windows line endings (CRLF) also cause silent parse failures on Unix-based servers. Use LF line endings when uploading to Linux hosts.

HTTP vs. HTTPS Discrepancy

Your browser auto-redirects to HTTPS. The AdSense bot only checks the HTTPS path and does not follow HTTP-to-HTTPS redirects for .txt files on some server configurations. Verify directly:

curl -I https://yourdomain.com/ads.txt

The response must return HTTP/2 200. Anything else means the file is unreachable to the crawler.

WWW vs. Non-WWW Redirect Loops

Google checks the root domain. If your site lives on the www subdomain, configure a clean 301 redirect from yourdomain.com/ads.txt to www.yourdomain.com/ads.txt. Multiple redirect hops cause the crawler to time out without reporting a specific error.

Fixing Issues in Modern Tech Stacks

Cloudflare Cache Bypass

Cloudflare caches static assets aggressively. After you update the file on your server, Cloudflare can keep serving the old 404 to Google for days. Create a Page Rule:

Go to Rules > Page Rules in your Cloudflare dashboard
Set the URL to *yourdomain.com/ads.txt
Set Cache Level to Bypass
Save and purge your cache

This forces Cloudflare to fetch the live file from your origin server on every request.

SPA Routing Hijacking

React Router and Vue Router intercept all URL requests, including /ads.txt. The bot requests the file but receives a rendered React component instead of plain text. The fix: place the file in your /public directory and configure your web server to serve it before the SPA catches the request.

For Nginx:

location = /ads.txt {
    root /var/www/html/public;
    try_files $uri =404;
}

Custom Framework File Placement

Next.js and Laravel both serve static files from a specific folder:

Framework	Correct path
Next.js	`/public/ads.txt`
Laravel	`/public/ads.txt`
Vercel	`/public/ads.txt` + no rewrites rule needed
Netlify	`/public/ads.txt`, ensure no `_redirects` rule catches `/*`

Placing the file in the project root instead of /public makes it inaccessible to external requests.

Standard Platform Solutions

WordPress Configurations

Upload the file via FTP or cPanel File Manager to /public_html/ads.txt. This is the root directory for most WordPress installations. If you lack server access, use a plugin like Ads.txt Manager under Settings.

Security plugins can silently block crawler access to text files in your root directory. Check your firewall plugin's settings for rules that block access to .txt extensions. The same configuration layer that causes WordPress database connection errors can also restrict file access at the server level.

Shopify

Shopify restricts root FTP access entirely. Navigate to Online Store > Preferences in your dashboard and use the built-in ads.txt editor there. Do not try to upload via FTP.

Checking .htaccess and robots.txt Blockages

If your .htaccess contains a broad deny rule for text files, the crawler receives a 403 and reports Status Not Found. Add an explicit exception:

<Files "ads.txt">
    Allow from all
    Satisfy Any
</Files>

Also verify your robots.txt does not block the AdSense crawler:

User-agent: Mediapartners-Google
Disallow:

An empty Disallow after the user agent directive means full access is allowed.

Troubleshooting Checklist: Where to Start

If you have already uploaded the file and still see the error, work through this order:

Check the HTTPS URL directly (curl -I https://yourdomain.com/ads.txt) - must return 200
Check encoding - open the file in VS Code, look for BOM indicator in the status bar
Check Cloudflare - purge cache and add the Page Rule if using Cloudflare
Check .htaccess - look for Deny from all or FilesMatch rules covering .txt files
Check SPA routing - if using React/Vue, verify your web server serves the static file before the SPA catches the request
Wait and recheck - if all of the above pass, the crawler just needs time; the dashboard updates within 24 to 48 hours

How to Verify Your Fix

Test the setup immediately rather than waiting.

Run your domain through the Google Ads.txt Validator or AdStech.io. These tools simulate the exact crawler behavior and detect encoding issues, redirect problems, and publisher ID mismatches before Google's bot makes its next visit.

One more thing: never upload the file to a subdomain. Even if your entire blog runs on blog.yourdomain.com, Google requires the verification file at yourdomain.com/ads.txt. Once the root domain file is accessible, all subdomains are covered automatically.

FAQ

Frequently Asked Questions

After the file is correctly placed and accessible at your HTTPS root URL, Google's crawler typically clears the warning within 24 to 48 hours. In some cases it takes up to a week, depending on how frequently the crawler visits your domain.

The most common causes are Cloudflare or server-side caching serving an old 404 to the bot, a redirect loop between www and non-www versions, or a .htaccess rule blocking access to .txt files. Run curl -I https://yourdomain.com/ads.txt to verify the file returns a 200 status before waiting for the crawler.

It must be in the root directory of your primary domain, accessible at https://yourdomain.com/ads.txt. For WordPress this is public_html, for Laravel and Next.js it is the /public folder. Never place it in a subdirectory or on a subdomain.

Unauthorized means the crawler found the file but your publisher ID does not match your active AdSense account. Re-copy the code snippet directly from your AdSense dashboard under Sites and replace the existing file content.

Yes. Add one line per ad network. Each line follows the format: domain, publisher-id, DIRECT or RESELLER, certification-authority-id. Keep your Google AdSense line intact and add other networks on separate lines below it.

Not found means the crawler could not access or locate the file at all, usually due to a 404, 403, or redirect issue. Unauthorized means the file was found and read successfully, but the publisher ID inside does not match your AdSense account.

Create a Page Rule in Cloudflare that matches the pattern *yourdomain.com/ads.txt and sets Cache Level to Bypass. Then purge your cache. This forces Cloudflare to fetch the live file from your origin server on every request instead of serving a cached version.

Not directly. The file is read by ad exchanges, not search engine crawlers. However, leaving the warning active reduces your ad fill rate and revenue without any ranking benefit from fixing it.

Published in

Web Development