Start by adding your publisher IDs or pick a template on the left.
WeForAds auto-generates and maintains your ads.txt for you. Every time we add a demand partner, your file updates automatically. No more missed records, no more manual edits.
Sign Up Free →ads.txt).https://yoursite.com/ads.txt.Each line of your ads.txt follows this structure:
DOMAIN, PUBLISHER_ACCOUNT_ID, DIRECT or RESELLER, CERTIFICATION_AUTHORITY_ID
google.com, not adsense.google.com).DIRECT if you have a direct contract; RESELLER if the network is authorized to resell your inventory.google.co instead of google.com)Your ads.txt should list every ad network authorized to sell your inventory, one record per line. Include every demand partner you work with — partners that can't find themselves in your file will stop bidding on your inventory without warning.
Upload it to the root of your domain so it's accessible at https://yoursite.com/ads.txt. Must be served with Content-Type: text/plain and return HTTP 200. Not /ads.txt.html, not in a subfolder.
Two options: host a separate ads.txt at each subdomain root (e.g. blog.yoursite.com/ads.txt), or use a SUBDOMAIN= directive in your main file to delegate. Option 2 is simpler but still requires each subdomain's DNS to resolve to serve the file.
Every time you add or remove a demand partner. For header bidding publishers with many partners, this can be weekly. WeForAds auto-updates your ads.txt whenever the partner list changes.
No. Everything runs in your browser — nothing is sent to our servers. Close the tab and it's gone.
Yes. This tool generates files strictly following the IAB Tech Lab ads.txt 1.1 specification. Validate with our ads.txt validator to confirm.