Validate ads.txt and app-ads.txt, and check every seller against sellers.json.
Example
Summary
Sellers
| Line | Ad system and seller ID | Type | sellers.json |
|---|
Findings
File
Capabilities and processing
Enter a website and choose ads.txt or app-ads.txt, or paste a file. For a website, our server fetches the file from the root of the host, over HTTPS first, and then each ad system's sellers.json for the seller IDs the file names, for up to 12 ad systems. A pasted file is read in your browser, and its sellers are looked up only when you ask.
Every line is read as the IAB Tech Lab ads.txt 1.1 specification defines it: ad system domain, seller account ID, DIRECT or RESELLER, an optional certification ID, and the CONTACT, SUBDOMAIN, INVENTORYPARTNERDOMAIN, OWNERDOMAIN and MANAGERDOMAIN variables. Lines buyers will skip, duplicates and accounts listed as both DIRECT and RESELLER are flagged, and each seller is checked against sellers.json: DIRECT should be a PUBLISHER seller and RESELLER an INTERMEDIARY. Repairs fix the spelling of relationships, remove duplicates and strip www. or https:// from ad system domains, and the result can be downloaded.
Example workflow
The sample shop's ads.txt has a duplicate line, a misspelled DIRECT that buyers skip, an ad system written with www., a DIRECT account that sellers.json lists as an intermediary, and a seller ID the exchange does not list. Break it duplicates a line, misspells DIRECT, removes a seller ID and writes an ad system as an address, built from your file when you entered one.
Limits and interpretation
A seller that sellers.json does not list may be closed, mistyped or confidential. Ad systems that publish no readable sellers.json cannot be confirmed either way. The ad systems in the sample are fictional. Nothing is stored.
Related tools
robots.txt and sitemap validator · llms.txt checker and generator · All tools · Privacy