What to check when ads.txt is visible but AdSense still says not found

When ads.txt is visible in a browser but AdSense still says it is not found, treat the browser view as only one signal. The file may be reachable from one host while the ad system checks another host, or it may be correct now but not yet recrawled. The useful response is to document the exact route rather than repeatedly editing the same line.

Google’s ads.txt guidance says the file should live at the root of the domain, for example example.com/ads.txt, and include the publisher IDs allowed to request ads for that domain. For a Google AdSense line, the visible pieces usually include google.com, the publisher ID, DIRECT or RESELLER, and the Google certification authority ID.

A good checklist includes the canonical domain, www versus non-www behavior, HTTPS redirect, HTTP status, final URL after redirects, file content, publisher ID, cache layer, robots or firewall rules, and the last modified time. If a site uses a CDN or static host, also check whether the root path is served by the same deployment as the page where ads run.

The conclusion should be modest: file present, line matches account, host route confirmed, waiting on recrawl; or host mismatch found, redirect problem found, publisher ID mismatch found. This format is easier to review than a vague “ads.txt broken” note.

What to check when ads.txt is visible but AdSense still says not found

// COMMENTS

ON THIS PAGE