What to record when an ads.txt warning appears but ads still serve

When an ads.txt warning appears but ads still serve, record the warning text, file URL, publisher line, crawl timing, domain version, and whether the issue affects all pages or only some inventory.

An ads.txt warning can be confusing because revenue may continue while the platform is still checking the file. The creator may fix the file, see ads serving, and assume the warning is stale. Or the creator may see the warning and repeatedly edit the file without checking whether the public URL, redirect, www versus non-www domain, cache, or publisher id line is actually correct.

A useful note starts with the public ads.txt URL and the exact line expected by the ad platform. Then record the domain used in the account, whether the file is reachable without login, whether it returns plain text, whether redirects change the host, and when the file was last updated. If multiple domains or subdomains exist, list which one serves the file.

Do not treat “ads still show” as proof that the warning can be ignored. Also do not make repeated edits every few minutes. Verification systems may need time to recrawl. The better action is to fix the public file once, preserve the evidence, and wait for the documented check cycle unless another concrete mismatch appears.

The practical question is simple: can a clean public request reach the exact authorized seller line for the exact domain the account expects?

What to record when an ads.txt warning appears but ads still serve

// COMMENTS

ON THIS PAGE