Ads.txt review stuck? Three quick checks to clear AdSense warnings
When AdSense keeps flagging ads.txt even after you fixed it, confirm these three points—file location, exact syntax, and cache/recrawl timing—so the re-review finishes smoothly.
Conclusion
When AdSense keeps flagging ads.txt even after you fixed it, confirm these three points—file location, exact syntax, and cache/recrawl timing—so the...
What you will learn
- The basic way to read this topic
- Practical caveats to check before using it
- Related articles to read next
If AdSense keeps showing an ads.txt needs attention warning even after you edited the file, the issue is usually about how Google crawls and caches that file—not that you wrote it wrong. Based on Google’s own specs and real troubleshooting, here are the three checks that resolve most stuck re-reviews.
Why ads.txt re-review gets stuck
Google’s crawler must (1) find the file at the exact root path, (2) read a line that matches the spec perfectly, and (3) refresh its cache. Miss any one and the warning can linger for days.
Check 1: File lives at the public root
Why it matters
Google only looks for https://your-domain/ads.txt. A different path—or a file that requires auth—won’t be read.
Do this
- Open
https://your-domain/ads.txtin a browser; confirm a 200 OK and plain text. - No redirects to other paths; no 404/403; no login prompts.
- On Next.js/Vercel, place the file in
public/ads.txtso it deploys to the root.
Check 2: Lines match the official format exactly
Why it matters ads.txt is strict; a single stray character can invalidate the line.
Correct pattern
google.com, pub-XXXXXXXXXXXXXXXX, DIRECT, f08c47fec0942fa0
- Order: ad system domain, publisher ID, relationship, certification ID (optional but recommended).
- Use commas, not tabs; no extra spaces or comments; one record per line.
Common mistakes
- Typo in the
pub-number. - Hidden characters (copy/paste from editors that add non-ASCII spaces).
Check 3: Allow for crawl and cache timing
Why it matters Updates are not instant. Google recrawls periodically, and CDNs may keep serving the old file.
Guideline
- Expect 48 hours to several days for the warning to clear.
- Purge CDN cache (Vercel, Cloudflare, etc.) after edits.
- Avoid rewriting the file repeatedly; it can extend the crawl window.
Quick checklist before you wait
ads.txtis at the site root and publicly reachable.- Each line follows
google.com, pub-..., DIRECT, f08c47fec0942fa0with no extra characters. - CDN cache cleared; now wait at least 2–7 days for recrawl.
Summary
Most ads.txt re-review delays come from path issues, tiny syntax slips, or caching. Fix the root path, verify the exact line format, purge caches, and give Google a few days. Follow that order and the AdSense warning usually disappears without further edits.
What to do next
- Check the source or official information before making an important decision.
- Separate what applies to your use case from what does not.
- Read a related pillar article to add more context.