An ads.txt record is a single comma-separated line that declares an authorized digital seller, with four ordered fields: the bare advertising-system domain, the platform-issued publisher account identifier, a relationship of DIRECT or RESELLER, and an optional certification authority ID. Hosted as a plain text file at the root path /ads.txt, the file lets programmatic buyers confirm that the inventory they are about to bid on really belongs to a seller the publisher has approved, rather than to an unauthorized resold chain that the publisher never authorized. Because the file is meant to be read by crawlers and SSPs, every character matters: a stray https://, an accidental comma inside a publisher ID, or a mismatched DIRECT relationship can quietly invalidate a record even when the rest of the line looks fine. The Ads Txt Generator builds that file from the explicit values you copy from each ad platform's own setup page, validates every field against the published rules, blocks duplicate rows, normalizes domain case, and gives you a copy-ready or downloadable text file ending in a newline — all inside a Safari tab on your phone, with no server call carrying your account details.
Why an ads.txt file still matters on mobile
Publishers who manage everything from their phone — small blogs, side-project apps, niche sites — still face the same demand-side trust problem as a large media company: programmatic buyers need a public list of accounts authorized to sell that domain's inventory, and the IAB Tech Lab's ads.txt 1.1 specification defines how that list must be formatted (Ads.txt 1.1 specification). Without the file, ad exchanges either treat every bid as unverified, lowering CPMs, or rely on indirect signals that are easier for unauthorized resellers to spoof. An ads.txt file does not need to be edited on a desktop, and the platform that issued your publisher ID does not need to be opened from any particular device — the file is just a small text document hosted at a fixed URL on your domain root.
What makes an iPhone workflow realistic is that the file is tiny, the public location is fixed, and the values come from the advertising platform's own setup instructions, which you can copy and paste from Mail, Notes, or a screenshot into any mobile browser. The hard part is not the file itself but the discipline around it: copying the exact publisher ID with its pub- prefix intact, choosing the right relationship, and only including a certification authority ID when the platform actually provides one for your seller record.
What the iPhone Safari workflow looks like
Running the generator on an iPhone means opening the Ads Txt Generator page in Safari, pasting the four field values for each authorized seller, reviewing the live preview, and either copying the finished text or downloading ads.txt directly to the Files app. Because everything happens client-side, the page never sends the publisher ID, relationship, or certification authority ID to a server — the iPhone workflow is essentially the same as a desktop session, just with a smaller viewport and on-screen keyboard. That matters because ad account IDs are sensitive identifiers; keeping them inside the browser tab reduces the chance of accidental logging by an intermediate proxy.
The output is the same standards-shaped text regardless of which device produced it. Each seller becomes one comma-separated line, the file ends with a newline, and the page supports up to 200 records so a single mistaken oversized paste cannot produce an unwieldy browser tab. From there, the iPhone workflow moves outside Safari: uploading ads.txt to your hosting control panel, or — if your CMS exposes one — using the platform's built-in file manager, so the public URL https://yourdomain.com/ads.txt serves the file as plain text.
Build your ads.txt file on iPhone in Safari
- Open Safari on your iPhone and navigate to the Ads Txt Generator page; do not enable any private relay or content blocker that rewrites form values, because the page validates the text exactly as you submit it.
- In a separate Mail or Notes thread, copy the advertising-system domain, publisher account ID, relationship, and any optional certification authority ID from each ad platform's own setup instructions — Google AdSense, Google Ad Manager, ad partners authorized through your exchange, and so on.
- Paste the four values into the generator's input area; the page lowercases the domain, rejects any https:// prefix or path, and flags commas or whitespace inside fields rather than silently sanitizing them.
- Tap Add to append the validated row to the visible list, then repeat for every authorized seller. The generator prevents exact duplicate rows, so re-pasting the same record is blocked instead of producing a redundant line.
- Review the full generated text line by line. Remove anything you cannot trace back to a current ad-platform instruction, and confirm each DIRECT row really corresponds to an account you control.
- Tap Copy to put the newline-terminated file into your clipboard, or tap Download to save ads.txt to the Files app. Either path produces identical output — only the delivery step changes.
- Open your hosting control panel or CMS file manager in a new Safari tab, upload ads.txt to the root directory of the inventory-owning domain, then close the generator tab.
The full deployment walk-through for the upload step, including how to verify the public URL afterwards, is covered in the how to create an ads.txt file and publish it guide.
Field rules the generator enforces on iPhone
The iPhone page enforces the same syntax rules as the desktop version, because the validation runs in the browser. The first field is the canonical domain of the advertising system where buyers connect — not your own website — so the value for a Google seller record is google.com, not yourdomain.com. Paste a bare domain like google.com without https://, a path, port, username, or password; the generator lowercases it and checks it against the DNS-style host format. The second field is the seller or publisher account identifier assigned by that advertising system. For Google seller accounts the official guidance uses a pub- prefix followed by the account digits, while other exchanges use different identifiers — copy the value from the platform's own instructions rather than inventing or converting it.
| Position | Field | Required | Format on iPhone | Example |
|---|---|---|---|---|
| 1 | Advertising system domain | Yes | Bare lowercase host, no scheme or path | google.com |
| 2 | Publisher account ID | Yes | Copy from platform; preserve any prefix | pub-0000000000000000 |
| 3 | Relationship | Yes | DIRECT or RESELLER only | DIRECT |
| 4 | Certification authority ID | No | Leave blank unless the platform provides one | f08c47fec0942fa0 |
The third field is restricted to DIRECT or RESELLER. 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, so the relationship must reflect the actual commercial structure rather than a guess. The fourth field is optional. Google's published example includes f08c47fec0942fa0, but that identifier belongs to Google's seller records — do not assume the same string applies to another exchange. Leave the field blank unless the advertising platform provides the exact value for its seller record.
The generator also trims surrounding input, rejects commas or whitespace inside fields, normalizes domain case, prevents exact duplicate rows, and ends the file with a newline. The page supports up to 200 records, so a single mistaken oversized paste cannot produce an unwieldy browser result on a phone screen.
Deploy ads.txt from iPhone and verify the public URL
The deployment step is the one place where the iPhone workflow genuinely differs from a desktop session, and it is where most malformed files surface. The downloaded ads.txt must be hosted as a plain text file at /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 a login does not create the same crawler-visible root resource, so the file will not be picked up by ad exchanges or crawlers no matter how well it was generated.
After uploading from your iPhone, open a fresh Safari tab and load the public URL. The browser should show the raw text — no HTML wrapper, no download prompt, no rendered preview. Read each line and compare it against the verified account records from your ad platforms; if you see a line you do not recognize, a missing pub- prefix, or a relationship that does not match your business arrangement, edit the file before crawlers cache the wrong version. Account or network changes may require future updates, so keep a backup of the prior file and treat each rewrite as a small, reviewable diff.
Pitfalls that break an iPhone-generated ads.txt file
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. A few recurring mistakes show up specifically on iPhone because of how the on-screen keyboard and the small viewport handle paste:
- Pasting the full URL instead of the bare domain. Many iPhone clipboard managers preserve https://, which the generator rejects; copy the host part only.
- Inventing a publisher ID instead of copying it. Other exchanges use different identifiers than Google, so do not convert one platform's format to match another.
- Adding a certification authority ID that was issued for a different exchange. Leave the field blank unless the platform provides the exact value for its seller record.
- Marking a row DIRECT when the account is actually run by a partner. The relationship must reflect the real commercial structure.
- Uploading ads.txt under a subdirectory or wrapping it in HTML. Only the root path /ads.txt is recognized by crawlers.
- Replacing the file and dropping existing valid sellers just to add a new one. Keep a backup of the prior file and add verified records without removing authorized sellers.
If several advertising systems are authorized, add one verified record for each account, review the complete text before deploying, and then check the public URL as plain text after the upload is complete. Formatting assistance cannot replace account-level verification, so treat the iPhone workflow as a quick, standards-shaped scaffold rather than a substitute for confirming each seller against the platform that issued it.
For a deeper look, see What Can Go Wrong When You Check AI Bot Robots.txt.