AdSense ads.txt & app-ads.txt Generator & Deduplicator

Generate a clean IAB-compliant google.com, pub-XXXXXXXXXXXXXXXX, DIRECT, f08c47fec0942fa0 file, configure OWNERDOMAIN / MANAGERDOMAIN directives, add SSP partner seats, and deduplicate messy legacy ads.txt files in one click.

1-click presets:
Accepts pub-, ca-pub-, ca-app-pub-, or bare 16 digits.
Both formats include Google TAG ID f08c47fec0942fa0.
Use DIRECT for your own AdSense / AdMob / GAM seat.
Business root domain matching your exchange sellers.json profile.
Only declare MANAGERDOMAIN if an exclusive monetization partner manages primary inventory on this site.
Optional Demand-Partner & Mediation Presets Leave blank unless you hold an approved seat ID with that exchange

Paste your current live /ads.txt or network-supplied seller lines here. We automatically strip duplicate rows, resolve conflicting google.com, pub-... entries, fix accidental ca-pub- prefixes, and preserve valid comments & variables.

Open Ads.txt Validator

Researching competitor publisher networks alongside your own setup?

Verify any pub- account across connected domains in /id (first 2 previews open; free 6-digit email OTP unlocks full tables & CSV exports). When you shortlist winning sites, unlock the $19 Starter Pack (120 non-expiring credits · 24 structured 30-section case studies) or scale with Pro ($49/mo · 400 credits).

Complete Publisher Guide to Generating & Maintaining IAB ads.txt and app-ads.txt

When Google AdSense, Google Ad Manager, or AdMob displays an "Earnings at risk — One or more of your ads.txt files doesn't contain your AdSense publisher ID" banner, programmatic demand partners pause or discount open-exchange bidding until they can verify your root authorization file. Authorized Digital Sellers (ads.txt v1.1 for websites and app-ads.txt v1.0 for mobile and connected-TV apps) is an IAB Tech Lab standard designed to stop domain spoofing and unauthorized inventory reselling.

Every valid seller declaration line uses three or four comma-separated fields on a single UTF-8 plain-text line: the canonical exchange root domain, the publisher's account identifier on that exchange, the commercial relationship (DIRECT or RESELLER), and—where assigned—the Trustworthy Accountability Group (TAG) certification authority identifier.

1. Anatomy of google.com, pub-XXXXXXXXXXXXXXXX, DIRECT, f08c47fec0942fa0

