Google won't auction a request an ads.txt file can't verify

The revenue mechanism

Ads.txt is a voluntary industry specification; nothing in the file format itself stops a buyer from ignoring it. Google Ad Manager is where that voluntary standard gets practical teeth for the large share of publishers who sell through Google's own exchange and demand. Google's help documentation describes ads.txt and app-ads.txt as tools publishers use "to identify who is authorized to sell your inventory," and states plainly that "use of ads.txt/app-ads.txt is not mandatory, but is highly recommended." The revenue mechanism is what happens next: Google checks the file before it will run an auction for a given request at all, which means a publisher's ads.txt accuracy directly gates whether Google's demand can bid on its inventory in the first place, not merely whether the sale is later flagged as suspicious.

What the documents show

Google's own ads.txt/app-ads.txt FAQ page answers "How does Google enforce ads.txt/app-ads.txt files?" directly: "Google runs an auction and returns a winning ad for requests on sites where an ads.txt/app-ads.txt file exists with a correctly listed publisher identifier. If the identifier in the file is incorrect, an auction is not run for that request." The same page states that domains or apps whose file omits the seller's publisher ID "are no longer monetized through Ad Manager, and Google no longer buys ads on such sites/apps," and that Google crawls every domain it receives requests from "at least once a day," with changes to a file taking up to 48 hours to be detected. A companion page on reviewing authorization status confirms publishers can see, inside Ad Manager, which of their linked accounts are authorized on each domain and the resulting impact on ad unit requests.

The assumptions exposed

This enforcement is scoped to Google's own products: linked AdSense and Ad Exchange seller accounts, checked against Google's own crawl of the file, not a guarantee that every other exchange enforces the same way. The up-to-48-hour detection window means a publisher who just fixed an error, or just changed sellers, should not assume Google's system reflects that change immediately. A publisher may also mistake "Ad Manager shows my domain as authorized" for a statement about every buyer's behavior, when it only confirms Google's own crawl and auction logic.

What to check before you rely on it

This is an editorial checklist. A publisher troubleshooting missing Google demand should check ads.txt authorization status inside Ad Manager before assuming the shortfall has another cause.

• Does Ad Manager show all seller accounts as authorized for every domain you monetize?
• Has it been at least 48 hours since your last ads.txt update, allowing time for Google to re-crawl it?
• Are your app-ads.txt records affected by the same developer-URL dependency documented for the standard generally?

Google's enforcement gives ads.txt real commercial consequences for one major buyer, but it is Google's own policy choice, documented on Google's own pages, not a universal guarantee that every exchange treats an unauthorized listing the same way.