What app-ads.txt is for
app-ads.txt is a plain text file that lists who is allowed to sell ad space in your apps. Advertisers and ad platforms read it to confirm that an ad request really comes from an authorised seller, which cuts down on fraud. Apps without it can see lower fill rates and weaker demand, because buyers prefer inventory they can verify.
Where the file must live
It must be served at the root of your developer website, for example https://yourdomain.com/app-ads.txt, as plain text, with no login and no redirect chain. Crawlers find that website from the “developer website” field on your Google Play listing, so the domain in the listing and the domain hosting the file must match.
The file is read from the root domain. If your listing points to www.example.com, make sure the file also opens there, or that the redirect to it is a simple one.
The format of each line
Each line has four comma-separated fields. For AdMob it looks like this:
google.com, pub-0000000000000000, DIRECT, f08c47fec0942fa0
- Domain: the ad system, google.com for AdMob.
- Publisher ID: your own pub- number from AdMob. Use the real one for each account.
- Relationship: DIRECT when you own the account, RESELLER otherwise.
- Certification ID: the fixed identifier for Google, f08c47fec0942fa0.
Several accounts, one domain
If you publish under more than one Play Console account and more than one AdMob account, put every AdMob publisher ID on its own line in the same file. One file serves all your apps on that domain, so you do not need a separate file per account.
Add a line for every other ad network or mediation partner you use, exactly as that partner tells you. Remove lines for networks you no longer use.
Checking that it works
Open the URL in a private window and confirm that you see plain text. Then check AdMob’s app-ads.txt report for each app. Verification is not instant: allow some time after the first crawl, and re-check after you change the developer website on the listing.
Mistakes to avoid
Uploading the file inside a subfolder, saving it with a hidden extension such as .txt.txt, using a pub ID from the wrong account, and forgetting to update the developer website after moving domains are the usual causes of “not found”.
- Wrong location: the file is not at the root.
- Wrong domain: the listing points elsewhere.
- Typos: a missing comma or a stray space breaks the line.
- Stale lines: old networks left in the file for years.