What is Ads.txt?

Abisola | Feb 14, 2026

Ads.txt (Authorized Digital Sellers) is a plain text file publishers host at the root of their domain. Each line names an advertising system allowed to sell their inventory, the publisher’s account ID there, and whether the link is DIRECT or RESELLER. Buyers use it to confirm sellers are authorized before they bid.

The file is public, human-readable, and machine-parsed, which made adoption faster than heavier certification schemes alone.

How ads.txt is used in bidding

Demand-side platforms and related tools crawl example.com/ads.txt and cache the results. During an auction, the buyer compares the seller declared on the bid request with the publisher’s file. If the seller is not listed, many buyers skip the bid to reduce domain spoofing and unauthorized resale.

Syntax matters: typos or wrong publisher IDs can block legitimate revenue. Publishers update the file when they add or remove partners. Optional fields can include certification IDs where partners support them. Schedule reviews after every new SSP or exchange onboarding so sales teams are not surprised by sudden bid drops.

Why ads.txt matters for ad fraud

Spoofing is listing fake inventory as if it came from a premium site. Ads.txt shrinks the window by requiring a public match between domain and seller. It does not stop every abuse: bot traffic, invalid clicks, and creative fraud can still occur on authorized domains, so treat ads.txt as one layer in a broader ad fraud strategy.

For advertisers, enforcing ads.txt checks cuts spend on misrepresented web supply and complements click fraud work on other channels. Publishers gain trust and fewer blocked bids when the file is accurate. Layer policy with invalid impression hygiene and detection fundamentals you already trust.

  • Sellers.json on the sell side discloses who monetizes for each seller ID
  • Supply-path reviews to remove redundant resellers
  • Monitoring for stale or oversized files that signal poor governance
  • Cross-checks with analytics when spoofed domains still send referral traffic flagged as suspicious activity downstream

Frequently Asked Questions

  • Does ads.txt block all fraud?

    No. Ads.txt (Authorized Digital Sellers) targets unauthorized selling and domain spoofing by listing which ad systems may sell a publisher's inventory. It does not stop bot traffic, invalid clicks, or creative fraud on authorized domains. Treat ads.txt as one transparency layer alongside seller files, supply-chain checks, and click fraud controls on other channels.

  • What breaks if ads.txt is wrong?

    Demand-side platforms compare bid sellers against the publisher's ads.txt file. Typos, wrong publisher IDs, or stale entries can cause buyers to skip bids, which shows up as sudden revenue drops. Fix syntax, update partner lines after onboarding, and allow time for crawlers to refresh cached copies of your domain's file.

  • Is ads.txt only for huge publishers?

    Any site that sells programmatic ads benefits from hosting ads.txt at the domain root. Small publishers face the same bid blocking when IDs or DIRECT versus RESELLER flags are wrong. Schedule reviews whenever you add or remove an SSP or exchange so sales teams are not surprised by unexplained traffic loss.

  • How often should publishers update ads.txt?

    Update ads.txt whenever you onboard a new supply-side partner, change reseller relationships, or remove a seller ID. Many teams review the file quarterly and after every contract change. Because buyers cache results, even a one-line typo can block legitimate bids until the next crawl completes successfully.

Abisola

Abisola

Abisola handles content and support at ClickPatrol. She helps customers get more value from cleaner traffic data and writes practical resources about ad fraud, fake traffic, and smarter PPC decisions.