Key Takeaways

• Bloated ads.txt files make audits harder and create maintenance overhead. A file with 200 entries when only 30 are active is harder to review and more likely to hide errors.
• Stale entries don't directly hurt CPMs, but they create indirect costs. Extra entries make the file harder to parse, increase audit time, and can mask legitimate issues.
• The cleanup process has three phases: identify active partners, verify entries, and remove the rest. Each phase is straightforward but requires attention to avoid removing active entries.
• Always back up before cleaning. Save a copy of the current file before making changes. Removing an active entry is worse than keeping a stale one.
• Cleanup is an opportunity to optimize, not just trim. While you're reviewing entries, fix formatting issues, update account IDs, and correct relationship types.

---

How to Clean Up a Bloated ads.txt File

ads.txt files grow over time.

Publishers add entries when they onboard new SSPs but rarely remove them when relationships end. Reseller entries pile up as partners are added for "incremental demand" that never materializes. After a few years, a file that should have 30-50 entries has 200 or more.

A bloated ads.txt isn't an emergency. Stale entries don't directly cause verification failures for active partnerships. But they create costs: harder maintenance, longer audits, and an increased risk that legitimate errors hide in the noise.

Here's how to clean it up.

Phase 1: Identify Your Active Partners

Before removing anything, build a clear list of every SSP and reseller you actively work with.

Direct SSP Partners

Open your ad server or header bidding configuration. List every SSP that receives ad requests from your properties. For each SSP, record:

• SSP name and domain
• Your account ID
• Whether the relationship is active (generating revenue)

Active Reseller Relationships

Contact each direct SSP partner and ask which exchanges or resellers they work with on your behalf. Some SSPs automatically resell through partner exchanges. Others have specific arrangements.

For each reseller identified:

• Reseller name and domain
• Account ID on the reseller platform
• Whether the reseller generates meaningful revenue

Revenue Validation

Pull 90-day revenue reports by SSP. Any SSP generating zero revenue for three months is a candidate for removal. Any SSP generating meaningful revenue is an entry you need to keep.

Phase 2: Review Every Entry

Go through your ads.txt line by line. For each entry, classify it:

Keep: Active SSP or reseller on your confirmed partner list. Entry has correct account ID and relationship type.

Update: Active partner but the entry has an incorrect account ID, wrong relationship type, or formatting issues. Fix the entry.

Investigate: Entry is for a known SSP but you're not sure if the relationship is still active. Check with your ad ops team or the SSP before removing.

Remove: Entry is for an SSP you no longer work with, an SSP that no longer exists, or a reseller that generates no revenue and was never intentionally added.

Common Categories of Stale Entries

Defunct SSPs. SSPs that have gone out of business, been acquired, or shut down their programmatic platform. Their domains may no longer resolve.

Ended partnerships. SSPs you trialed for a few months but didn't continue with. The ads.txt entry was never removed.

Redundant resellers. Reseller entries added during initial setup that were never evaluated. Some publishers have 50+ reseller entries that generate zero revenue.

Duplicate entries. The same SSP and account listed more than once, sometimes with slightly different formatting.

Test entries. Entries added during development or testing that weren't removed before going live.

Phase 3: Execute the Cleanup

Back Up First

Save a copy of your current ads.txt. If you accidentally remove an active entry, you can restore it immediately.

Make Changes in a Single Update

Rather than removing entries one at a time over weeks, make all changes at once. This:

• Gives you a clean before/after to compare
• Makes it easy to revert if something goes wrong
• Minimizes the window where changes are partially applied

Structure the New File

While you're rewriting, organize the file for maintainability:

text
# DIRECT SSP Partners
# Last updated: 2025-MM-DD

google.com, pub-1234567890, DIRECT, f08c47fec0942fa0
openx.com, 12345, DIRECT
pubmatic.com, 12345, DIRECT, 5d62403b186f2ace

# RESELLER Partners

appnexus.com, 1234, RESELLER, f5ab79cb980f11d1
rubiconproject.com, 12345, RESELLER, 0bfd66d529a55807

Organize by relationship type. Group DIRECT entries first, then RESELLER entries. This makes the file easier to scan during future audits.

Add a date comment. Include a comment with the last update date. This helps future audits know when the file was last reviewed.

Use comments for context. Optionally add comments identifying which SSP each entry belongs to, especially for entries with numeric-only domains or ambiguous account IDs.

Deploy and Monitor

After updating, monitor your revenue for two weeks:

• Check that fill rates stay stable across all SSPs
• Verify CPMs aren't dropping on any active SSPs
• Confirm your header bidding auctions are functioning normally

If you see an unexpected drop on a specific SSP, check whether you accidentally removed their entry.

How to Prevent Future Bloat

Add an Offboarding Step

When you end an SSP relationship, add "remove ads.txt entry" to the offboarding checklist. This prevents entries from piling up.

Review During Each Onboarding

When you add a new SSP, review the full file. It only takes a minute to scan for entries that should no longer be there.

Schedule Quarterly Cleanup

Every three months, run through the active partner list and compare it against ads.txt. Remove anything that's no longer active. This prevents the file from growing out of control.

Track Changes

If you use version control (git) for your website, keep ads.txt in the repository. This gives you a full history of changes and makes it easy to see when entries were added or removed.

When Not to Remove Entries

Be cautious about removing entries in these situations:

SSP generating low but non-zero revenue. A reseller generating $50/month isn't nothing. Before removing, consider whether the revenue justifies the entry. The maintenance cost of one extra line is near zero.

Recently added entries. If an entry was added in the past month, give it time to ramp. Some SSP partnerships take weeks to reach full demand potential.

Entries you can't identify. If an entry is for a domain you don't recognize but it was intentionally added (it's in proper format with correct fields), investigate before removing. Someone on your team may have added it for a reason.

Global reseller entries. Some ads.txt managers include global reseller entries that are recommended by SSPs for their demand partnerships. These may generate indirect revenue that isn't visible in per-SSP reporting.

Frequently Asked Questions

Does a bloated ads.txt file hurt my CPMs?

Not directly. DSPs parse ads.txt to find specific entries. Extra entries don't slow down this process in a meaningful way. The cost is indirect: harder maintenance, longer audits, and a greater chance of missing legitimate errors.

How many entries should a typical ads.txt file have?

It varies widely by publisher. A publisher working with 5-10 SSPs directly might have 20-40 entries (including resellers). A publisher using a header bidding wrapper with many partners might have 50-100. Files with 200+ entries almost always have big bloat.

Should I remove entries for SSPs that exist but generate no revenue?

If the SSP is active and receives ad requests from your ad server but generates no revenue, the issue might not be the ads.txt entry. Check whether the SSP integration is configured correctly before removing the entry.