Key Takeaways

• Review your ads.txt file at least monthly. The programmatic ecosystem changes constantly. SSPs update sellers.json, partners restructure accounts, and new relationships start. Monthly reviews catch drift before it costs you bids.
• Certain events should trigger an immediate update. Adding or removing an SSP, changing monetization partners, noticing revenue drops, or hearing about an SSP merger all require same-day edits.
• DSPs re-crawl ads.txt every 24-72 hours. After you make a change, most major DSPs will see it within a few days. Some take up to a week. Trust scores damaged by errors may take 2-4 weeks to recover.
• SSPs change their sellers.json without notifying you. Your ads.txt was correct when you set it up. But if the SSP reclassified your account or changed domain fields, your entries are now wrong. You had no idea.
• In December 2025 alone, publishers added 456,994 new ads.txt lines and removed 398,928. The ecosystem moves fast. Static files rot.

---

How Often Should You Update ads.txt?

Most publishers create their ads.txt file once and forget about it.

They set up their SSP entries when they launch, maybe add a partner here and there, and then the file sits untouched for months.

Sometimes years.

Meanwhile, the programmatic ecosystem moves under them.

SSPs rebrand, merge, or shut down. Account IDs get reassigned. Monetization partners rotate. sellers.json files get updated without notification.

And every change that isn't reflected in the publisher's ads.txt is a bid that silently disappears.

DataBeat's December 2025 SSP sellers report tracked the scale of this churn: 456,994 new ads.txt lines were added across the ecosystem, while 398,928 were removed.

In a single month.

If your file hasn't changed in six months, it's statistically certain that something is wrong.

This guide covers the right update cadence, the events that should trigger immediate changes, and how to build a maintenance workflow that prevents drift.

The Minimum: Monthly Reviews

At a bare minimum, review your ads.txt file once a month.

Open the file, compare it against your current SSP relationships, and verify that every line still represents an active, correctly configured partnership.

Fifteen minutes.

That's all it takes.

A monthly review catches:

• Partners you added but forgot to include in ads.txt. Header bidding adapters get configured, traffic flows, but the ads.txt line never gets added. That partner is running at reduced demand because DSPs can't verify them.
• Partners you dropped but didn't remove from ads.txt. Old entries for SSPs you no longer work with are dead weight. They can't generate revenue (no active integration), but they create noise in your file and give fraudsters potential cover.
• Account ID changes. SSPs occasionally reassign publisher IDs, especially after platform migrations or acquisitions. Your old ID no longer maps to your account. And nobody told you.
• sellers.json drift. SSPs update their sellers.json independently. An entry that verified perfectly last month might fail cross-verification today because the SSP changed the seller_type or domain field for your account.

A monthly review takes 15-30 minutes for a publisher with 10-30 SSP relationships.

The cost of not doing it is silent revenue loss that compounds every week.

Quarterly Deep Audits

Beyond monthly reviews, run a thorough audit every quarter.

This goes deeper than just comparing entries:

Cross-reference every line against sellers.json. Don't just check that your SSP entries exist. Verify that the account ID, relationship type, and domain match what the SSP reports in their sellers.json file.

24% of ads.txt entries fail this cross-verification. A quarterly check catches mismatches before they compound into months of lost bids.

Review your entry count. Compare your file size against previous quarters. A file that keeps growing without corresponding new partnerships is accumulating dead entries. A file that hasn't changed at all when you know you've added partners means someone forgot to update it.

Check for duplicate entries. Over time, different team members or partners may add the same SSP line in slightly different formats. Duplicates aren't harmful per se, but they bloat the file and make maintenance harder.

Benchmark against industry peers. How many SSP relationships does a comparable publisher maintain? If your file has 200 entries and peers have 30, your file is probably carrying dead weight.

That's a red flag.

Events That Require Immediate Updates

Some changes can't wait for the next scheduled review.

These events should trigger a same-day ads.txt update:

Adding a New SSP or Ad Network

When you sign a new demand partner, add their ads.txt lines the same day you configure the ad server integration. Not next week. Not when you "get around to it."

Every day without the ads.txt entry is a day that DSPs reject bids from that partner on your inventory.

Make the ads.txt update part of the same operational ticket as the ad server setup. One doesn't ship without the other.

Period.

Removing or Pausing an SSP

When you stop working with a partner, remove their entries immediately. Stale entries for inactive SSPs serve no purpose and create maintenance noise. In rare cases, they can be exploited by domain spoofing operations that use old, inactive entries as cover.

Switching Monetization Partners

If you move from one managed service to another (for example, switching header bidding platforms), the changeover typically involves multiple SSP relationship changes. Your old partner's RESELLER entries need to come out. Your new partner's entries need to go in.

The ads.txt update should happen simultaneously with the ad server swap.

Not after. Simultaneously.

SSP Merger or Acquisition

When an SSP you work with gets acquired, watch for changes to exchange domains, account IDs, and sellers.json entries. The acquiring company may migrate accounts to new IDs, change the exchange domain, or restructure the sellers.json.

Keep an eye on industry news and verify your entries after any major M&A event.

Unexplained Revenue Drops

When CPMs or fill rates drop without an obvious cause (not seasonality, not traffic changes), check your ads.txt first. A broken entry, a missing partner, or a sellers.json mismatch can silently cut demand.

This is often the fastest diagnostic step and the most commonly overlooked one.

Turns out, the answer to "why did my revenue drop?" is sometimes just a text file.

SSP Notifies You of Changes

Some SSPs send alerts when they update their systems. If an SSP emails you about a platform migration, new account format, or sellers.json update, review and update your ads.txt entries for that SSP immediately.

How Quickly Do Changes Take Effect?

After you update your ads.txt file, DSPs won't see the change instantly.

Here's the typical timeline:

24 hours: Google's crawlers typically re-fetch ads.txt within 24 hours. Google is one of the fastest.

24-72 hours: Most major DSPs (The Trade Desk, DV360, MediaMath) re-crawl within this window. After 72 hours, the majority of programmatic demand should reflect your changes.

Up to 7 days: Smaller DSPs and some specialized buyers may take longer. If you're testing a new partner, give it a full week before evaluating bid performance.

2-4 weeks for trust recovery: If your file had errors for an extended period, some DSPs may have lowered your supply chain trust score. Fixing the errors is step one, but the trust score may take weeks to recover fully.

DSPs don't just check current state. They factor in historical reliability.

And that's the real cost of procrastination. An error that sits in your file for three months causes three months of lost bids, and then potentially another month of trust score recovery after you fix it.

Four months of damage from one mistake.

Building a Maintenance Workflow

For publishers managing ads.txt seriously, establish a repeatable workflow:

Assign ownership. One person or team owns the ads.txt file. Not "whoever remembers." A named owner who's accountable for accuracy.

Typically this sits with ad operations.

Tie updates to partner changes. Every SSP onboarding or offboarding process should include an ads.txt update step. Build it into your operational checklist. No partner goes live without their ads.txt lines. No partner gets removed without their lines being cleaned up.

Use version control. Keep a changelog of what was added, removed, and when. This doesn't need to be Git (though that works great). Even a simple spreadsheet that logs changes by date, partner, and reason is valuable.

When something breaks, you can trace back to what changed.

Automate monitoring. Manual monthly reviews are the minimum. Automated monitoring that alerts you to changes, sellers.json mismatches, or accessibility issues is better.

Tools like BeamFlow can continuously monitor your ads.txt against the SSP ecosystem and flag problems the day they appear, not the day you happen to check.

Test after every change. After updating your file, verify it's accessible at yourdomain.com/ads.txt, returns the correct content, and the new entries parse correctly. A broken upload that serves a 500 error is worse than the old file.

Always verify.

What Happens When You Don't Update

The costs of a stale ads.txt file are cumulative and invisible:

Month 1-2: A few entries drift. One SSP updated their sellers.json. One partner you dropped is still listed. The impact is small, maybe 2-3% of potential demand affected.

Month 3-6: More entries accumulate errors. You added two new partners but never updated ads.txt. Those partners show "poor performance" in your ad server because DSPs are rejecting their bids.

You blame the partner. The real problem is your file.

Month 6-12: Your file is out of sync. Stale entries outnumber active ones. DSPs that evaluate supply chain quality give you a lower trust score. The impact spreads beyond individual broken lines to your overall inventory reputation.

Year 2+: Your ads.txt is technical debt. Nobody wants to touch it because nobody knows which lines are real and which are legacy.

Any audit becomes a multi-day project instead of a 30-minute review.

The publishers who treat ads.txt as a living document, updated with every partner change and reviewed monthly, avoid this decay entirely. The ones who set it and forget it slowly leak revenue they never see.

And that leaked revenue? It doesn't come back on its own.

Frequently Asked Questions

Can I automate ads.txt updates?

Some monetization platforms and ads.txt management services offer automated updates. These work by redirecting your ads.txt path to a dynamically generated file that the service maintains. This can work well, but verify that the service keeps entries accurate and that DSP crawlers can follow the redirect. You're outsourcing accuracy, so trust the provider but verify the output.

Do SSPs notify publishers when sellers.json changes?

Rarely. Most SSPs update their sellers.json without direct notification to publishers. Some send platform-wide announcements, but individual account-level changes (like reclassifying your account type) typically happen silently. This is why monitoring is so important. You can't fix what you don't know about.

What if I update too frequently?

There's no penalty for frequent updates. DSPs re-crawl on their own schedule regardless of how often you change the file. Updating daily is unnecessary for most publishers, but it causes no harm. The risk is only in making incorrect changes, not in making changes too often.

Should I keep a backup of my previous ads.txt?

Yes. Before any update, save a copy of the current file with a date stamp. If a change causes unexpected issues (a partner's bids dropping because you accidentally removed their line), you can quickly revert.

Version control is cheap insurance. And you'll thank yourself the first time something goes wrong.

How do I know if my ads.txt has drifted?

The clearest signal is sellers.json verification failures. If entries that used to verify now fail, something changed on the SSP side. Revenue drops for specific SSP channels can also indicate drift. But the most reliable method is automated scanning that compares your ads.txt against current sellers.json data on an ongoing basis.