Free Ads.txt Validator for AdSense Publishers

Paste your /ads.txt file to check IAB seller syntax, verify 16-digit Google AdSense pub- IDs and TAG ID f08c47fec0942fa0, spot duplicate seller lines, and link DIRECT publisher IDs straight to reverse lookup.

Paste ads.txt lines to validate

Syntax parsing checks IAB Tech Lab field rules, DIRECT versus RESELLER declarations, and Google AdSense formatting. It is technical guidance for publishers, not a Google approval guarantee.

Check the root domain registry record

AdSense crawlers fetch ads.txt from the registrable root domain over HTTP/HTTPS. This lookup reads the public registration record only - age, registrar, status flags and expiry - as guidance rather than a Google approval guarantee. How PubSpy handles data.

What this ads.txt validator checks

🧾

Google AdSense ID & TAG format

Catches accidental ca-pub- prefixes, truncated publisher numbers that miss the 16-digit requirement, and missing f08c47fec0942fa0 TAG authority IDs.

🔗

DIRECT vs RESELLER hygiene

Flags non-standard relationship labels such as PARTNER or lowercase typos, and isolates DIRECT Google IDs so you can verify domain portfolios in reverse lookup.

🧹

Duplicates & IAB variables

Highlights repeated seller tuples added by multiple ad networks and checks CONTACT, OWNERDOMAIN, MANAGERDOMAIN and SUBDOMAIN declarations.

Common ads.txt mistakes that trigger AdSense "Earnings at risk"

Google's crawler expects a plain UTF-8 text file reachable at the root domain (https://example.com/ads.txt) returning HTTP 200. Serving an HTML error template with a 200 status, redirecting across unrelated domains, or blocking Google-adstxt in firewall rules prevents AdSense from verifying your seller record even when every comma is right.

Inside the file itself, the three errors we see most often in publisher audits are copying ca-pub- from an ad unit snippet instead of pub-, pasting smart quotes or invisible zero-width spaces from chat apps, and labeling third-party mediation networks as DIRECT when you do not own the underlying exchange seat.

Read our domain & publisher intelligence guide (中文实战指南) for how researchers interpret DIRECT versus RESELLER lines across multi-site portfolios.

Frequently asked questions

What should a Google AdSense line look like in ads.txt?

A standard Google AdSense seller line uses four comma-separated fields: google.com, pub-0000000000000000, DIRECT, f08c47fec0942fa0, replacing the zeros with your 16-digit publisher number (without ca-).

What is f08c47fec0942fa0 in an ads.txt file?

f08c47fec0942fa0 is Google's Trustworthy Accountability Group (TAG) certification authority ID. Including it as the fourth field helps programmatic buyers confirm the exchange identity.

When should a line use DIRECT versus RESELLER?

Use DIRECT only when you directly hold and control the account listed in field two. Use RESELLER when an ad management network or SSP sells an impression slot on your behalf.

Does passing ads.txt syntax validation mean Google approved my site?

No. Syntax validation confirms your file follows the IAB specification. AdSense site approval and ad serving depend on Google's policy review - this page is guidance, not a Google approval guarantee.

Related AdSense tools

Free AdSense Approval Checker

Check registration age, registrar, status flags and template-level content readiness before submitting a domain.

AdSense Block Checker

Debug blank ad slots step by step: browser blockers, consent banners, script placement, and ads.txt propagation delays.

Reverse AdSense Publisher Lookup

Search cached AdSense publisher IDs and see the other domains publicly declaring the same seller account.

Inspect live pages alongside ads.txt

Install the free PubSpy Chrome extension to inspect live ads.txt relationships, page structure, and 30-section website case studies. Eligible new accounts start with 100 free credits; see pricing for recurring plans and packs.

Install the free extension Claim starter credits