Declare authorized sellers with ads.txt/app-ads.txt

Host an ads.txt/app-ads.txt file

After you create an ads.txt/app-ads.txt file, have your webmaster upload the file to your root domain.

A "root domain" is defined as one level down from the public suffix list. The IAB specifications for ads.txt and app-ads.txt specifically ask for your file to be uploaded to the root domain.

Example

  • google.co.uk would be considered a root domain as "co.uk" is on the public suffix list
  • maps.google.co.uk would not be considered a root domain, because "maps" is a prefix
  • www.google.co.uk would not be considered a root domain, because "www" is a prefix.

If you have more than one root domain, an ads.txt/app-ads.txt file must be uploaded to each root domain individually.

In Ad Manager, click Admin and then Ads.txt management and confirm that an aads.txt/app-ads.txt file has been uploaded to each of your domains.

Examples of ads.txt/app-ads.txt files

Publishers working with Google products should always use google.com as the domain name, with their publisher ID. For example:

google.com, pub-0000000000000000, DIRECT, f08c47fec0942fa0
google.com, pub-0000000000000000, RESELLER, f08c47fec0942fa0

Publishers working with other non-Google products should list their SSP or exchange domain names, with their seller account IDs. For example:

greenadexchange.com, 12345, DIRECT, AEC242
blueadexchange.com, 4536, DIRECT
silverssp.com, 9675, RESELLER

What if the ads.txt/app-ads.txt file is hosted on a subdomain?

Google crawls and enforces ads.txt/app-ads.txt files placed on subdomains, where one exists, and is referenced from the ads.txt/app-ads.txt file on the root domain.

The Ad Manager ads.txt management tool does not yet show a list of crawled subdomains.

Was this helpful?
How can we improve it?