
ads.txt Guide for AdSense: Authorized Sellers, DIRECT Records, and Checks
Learn what ads.txt does, how Google AdSense publisher records are structured, and how to check the file before review.
Create and review ads.txt records for publisher verification without uploading seller IDs or pasted records to tempboxs.
Create a Google AdSense authorized-seller record and review pasted ads.txt lines locally before publishing them at your site root.
Google publisher line was found in the pasted ads.txt.
google.com, pub-1234567890123456, DIRECT, f08c47fec0942fa0
Line 1: ignored
Comment line.
Line 2: valid
Record shape looks valid.
google.com, pub-1234567890123456, DIRECT, f08c47fec0942fa0
This checker runs locally in your browser. tempboxs does not upload your publisher ID, pasted ads.txt records, seller accounts, or generated line.
ads.txt is a public text file that lists authorized digital sellers for a domain. Advertising platforms use it to reduce spoofing and confirm which seller accounts are allowed to sell inventory for the site.
For Google AdSense, a common record uses google.com, the publisher ID, the DIRECT relationship, and Google's certification authority ID.
An ads.txt record is comma-separated. The first field is the advertising system domain, the second is the publisher or seller account ID, the third is the relationship type, and the optional fourth field is a certification authority ID.
DIRECT usually means the publisher controls the seller account. RESELLER means another authorized party sells inventory. Use the relationship shown by the ad platform, not a guess.
Publish the file at the root of the domain as /ads.txt. After deployment, open the URL in a browser and confirm the file returns plain text with the expected records.
Keep the file small, accurate, and updated when ad accounts change. A malformed or missing line can delay ad verification or cause inventory to be treated as unauthorized.
ads.txt checks run locally in your browser. tempboxs does not receive publisher IDs, seller records, or generated lines.
Turn a Google AdSense publisher ID into a copyable authorized-seller record.
Parse ads.txt lines and flag missing fields, invalid relationships, and suspicious Google authority IDs.
Use the tool before publishing /ads.txt so ad platforms can verify authorized sellers more reliably.
Learn more about privacy, tracking, passwords, and safer signups.

Learn what ads.txt does, how Google AdSense publisher records are structured, and how to check the file before review.

Learn how robots.txt rules affect public tools, blog posts, policy pages, sitemaps, and crawlability before search or AdSense review.

Learn which meta tags help search engines, social previews, and AI crawlers understand a page, and how to audit them before publishing.

Build a practical browser-only workflow with temporary email, generated passwords, URL cleaning, header review, and tracking-pixel checks.
Review content quality, policy pages, ad placement, crawlability, and technical files before AdSense checks.
Generate random UUID v4 identifiers in your browser, copy one value, or create a small batch for testing.
Convert Unix timestamps, milliseconds, ISO dates, and local-readable times locally in your browser.
Paste page HTML to inspect title tags, meta descriptions, canonical URLs, robots directives, Open Graph tags, and JSON-LD locally in your browser.
Generate JSON-LD schema markup for articles, FAQ pages, web pages, and browser tools locally before publishing.
Draft Open Graph and Twitter card preview tags locally for articles, tools, landing pages, and social shares.
Generate an llms.txt draft for AI discovery with public pages, useful tools, safety notes, and crawling guidance.
Generate sitemap XML from public URLs and check duplicate or invalid entries locally before publishing.
Paste robots.txt rules to test whether a URL path appears allowed or blocked for Googlebot, Bingbot, or another crawler locally in your browser.
Decode JWT headers and payloads locally in your browser, inspect claims, and learn what still needs verification.
Check password length, character variety, common patterns, and estimated guess resistance locally in your browser.
Paste email HTML to find likely tracking pixels, remote images, and marketing links locally in your browser.
Convert common YAML snippets into formatted JSON locally in your browser for configs, docs, and API examples.
Parse browser, operating system, device, engine, and bot hints from user agent strings locally in your browser.
Paste raw email headers to inspect sender fields, authentication results, and delivery hops locally in your browser.
Parse a URL into protocol, origin, hostname, port, path, query parameters, hash, and decoded components locally in your browser.
Encode URL text into percent-escaped values or decode encoded URLs locally in your browser.
Clean tracking parameters from links, decode common redirect URLs, and inspect domains locally in your browser.
Look up common DNS record types, purposes, examples, and setup notes locally in your browser.
Build campaign URLs with UTM source, medium, campaign, term, and content parameters locally in your browser.
Format, minify, and validate JSON locally in your browser with clear error feedback.
Encode HTML-sensitive characters or decode named and numeric entities locally in your browser for docs, blog posts, comments, and support replies.
Test JavaScript regular expressions, flags, matches, indexes, and capture groups locally in your browser.
Look up common file extensions, MIME types, categories, and delivery notes locally in your browser.
Preview Markdown headings, lists, links, inline styles, and code blocks locally in your browser before publishing docs or guides.
Generate a browser-only privacy checklist for signups, support tickets, link sharing, and publishing workflows.
Count words, characters, sentences, paragraphs, reading time, speaking time, and repeated terms locally in your browser.
Check foreground and background hex colors against common WCAG contrast thresholds locally in your browser.
Explain five-field cron expressions locally in your browser with readable field meanings and schedule warnings.
Convert CSS px, rem, em, and percent values locally in your browser with adjustable root and parent font sizes.
Convert CSV or tabular spreadsheet exports into formatted JSON locally in your browser with header and delimiter controls.
Convert text into lowercase, uppercase, title case, sentence case, slug, snake_case, kebab-case, camelCase, and PascalCase locally in your browser.
Look up common HTTP status codes, meanings, categories, and troubleshooting notes locally in your browser.
Encode plain text to Base64 or decode Base64 back to UTF-8 text locally in your browser.
Generate SHA-256, SHA-384, and SHA-512 hashes for text or local files without uploading them.
No. The generator runs locally in your browser and does not send publisher IDs or pasted ads.txt records to tempboxs.
Publish it at the domain root, such as https://example.com/ads.txt, and make sure it is reachable as plain text.
A typical Google AdSense line is google.com, pub-0000000000000000, DIRECT, f08c47fec0942fa0. Replace the publisher ID with your own.
No. It checks the shape of pasted records. Actual AdSense account approval and site verification happen inside Google AdSense.