ads.txt and sellers.json

Stop losing bids to a missing line in a text file

Buyers skip supply paths your ads.txt doesn't authorize. We check every domain you monetize every four hours, tell you exactly which lines are missing, and keep our sellers.json consistent with them.

Illustration of an ads.txt checklist with every line checked, a globe and a repeating clock

Trusted by 100+ premium publishers, including

  • ynet
  • mako
  • N12
  • Israel Hayom
  • 24
  • TheMarker
  • Maariv
  • ONE

Direct integrations with the largest demand partners

  • Magnite
  • Microsoft
  • OpenX
  • Outbrain
  • Taboola
  • Criteo
  • Teads
  • TripleLift
  • Equativ
  • RTB House
  • Sovrn
  • OneTag
  • 33Across
  • and more

Why ads.txt errors are so expensive

When an ads.txt line is missing or wrong, nothing breaks on your site. Ads still show. Some buyers just stop bidding through that path, and the only symptom is a demand partner whose revenue drifts down over weeks.

  • Checked every four hours

    Each domain's ads.txt is fetched from the same place buyers' crawlers read it.

  • Lines ready to copy

    Missing lines are listed exactly, so there is no diffing a long file by hand.

  • Weekly summary

    A weekly email makes sure a missing line on a second or third site doesn't go unnoticed.

  • sellers.json in sync

    Our sellers.json is rebuilt from publisher records and deployed automatically every six hours.

A stylized ads.txt health dashboard with summary cards, a domains table and a missing-lines panel

A health status for every domain

For every domain we monetize, the ads.txt check compares your live file with the lines your setup needs, including the Valuad line and the lines for each demand partner running on that domain.

  • Status per domain: implemented, has issues, missing or not checked yet
  • Recheck on demand after you update the file
  • Your own partners' lines are left alone if you run your own demand seats
An ads.txt file and a sellers.json file linked by arrows that keep them in sync

Both sides of the check agree

Buyers compare your ads.txt with the seller's sellers.json and the supply chain in the bid request. The paths they keep are the ones where all three agree.

  • Generated lines are deduplicated and validated, so each ends in exactly DIRECT or RESELLER
  • OWNERDOMAIN and MANAGERDOMAIN set as defined in ads.txt 1.1
  • Exclusive deals respected: a competitor's lines are left out of your block

How it works

  1. 1

    We generate your lines

    Each site gets its ads.txt block built from its own configuration, not a generic list.

  2. 2

    We check them continuously

    Every domain is checked every four hours, with a weekly summary by email.

  3. 3

    You fix what's flagged

    Missing lines are listed ready to copy, and a recheck confirms the fix.

Talk to an expert

Valuad have made the unexpected. They have achieved to make us believe in miracles. After doubling our ad revenues once, and then once again, and then higher and then keep on improving - we started to believe that nothing is impossible, and all it takes is some pros with extra drive. We are now addicted to these guys' work, and the numbers are fantastic.
Gidon UzanDeputy CEO at Maariv Group

Questions publishers ask

Where do I add the lines?

In the ads.txt file at the root of each domain you monetize, for example yourdomain.com/ads.txt.

What about subdomains?

Crawlers start from the root domain, and its file covers subdomains too. A subdomain can have its own file, but crawlers only read it when the root file points to it with a subdomain line.

Why does sellers.json matter to me?

Buyers use it to check who an account in your ads.txt belongs to. If the two disagree, the path looks suspicious and gets lower priority in supply path optimization.

Talk to the team behind Israel's largest publishers

Tell us about your sites and your ad server setup, and we'll show you where the revenue is.