Keeping ads.txt, app-ads.txt, sellers.json and SChain accurate and short, so buyers can verify the supply path. Covers DIRECT and RESELLER labels, cutting reseller and duplicate lines, files that ad tech crawlers can reach, and how each SSP names the publisher in its sellers.json.
What named sources recommend, and how they say to do it or measure it, newest first.
A Beeler.Tech community member recommends: If a buyer reports your ads.txt missing, check that your CDN does not block its crawler. Add a bypass rule.
From Beeler.Tech community (one member)
Keep in mind: One member. Another member's rep told them to ignore the status.
Members of the Beeler.Tech community recommend exempting ads.txt and app-ads.txt from CDN bot rules, so Amazon and other ad tech crawlers can read them.
From Beeler.Tech community (two publishers)
Keep in mind: One member rate-limited Amazon's crawler at the CDN in August 2026 after a spike; throttling and access to ads.txt need separate rules.
James Strang of JS.Consulting recommended on 2026-09-10 checking how each SSP names you in its sellers.json. Look for intermediary labels, site names or retired company names.
From James Strang, JS.Consulting, Beeler.Tech
Keep in mind: James Strang also sells a tool for managing these files.
James Strang of JS.Consulting recommended on 2026-09-10 testing ads.txt with simulated ad tech crawler requests, not a browser. Firewalls can block crawlers while people still see the file.
From James Strang, JS.Consulting, Beeler.Tech
Keep in mind: In his demo, two large publisher sites returned a 403 error to simulated buyer crawlers. James Strang also sells a tool for managing these files.
Members of the Beeler.Tech community recommend labeling an ads.txt line DIRECT only when that seat pays the publisher. Label other lines RESELLER.
From Beeler.Tech community (several members)
Keep in mind: Members noted an exception where the publisher controls the account, which exists for Google Open Bidding.
Members of the Beeler.Tech community recommend this test of a curator or reseller's added demand. 1. Take one of its reseller seats with a friendly SSP. 2. Compare your direct requests with its requests over a set period. 3. Read 3x to 5x duplication as a sign that it brings no unique demand.
Observations and reported facts, newest first.
James Strang of JS.Consulting said on 2026-09-10 that some buyers filter out sites with more than 1,000 ads.txt lines.
From James Strang, JS.Consulting, Beeler.Tech
Keep in mind: No buyer was named.
Playwire said in the Beeler.Tech community in July 2026 that it had removed all resellers from its supply path.
From Playwire (vendor), via Beeler.Tech community, Rob Beeler
Keep in mind: Vendor's own announcement, relayed by Rob Beeler. Two publishers said it gave no performance data.
Named views and readings, newest first. A view is not a fact.
James Strang of JS.Consulting said on 2026-09-10 that a buyer that cannot fetch a publisher's ads.txt cannot verify its SChain either.
From James Strang, JS.Consulting, Beeler.Tech
James Strang of JS.Consulting said on 2026-09-10 that labeling a line RESELLER when the SSP lists the publisher as publisher can suppress demand.
From James Strang, JS.Consulting, Beeler.Tech
Keep in mind: His reason: one major DSP has said it avoids buying through resellers. No data shown. Labels are self-declared and buyers enforce them unevenly.
Beeler.Tech community members said in September 2026 that many DSPs refuse to bid on RESELLER lines, which pushes some SSPs to misdeclare lines as DIRECT.
From Beeler.Tech community (several members)
Keep in mind: On a 2026-09-10 Beeler.Tech call, an attendee said the label can shade the bid price rather than block the bid. No data was shown.
Beeler.Tech's 2026-09-21 write-up of its Camp.Fire with James Strang covers how ads.txt, sellers.json and SChain depend on each other and what breaks.
From Beeler.Tech
Add https://mcp.beeler.tech/mcp to Claude or ChatGPT as a custom connector, once. Then ask: “What do publishers report about clean up supply chain declarations?” It answers from these statements, with every source named and linked.
Every statement links to its source and says when Beeler.Tech has a tie to it, such as an In View client. Vendors are named as vendors. Community observations are anonymous; here is how we use them. Corrections are made in public.
