The free Ads Txt Generator is an ads.txt file generator that converts an advertising system’s bare domain, an assigned publisher account ID, and a DIRECT or RESELLER relationship into comma-separated seller records for a downloaded ads.txt file. It is not a general ad-copy or slogan writer: the task is to create an Authorized Digital Sellers declaration from information supplied by each advertising platform. Each record contains three required comma-free values—the canonical advertising system domain, the publisher or seller account identifier assigned by that system, and the relationship—with an optional fourth field for a certification authority identifier. The visible list becomes plain text with one record per line and a trailing newline. The generator lowercases and validates the domain instead of extracting a host from a pasted URL, trims surrounding input, rejects commas or internal whitespace, and prevents exact duplicate rows. It supports as many as 200 records. The finished text can be copied or downloaded without sending account details to the server. Those controls create a reliable drafting checkpoint, not proof of business authority: the page cannot log in to an ad account, discover every seller, confirm that a publisher ID is yours, or verify that a reseller is permitted. Current platform instructions and your verified account records remain the source of truth.
What the free generator produces
The Ads Txt Generator turns explicit seller information into a reviewable list rather than discovering sellers automatically. For every authorized advertising system, enter one record containing the details exactly as that platform instructs. The tool validates the structure of each row and combines the accepted rows into a standards-shaped file that ends with a newline.
This is an input-and-validation tool, not an account-management tool. It does not choose an advertising system, infer your publisher ID, or determine which companies are authorized to resell your inventory. That division keeps the result auditable: every domain, identifier, relationship, and optional authority value must come from a source you can verify.
| Record part | What to enter | Why it matters |
|---|---|---|
| Advertising system domain | A bare, lowercase domain such as google.com | This identifies the advertising system where buyers connect, not necessarily your own website domain. |
| Publisher or seller account ID | The exact identifier assigned by that advertising system | Identifier formats vary by platform, so the value must be copied rather than reconstructed. |
| Relationship | DIRECT or RESELLER | The selection describes who controls the listed seller account and must match the business relationship. |
| Certification authority ID | An exact platform-provided value, or a blank field | This optional value is exchange-specific and should not be copied from another advertising system. |
Gather values from platform instructions
Start with the advertising platform’s current setup instructions or verified account records. Those sources should identify the canonical advertising system domain, the publisher or seller account identifier, the appropriate relationship, and any required certification authority ID. Avoid inventing a missing value because a blank field is safer and more accurate than an unsupported guess.
The second field is not universal. For Google seller accounts, official guidance uses a pub- prefix followed by the account digits. Other exchanges can use different identifiers, punctuation, or formats. The tool’s Google testing fixture uses pub-0000000000000000, but those zeros are placeholders, not a usable publisher account. Replace them with the exact identifier assigned to your seller account. Likewise, f08c47fec0942fa0 is a certification authority value from Google’s published example; it does not automatically apply to another exchange. Leave the fourth field blank unless the relevant platform provides its exact value.
If your source is Google AdSense, the dedicated guide to retrieve and validate the platform-provided AdSense record can help verify the identifier before you add it. For broader specification context, the record structure follows the framework documented in the IAB Tech Lab ads.txt 1.1 specification.
Meet the input rules
Enter the advertising system domain as a bare hostname without https://, a path, port, username, password, or other URL components. The generator validates a pasted domain value instead of silently extracting a host from a pasted URL. It also normalizes domain case to lowercase. Do not pad individual fields with spaces: surrounding whitespace is removed, but whitespace inside a field is rejected because commas and internal spaces are not valid record syntax.
Relationship accuracy matters just as much as punctuation. DIRECT means your site directly controls the listed seller account and has a direct business relationship with the advertising system. RESELLER means another entity controls the listed account and is authorized to resell your advertising inventory. Selecting a relationship merely because its letters fit the accepted format can make the entire declaration inaccurate.
| Account situation | Correct selection | Meaning |
|---|---|---|
| Your business controls the seller account and contracts directly with the advertising system | DIRECT | The listed publisher or seller account is directly controlled by the inventory owner. |
| Another authorized entity controls the listed seller account | RESELLER | The entity is authorized to resell advertising inventory through that account. |
| Ownership or authorization is unclear | Verify before selecting | Neither relationship should be used until the account structure is confirmed. |
The generator limits the file to 200 records and blocks unsupported relationships, commas, schemes, and exact duplicate formatted rows. These syntax checks make review easier, but they do not prove that a record is genuine or complete. A file can be correctly formatted while still omitting an authorized platform or declaring a seller without proper authorization.
Build and review the file
- Copy the advertising system domain, publisher account ID, relationship, and optional authority ID from the platform’s own instructions or your verified account records. Keep each value separate and preserve the platform’s exact account identifier.
- Open the generator and enter one record at a time. Use a bare domain rather than a website URL, select DIRECT or RESELLER, and add the optional authority ID only when the relevant platform provides an exact value.
- Add the record to the visible list and repeat the process for every authorized advertising system. Use one verified row for each seller account and keep the total at or below 200 records.
- Review the complete list before downloading it. Check the domain, account identifier, relationship, punctuation, and optional authority value. Remove obsolete entries and exact duplicate rows, but do not remove an existing valid seller merely because you are adding another one.
- Back up the current ads.txt file, then copy or download the reviewed output. The generator produces one comma-separated record per line and ends the finished file with a newline.
- Publish the downloaded file as /ads.txt on the root domain that owns the inventory. Open the public address as plain text and compare every visible line with the source instructions and verified account records.
Publish at the root domain
The required public location is the root-domain path /ads.txt. For a website whose root domain is example.com, the expected address is https://example.com/ads.txt. Serving the same content only from /files/ads.txt, embedding it in an HTML page, or placing it behind authentication does not create the same crawler-visible root resource.
After deployment, inspect the file at its public URL rather than relying only on the downloaded copy or your publishing interface. Confirm that the first domain identifies the intended advertising system, the second field matches the account record, the relationship matches who controls that account, and the fourth field is present only when an exact authority ID was supplied. A syntactically valid line can still be unauthorized or incomplete, so this final comparison does not replace account-level verification.
Keep the public file current
Save the prior version before making future changes. Advertising account or network changes may require new records, relationship updates, or removal of obsolete sellers, so review current partner instructions before editing the file. When several systems are authorized, retain one verified record for each account. After every update, deploy the revised file, check the root-domain URL, and compare the complete public text with the records that authorized it.
If you're weighing options, Decode the AI Robots.txt Report Across 32 Product Tokens covers this in detail.