Skip to content
Lizely

Ads Txt Generator

Build a standards-shaped ads.txt file from explicit authorized-seller details, with strict field validation, duplicate protection and a ready download.

Privacy: your files never leave your device. All processing happens locally in your browser.

How to use

  1. 1.Copy the advertising system domain, publisher account ID, relationship and optional authority ID from the platform's own instructions.
  2. 2.Add each authorized seller, review every generated line and remove duplicates or obsolete entries.
  3. 3.Download ads.txt, publish it at the root domain as /ads.txt and compare the public file with your verified account records.

About Ads Txt Generator

Ads.txt Generator creates an Authorized Digital Sellers file from seller information supplied by your advertising platforms. Each entry contains the advertising system domain, publisher account identifier, DIRECT or RESELLER relationship, and an optional certification authority identifier. The finished text can be copied or downloaded without sending account details to the server.

The first field is the canonical domain of the advertising system where buyers connect. It is not necessarily your own website domain. Enter a bare domain such as google.com, without https://, a path, port, username or password. The generator lowercases and validates the domain instead of silently extracting a host from a pasted URL.

The second field is the seller or publisher account identifier assigned by that advertising system. Its exact form depends on the platform. For Google seller accounts, official guidance uses a pub- prefix followed by the account digits. Other exchanges use different identifiers, so copy the value from the platform's own instructions rather than inventing or converting it.

DIRECT means the site owner directly controls the account in the seller record and has a direct business relationship with the advertising system. RESELLER means another entity controls the listed account and is authorized to resell the inventory. Selecting the wrong relationship can make the declaration inaccurate even when every character is formatted correctly.

The fourth field is optional and identifies the advertising system within a certification authority. Google's published example includes f08c47fec0942fa0. Do not assume that identifier applies to another exchange. Leave the field blank unless the advertising platform provides the exact value for its seller record.

Every seller becomes one comma-separated line. The generator trims surrounding input, rejects commas or whitespace inside fields, normalizes domain case, prevents exact duplicate rows and ends the file with a newline. It supports up to 200 records so a mistaken oversized paste cannot produce an unwieldy browser result.

The page validates syntax, not authorization. It cannot sign into an ad account, confirm that a publisher ID belongs to you, prove that a reseller is permitted, or discover every platform that sells your inventory. A syntactically valid but unauthorized or incomplete file can still harm monetization. Review the output against current instructions from each partner.

Host the downloaded file as /ads.txt on the root domain that owns the inventory. For example, the expected public location for example.com is https://example.com/ads.txt. Publishing it only under /files/ads.txt, inside an HTML page or behind authentication does not create the same crawler-visible root resource.

If several advertising systems are authorized, add one verified record for each account. Do not remove existing valid sellers merely to add a new one. Keep a backup of the prior file, compare the change and check the public URL as plain text after deployment. Account or network changes may require future updates.

The Google example used in testing is google.com, pub-0000000000000000, DIRECT, f08c47fec0942fa0. The zeros are a placeholder, not a usable publisher account. Replace them with your exact account identifier. The tool deliberately does not prefill a real user ID or make a network choice for you.

Eight standards-aligned fixtures cover three- and four-field rows, DIRECT and RESELLER, domain case normalization, a trailing root dot, subdomains, punycode domains and common identifier punctuation. Boundary tests reject schemes, commas, unsupported relationships and duplicate seller declarations.

Use the tool by entering one platform-provided record, adding it to the visible list and repeating for every authorized seller. Review the complete text, copy or download ads.txt, deploy it to the root, then open the public URL and compare each line with the source instructions. Formatting assistance cannot replace account-level verification.

Methodology & sources

Each seller row is validated as three required comma-free tokens plus one optional certification token. Domains are normalized as bare lowercase DNS-style hosts, relationships are restricted to DIRECT or RESELLER, duplicate formatted rows are rejected, and output is newline terminated.

Frequently asked questions

Related tools

SEO & Webmaster guides

View all