How to Fix ads.txt error message on Google AdSense Account

Ads.txt is a simple, flexible, and secure method for publishers and distributors to declare who is authorized to sell their inventory, improving transparency for programmatic buyers.
Ads.txt supports transparent programmatic digital media transactions and can remove the financial incentive from selling counterfeit and misrepresented media. Similar to robots.txt, ads.txt can only be posted to a domain by a publisher’s webmaster, making it valid and authentic. As a text file, ads.txt is easy to update, making it flexible. The data required to populate the file is readily available in the OpenRTB protocol, making it simple to gather and target. And because publishers sell their inventory through a variety of sales channels, ads.txt supports the following types of supplier relationships:
  • Domain owners who sell on exchanges through their own accounts
  • Networks and sales houses who programmatically sell on behalf of domain owners
  • Content syndication partnerships where multiple authorized sellers represent the same inventory


The ads.txt project aims to prevent various types of counterfeit inventory across the ecosystem by improving transparency in the digital programmatic supply chain.
When a brand advertiser buys media programmatically, they rely on the fact that the URLs they purchase were legitimately sold by those publishers. The problem is, there is currently no way for a buyer to confirm who is responsible for selling those impressions across exchanges, and there are many different scenarios when the URL passed may not be an accurate representation of what the impression actually is or who is selling it. While every impression already includes publisher information from the OpenRTB protocol, including the page URL and Publisher.ID, there is no record or information confirming who owns each Publisher.ID, nor any way to confirm the validity of the information sent in the RTB bid request, leaving the door open to counterfeit inventory.
Counterfeit inventory – is defined here as a unit of inventory sourced from a domain, app or video that is intentionally mislabeled and offered for sale a different domain, app or video. The motivation to create counterfeit inventory comes in many forms including, to sell invalid traffic (automated non-human, or incentivised/mislead human traffic) by hiding it in real traffic, to attract higher prices by mislabeling inventory as brand inventory, to bypass content or domain blacklists, or to capture advertising spend restricted to whitelisted domains, among others.
Note that this form of “inventory fraud” in advertising is independent of how the traffic is generated. It can potentially include a mix of for example automated (non-human) bot traffic and real human user traffic. It can also exist as a small amount of authentic and valid inventory mixed with mislabeled inventory.

Blogger websites.

Step 1

Go to settings on your blogger dashboard . Look  for  monetization and create a file ads.txt under the root directory.This is done by enabling ads.txt on your blog by clicking on the YES column. A whiteboard wil l be displayed. Paste the already copied ads.txt code into the white box. Save it. Done! 

Step 2
Copy and paste the code from your adsense account to the ads.txt, **pub-xxxxx, DIRECT, f08c47fec0942fa0
**Don’t forget to replace pub-xxxxx with your own publisher ID.
Step 3
Make sure you save the file and verify that you have the file now by

For WordPressers.  

Wordpress Websites

Step 1
Download and activate this plugin if you are using WordPress. See the images below. 

Under Settings go to Ads.txt page to configure plugin settings.

Copy and paste the code from your adsense account to the ads.txt, **pub-xxxxx, DIRECT, f08c47fec0942fa0
**Don’t forget to replace pub-xxxxx with your own publisher ID.

Mind you click on the code editor. That's where you will paste and save the code.
Step 4
Save changes and verify that it works by visiting
Notice : Adsense will verify this code on your blog. You will be required to wait for  for  24 hours to reflect the latest changes.**

Powered by Blogger.