Implement and validate an ads.txt file to declare a publisher's Authorized Digital Sellers per the current IAB Tech Lab spec

domain: iabtechlab.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Publish a plain-text /ads.txt file at the root domain (and subdomains as needed) listing each authorized seller as a comma-delimited record
  2. Adopt Ads.txt 1.1 fields where relevant — OWNERDOMAIN and MANAGERDOMAIN — to declare ownership/management relationships introduced in the August 2022 spec update
  3. Verify the file is reachable over HTTP/HTTPS at the standard relative path from every domain that serves the publisher's inventory
  4. Cross-check declared seller IDs against each SSP's sellers.json file for consistency
  5. Re-crawl and re-validate the file periodically, since ads.txt is a living declaration that changes as seller relationships change

Known gotchas

Related routes

Retrieve and validate an ads.txt file programmatically and check seller authorization status via sellers.json
iabtechlab.com · 6 steps · unrated
Implement app-ads.txt to declare authorized sellers for a mobile or CTV app's ad inventory
iabtechlab.com · 5 steps · unrated
Publish a sellers.json file and adopt the OpenRTB SupplyChain object for programmatic supply chain transparency
iabtechlab.com · 5 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans