Key Takeaways

• Most DSPs pick up ads.txt changes within 24-72 hours. This is the typical crawl cycle for major DSPs.
• Some DSPs crawl daily. Others crawl less frequently. There's no industry-standard crawl frequency.
• The change is live on your server immediately but not reflected in DSP bidding until they re-crawl. The delay is entirely on the DSP caching side.
• sellers.json changes follow a similar timeline. When SSPs update sellers.json, DSPs cache the new data within 24-72 hours.
• Plan accordingly when onboarding new SSPs or making critical fixes.

---

How Long Does It Take for ads.txt Changes to Propagate?

You upload the updated ads.txt to your server. The file is live instantly.

Anyone who visits your ads.txt URL sees the new content right away.

But DSPs don't check your live file on every bid request. They use cached copies. The propagation delay is the time between your update and the DSP's next crawl of your file. That's the entire problem.

The Typical Timeline

0 hours: You upload the updated ads.txt. File's live on your server.

0-24 hours: The fastest DSPs crawl your file within their daily cycle. If your update happens just after a crawl, you wait for the next one. Bad timing can mean 24 hours right there.

24-48 hours: The majority of major DSPs have re-crawled your file and updated their cache. This is where most of your demand volume comes from.

48-72 hours: Slower DSPs and secondary platforms complete their crawl cycle.

72+ hours: A small number of DSPs or third-party verification services may take longer. But the vast majority have your updated data by this point. If it's been a week and nothing's changed, something else is wrong.

What Affects Propagation Speed

Publisher Traffic Volume

Some DSPs crawl high-traffic publishers more frequently. Makes sense.

If your domain generates heavy programmatic volume, DSPs may crawl you daily or even multiple times per day. Lower-traffic domains? Less frequent cycle. You're not as high on their priority list.

DSP-Specific Policies

Each DSP sets its own crawl frequency. Google's systems tend to crawl frequently (usually within 24 hours). Smaller DSPs may crawl less often. There's no standard you can rely on. Every buyer does their own thing.

Server Availability

If a DSP's crawler hits your server during a timeout or outage, it'll retry on its next cycle. So if your server was down Tuesday morning and that's when they tried to crawl, you're waiting until their next scheduled crawl. Make sure your ads.txt file loads quickly and reliably at all times.

Caching Layers

CDN caching, server-side caching, or ISP caching can serve stale versions of your ads.txt even after you update the file on your origin server. We've seen this trip up publishers constantly.

Check your caching configuration. Set appropriate cache headers (short TTL or no-cache for ads.txt). Your CDN shouldn't be caching this file for 24 hours.

Practical Implications

Adding a New SSP

Update ads.txt before the SSP goes live, or simultaneously. If you add the SSP to your ad server on Monday and add the ads.txt entry on Wednesday, you lose 2 days of potential verification plus the 1-3 day propagation delay.

That's nearly a week of unverified supply. Revenue gone.

Fixing an Error

After fixing an ads.txt error, expect 1-3 days before the fix propagates to DSPs. During this window, the error is still in DSP caches and still affecting your bids. You've done everything right on your end, but DSPs don't know it yet.

Removing an Entry

When you remove an entry (ending an SSP partnership), the removal propagates on the same 24-72 hour timeline. The SSP can still technically sell your inventory during this window. But DSPs will stop authorizing it once they pick up the change.

How to Verify Propagation

You can't directly check whether a specific DSP has crawled your updated file. No dashboard for that.

But you can do this:

1. Check your own file. Verify the update is live at your URL. Sounds obvious but people mess this up.
2. Monitor CPM changes. If you fixed a verification issue, watch for CPM improvement starting 1-3 days after the update.
3. Use monitoring tools. BeamFlow's scanner shows the current verification status of your ads.txt entries, which reflects what DSPs are seeing after their latest crawl.

sellers.json Propagation

The same caching dynamic applies to sellers.json. When an SSP updates your sellers.json entry (adding it, fixing a mismatch, removing confidential status), DSPs pick up the change on their next sellers.json crawl cycle.

Typically 24-72 hours. Same timeline as ads.txt.

This means the total time from "SSP confirms they fixed your entry" to "DSPs see the fix" is usually 1-3 days. Plan accordingly when estimating the timeline for revenue recovery after fixing supply chain issues. You're not going to see instant results. Be patient and give it 3-5 days before you start worrying.