If you’ve been running a blog for a while and someone in a Facebook group or a Discord server told you to “just add an ads.txt file,” you probably nodded along and then quietly Googled it later. That’s normal. Nobody explains this stuff clearly when you’re starting out, and most guides jump straight into code snippets before telling you what the file is even for.
So let’s back up and do this properly.
The short version
Ads.txt is a plain text file. Not a plugin, not a piece of software, not something complicated sitting in your database. It’s a single .txt file that lives on your website and lists out every company you’ve given permission to sell ad space on your pages.
That’s it. That’s the whole concept.
The name itself is a clue: “ads.txt” stands for “Authorized Digital Sellers.” It’s basically a public declaration that says, “these are the only companies allowed to sell ads on my site — anyone else claiming to sell my inventory is lying.”
Why does this even need to exist?
Here’s the part most articles skip over, and it’s honestly the more interesting half of the story.
Before ads.txt existed, there was a pretty widespread problem in the ad industry called domain spoofing. Basically, shady middlemen would pretend to sell ad space on well-known, high-traffic websites — sites they had absolutely nothing to do with. An advertiser would think they were buying a banner ad on, say, a popular news site, pay a premium price for it, and the ad would actually run somewhere completely different, or not at all. The advertiser lost money, the real publisher never saw a cent, and everyone in between quietly took a cut.
It’s a scam that worked specifically because there was no easy way for an advertiser or an ad exchange to check “wait, is this seller actually authorized to sell space on this website?”
Ads.txt fixed that by giving publishers a simple way to publicly say who’s allowed to sell for them. Ad exchanges started checking this file automatically. If a seller shows up trying to sell inventory for a domain, but that domain’s ads.txt file doesn’t list them, the exchange knows something’s off and can refuse the bid.
It’s a small file solving a fairly big trust problem.
So what happens if you skip it?
This is the question people actually care about, so let’s be direct.
Your site won’t crash. Your pages will load exactly the same. Nobody’s going to send you an error message saying you broke something. In that sense, ads.txt is technically optional — no ad network is going to block your website from functioning just because the file is missing.
But here’s the catch: a growing number of ad exchanges and demand-side platforms simply won’t bid on your ad inventory if they can’t verify it against an ads.txt file. Not because they’re being strict for the sake of it, but because unverified inventory is exactly the kind of thing the whole system was built to filter out. To them, no ads.txt file looks a lot like the same red flag as an unauthorized reseller.
What that actually looks like on your end is quiet and easy to miss. You don’t get an alert saying “you’re losing money.” You just start noticing your fill rates are a little lower than they should be, or your CPMs (the amount advertisers pay per thousand impressions) are sitting below what similar sites in your niche are earning. It’s a slow leak, not a dramatic failure, which is exactly why so many bloggers never realize it’s happening to them.
If you’re running Google AdSense specifically, it’s a bit more visible. AdSense will actually flag your account with an “Earnings at risk” warning if your ads.txt setup isn’t right, which is Google’s way of saying “fix this before it starts costing you.”
What’s actually inside the file
Once you open an actual ads.txt file, it looks almost anticlimactic. Each line follows this basic pattern:
google.com, pub-0000000000000000, DIRECT, f08c47fec0942fa0
Breaking that down piece by piece:
The domain — this is the ad network’s domain, not yours. So if you’re working with Google AdSense, the first field is always google.com, regardless of what your own website’s domain is.
Your publisher ID — this is the unique account ID the ad network gave you. For AdSense, it always starts with “pub-” followed by a string of numbers. You’ll find it inside your AdSense account under Account, then Settings, then Account information. Just a heads-up: your AdSense ad code often shows this same ID with “ca-” stuck in front of it, like ca-pub-123456789. For ads.txt, you drop the “ca-” and just use the pub- part.
The relationship type — this is either DIRECT or RESELLER, and it matters more than people think.
The certification authority ID — this last field is optional. It’s issued by an independent verification body and basically adds an extra layer of trust to the entry, confirming the network in question really is who it claims to be. Not every network provides one, and it’s fine to leave it blank if yours doesn’t.
DIRECT vs RESELLER, explained without the jargon
This trips a lot of people up the first time they see it, so here’s the plain version.
DIRECT means you have a direct account with that ad network yourself. You signed up, you own the account, there’s no third party sitting between you and the network. Most people running AdSense on their own blog will use DIRECT.
RESELLER means someone else — usually another ad network or an agency — has permission to sell your inventory on your behalf. You didn’t set up that account yourself; you authorized a partner to handle it for you.
You can absolutely have both types in the same file, and most established sites do. Maybe you sell some space yourself through AdSense (DIRECT), while also letting another network resell additional space for you (RESELLER). They live in the file together without any conflict.
Where the file actually needs to sit
This is the single most common mistake people make, so it deserves its own section.
Your ads.txt file has to be placed at the root of your domain. Not in a subfolder, not inside your WordPress uploads directory, not tucked away somewhere convenient. It needs to be reachable at exactly this address:
https://yourwebsite.com/ads.txt
If your file is sitting at yourwebsite.com/blog/ads.txt or yourwebsite.com/files/ads.txt, ad crawlers simply won’t find it. They only check that one exact root-level path, every time, no exceptions.
If you’re on WordPress, this usually means uploading the file directly through FTP or your hosting provider’s file manager, straight into the main installation folder — not inside wp-content, not inside wp-admin. Some hosting dashboards and plugins can handle this for you, but it’s worth double-checking where the file actually landed afterward.
How to check if yours is working
Once it’s uploaded, verifying it is refreshingly simple. Just type your domain followed by /ads.txt straight into your browser’s address bar. You should see plain text on the screen — the actual lines of your file — not a 404 error and not a file download prompt.
If you’re using AdSense, there’s a second check worth doing. Head into your AdSense account, go to Sites, and look at the status next to your domain. Google will show you one of a few statuses there — authorized, not found, or a specific error — which tells you exactly where things stand from Google’s side, separately from what you see in your own browser.
Building the file without losing your mind over syntax
Honestly, the syntax itself is where most mistakes creep in. A misplaced comma, a typo in the network’s domain, or a leftover “ca-” prefix on your publisher ID, and the whole line becomes invalid without any obvious warning telling you so.
Rather than hand-typing this from scratch and hoping you got the formatting right, it’s a lot less error-prone to use something built specifically for this — SmartBalak’s free Ads.txt Generator lets you pick your network, drop in your publisher ID and relationship type, and it builds the correctly formatted line for you automatically. You can add entries for multiple networks in the same session, then copy or download the finished file and upload it straight to your site. No account needed, nothing saved on a server anywhere — the whole thing happens right in your browser.
The bottom line
Ads.txt isn’t complicated once you understand what problem it’s actually solving. It’s not a technical hoop ad networks make you jump through for no reason — it’s a trust signal that protects your ad revenue from being quietly siphoned off by sellers you never authorized in the first place.
If you’ve got a blog with any kind of advertising on it, even a small one, this is one of those five-minute jobs that’s genuinely worth doing properly. Skipping it doesn’t break anything visibly, but it does leave money on the table you’ll probably never notice going missing — until you compare notes with someone running a similar site who took the time to set theirs up right.