Your app earns less without a valid app-ads.txt.
app-ads.txt errors aren't just in the file. They're in the connection between your app store listing, developer website, and hosting setup. Our checker validates the full chain against 2,000+ SSP sellers.json files.
Works for iOS, Android, and CTV apps. Free. Instant results.
Same format. Completely different failure modes.
app-ads.txt lives on your developer website, not your app domain.
The app store developer URL must point to the correct website or DSP crawlers never find your file.
Every ad network in your mediation waterfall needs an entry -- not just your primary SDK.
The 7 most common app-ads.txt problems.
The biggest issues aren't in the file itself.
No developer URL in app store
No URL in Google Play Console or App Store Connect means no crawler can find your file.
Wrong developer URL
App store listing points to a marketing site, not the domain hosting app-ads.txt.
Missing mediation partners
Primary SDK is listed, but the other networks in your waterfall are missing entries.
SSL or hosting failures
Expired certificate, wrong content type, or too many redirects block DSP crawlers.
Account ID mismatches
Your publisher ID doesn’t match the ad network’s records.
Stale entries after SDK changes
Switched mediation platforms but left old entries, or added a new SDK without adding app-ads.txt entries.
sellers.json verification failures
The ad network doesn’t list you in their sellers.json file.
Setting up app-ads.txt correctly.
Find your developer website URL
This is the URL in Google Play Console (Store listing > Website) or App Store Connect (App Information > Marketing URL).
Create the app-ads.txt file
Same format as ads.txt. One line per authorized seller: ssp-domain.com, account-id, DIRECT|RESELLER, [tag-id]
Add every ad network
List your primary SDK, every mediation partner, and every reseller in your waterfall.
Host it at the root
Upload to https://your-developer-site.com/app-ads.txt. Must be HTTPS, correct content-type, directly accessible.
Validate
Run through BeamFlow’s checker to verify every entry against live sellers.json files.
Don't have a developer website? BeamFlow offers free app-ads.txt hosting.
How BeamFlow checks your app-ads.txt.
Fetch
We fetch your app-ads.txt from your developer website domain.
Parse
Every line parsed: SSP domain, account ID, relationship type, TAG ID.
Cross-reference
Each entry verified against the SSP’s live sellers.json from 2,000+ SSPs.
Report
Health score (A-F), color-coded line status, and fix recommendations.
app-ads.txt checker FAQ
Enter your developer website URL above. BeamFlow fetches your app-ads.txt and verifies every entry against 2,000+ SSP sellers.json files.
Google Play requires it for apps serving ads. Apple doesn’t mandate it yet, but DSPs check it regardless. Without it, your inventory is treated as unverified.
Same format, different location. ads.txt lives on your website. app-ads.txt lives on your developer website (the URL in the app store). For apps, DSPs check app-ads.txt.
On the domain listed as your developer website in the app store. Root path: https://developer-site.com/app-ads.txt. HTTPS required.
In Google Play Console, go to Store presence > Store settings > Contact details. Enter your developer website. Host app-ads.txt at that domain’s root.
In App Store Connect, go to My Apps > App Information. Set the Marketing URL. Host app-ads.txt at that domain’s root.
Yes. Every ad network that can fill an ad needs an entry. AdMob + Meta + Unity + ironSource = all four need entries.
Yes. Free hosting with guided setup wizard. No server needed. Visit beamflow.co/host to get started.
Check your app-ads.txt in 30 seconds.
Free for iOS, Android, and CTV apps. No signup required.