For Google AdSense, AdMob, and Ad Exchange (AdX), every field in the canonical record carries a strict programmatic meaning evaluated by demand-side platforms (DSPs) such as DV360, The Trade Desk, and Criteo:

  • Field 1 — Exchange Domain (google.com): Always lowercase google.com without protocol prefixes (never https://www.google.com or regional TLDs like google.co.uk).
  • Field 2 — Normalized Publisher Account ID (pub-16digits): Your 16-digit publisher identifier prefixed by pub-. A frequent implementation bug is copying ca-pub-1234567890123456 from HTML <script> tags or copying an AdMob ad-unit ID containing a slash or tilde (ca-app-pub-1234567890123456/9876543210). Crawler parsers expect pub- followed by 16 digits only.
  • Field 3 — Account Relationship (DIRECT vs RESELLER): Declare DIRECT exclusively when your organization directly owns and receives payouts from that Google account. Declare RESELLER only when an external ad network, MCM partner, or header-bidding wrapper monetizes ad slots through its own Google seat on your behalf.
  • Field 4 — Google TAG Certification ID (f08c47fec0942fa0): This 16-character hexadecimal string uniquely identifies Google in the TAG Registry. While technically optional in the base IAB grammar, omitting f08c47fec0942fa0 triggers validation warnings and weakens supply-path verification for strict brand-safety buyers.

2. Web ads.txt vs Mobile app-ads.txt: Deployment Rules That Trip Up Crawlers

Although web ads.txt and mobile app-ads.txt share identical internal record formatting, crawlers discover them through different trust anchors:

  • Web Publishing (https://example.com/ads.txt): Must live at the registrable root domain over HTTP/HTTPS returning status 200 OK with Content-Type: text/plain. If your content lives strictly on a subdomain such as blog.example.com or tools.example.com, you still publish the primary file at https://example.com/ads.txt and optionally add a SUBDOMAIN=blog.example.com directive if the subdomain delegates to its own seller list.
  • Mobile & CTV Apps (https://developerdomain.com/app-ads.txt): Google Play and Apple App Store crawlers extract the Developer Website URL from your public store listing, translate subdomains according to the IAB registrable-domain rule, and fetch /app-ads.txt from that root host. Hosting your store listing on a free third-party subpath (such as Notion, GitHub repo subpaths, or Linktree) prevents root /app-ads.txt verification—always use a custom domain you control.
  • Redirects, Firewalls & Caching: IAB crawlers accept at most one cross-domain redirect outside the original root domain before rejecting the file, whereas multiple redirects within the same root domain (such as http://example.com/ads.txt → https://www.example.com/ads.txt) are permitted. Verify that CDN bot-fight modes, geographic IP blocks, or aggressive WAF rules do not return HTML challenge pages (text/html) to Google-adstxt user agents.

3. Understanding OWNERDOMAIN and MANAGERDOMAIN in ads.txt v1.1

Starting with IAB Tech Lab ads.txt version 1.1, two root-level variable directives closed a long-standing ambiguity between inventory ownership and outsourced monetization management:

OWNERDOMAIN declares the corporate or portfolio root domain of the legal entity that owns the website or app. For example, if a media operator runs twelve vertical calculator sites under one holding company, setting the same OWNERDOMAIN across all twelve sites lets DSPs match every site cleanly against the business domain listed in Google's sellers.json feed. Only one OWNERDOMAIN line should appear per file.

MANAGERDOMAIN identifies the corporate domain of an exclusive outsourced ad-operations partner (such as Mediavine, Raptive, Ezoic, or Freestar) managing monetization for that property. Self-managed AdSense publishers who run their own ad units should leave MANAGERDOMAIN empty; populating it with your own domain duplicates OWNERDOMAIN without adding supply-path clarity.

4. Why Deduplicating Multi-Network ads.txt Files Protects Auction Health

Publishers testing header bidding, mediation waterfalls, or seasonal SSP partners routinely accumulate bloated 2,000-line ads.txt files pasted together from onboarding emails. Over time, three silent defects creep in:

  1. Conflicting DIRECT and RESELLER rows for the same seat: Listing the exact same exchange domain and seller account ID twice—once as DIRECT and once as RESELLER—creates a supply-chain contradiction when DSPs cross-check OpenRTB schain nodes against exchange sellers.json files.
  2. Stale mediation resellers after offboarding: Leaving hundreds of RESELLER seats in your root file months after terminating a mediation contract keeps those intermediaries legally authorized to represent your domain in programmatic auctions.
  3. Copy-paste encoding corruption: Non-breaking spaces, smart quotes, HTML tags, or unescaped email signatures pasted without a leading # comment marker break line parsers and trigger syntax warnings in our Ads.txt Validator.

Using the Existing ads.txt Merge & Deduplicate box above resolves all three issues deterministically in your browser: your primary google.com declaration and chosen partner presets act as the source of truth, exact duplicates are stripped, conflicting DIRECT/RESELLER duplicates on the same account ID are collapsed, and unparseable lines are quarantined into an explicit audit report rather than silently corrupting your production file.

5. Connecting Seller Hygiene to Reverse Competitive Intelligence

Because ads.txt is public by design, disciplined publishers use the exact same identifiers for competitive research. Once you normalize a competitor's pub- ID, run a Reverse AdSense Lookup or open PubSpy Publisher Domains (/id) to see other synced websites authorized under that same DIRECT Google account, compare domain registration dates, and feed monthly visit estimates into our AdSense Revenue & Valuation Calculator.

Keep clear evidence boundaries in mind: public tools read observable seller declarations and domain registry records only. Missing entries in a crawled dataset mean "not yet indexed," never proof of zero revenue, and passing technical syntax checks serves as operational guidance for publishers, not a Google approval guarantee.

Ads.txt & App-Ads.txt Generator FAQ

What is the exact Google AdSense ads.txt line format?

The standard four-field declaration is google.com, pub-0000000000000000, DIRECT, f08c47fec0942fa0, replacing the sixteen zeros with your 16-digit publisher number and omitting any ca- prefix.

What is the difference between ads.txt and app-ads.txt?

Both follow the same comma-separated IAB seller syntax. Websites serve /ads.txt at the root of the content domain, whereas mobile apps serve /app-ads.txt at the root of the developer website URL linked on Google Play and the Apple App Store.

Should my Google AdSense line use DIRECT or RESELLER?

Use DIRECT when you directly own and control the AdSense, AdMob, or Ad Manager account. Use RESELLER only when listing a third-party network's account ID that sells inventory on your behalf.

How long does Google take to verify a newly uploaded ads.txt file?

Once https://yourdomain.com/ads.txt returns HTTP 200 over plain text and your pages receive ad requests, Google's crawler typically re-fetches within 24 to 72 hours, though low-traffic properties or DNS changes can take up to several days to clear dashboard alerts.

Does publishing a valid ads.txt file guarantee AdSense approval?

No. A valid ads.txt file verifies authorized seller seats for programmatic buyers, whereas site approval depends on Google's policy and content review. All checks on PubSpy are publisher guidance, not a Google approval guarantee.