Field count checks
Confirm each authorization line has the expected domain, seller ID, DIRECT or RESELLER value and optional certification authority ID.
Free Ads.txt and App-ads.txt Checker
Ads.txt and App-ads.txt Checker for authorized sellers files checked locally in your browser
Ads.txt content is checked locally in your browser. No ad account login is required. Use the Ads.txt and App-ads.txt Checker to review ads.txt, app-ads.txt and authorized sellers file content for field count, advertising system domains, publisher or seller IDs, DIRECT or RESELLER values, certification authority IDs, duplicate records, comments, blank lines, case issues and common text mistakes.
Browser-local authorized sellers file check
Run the Ads.txt and App-ads.txt Checker
This page combines Ads.txt Checker, App-ads.txt Checker and Authorized Sellers File Checker workflows in one local text parser.
Ads.txt content is checked locally in your browser. No ad account login is required.
Your authorized sellers file stays in this browser tab. This local checker does not verify whether seller IDs are real, check ad network account validity, diagnose Google AdSense or AdMob revenue, or query external ad databases.
Authorized sellers file results will appear here
Paste ads.txt or app-ads.txt content to check local format issues, duplicate authorized seller records, DIRECT and RESELLER distribution, missing fields, malformed domains, case cleanup and a copyable cleaned version.
Authorized sellers file check summary
File type judgment
Valid authorization lines
Invalid line numbers
Duplicate authorization records
DIRECT / RESELLER distribution
Cleanup status
Missing fields
Format errors
Line-level details
Main issues
Repair suggestions
How the Ads.txt and App-ads.txt Checker reviews authorized sellers files
The checker focuses on local text format checks. It does not validate seller ID ownership, ad account health, platform revenue or external database truth.
Ads.txt and App-ads.txt Checker local parsing
Paste ads.txt or app-ads.txt content and the local parser separates comments, blank lines, directives and authorization records inside your browser.
Ads.txt and App-ads.txt Checker result details
The result view shows file type judgment, valid line count, invalid line numbers, duplicate records, DIRECT and RESELLER distribution, missing fields and format errors.
Ads.txt and App-ads.txt Checker cleanup workflow
After the tool lists the main issues, copy the suggested cleaned content, confirm partner-provided IDs yourself and recheck before publishing.
Ads.txt and App-ads.txt Checker features for local ad authorization QA
Use this local parser when one authorized sellers file needs practical format review before you publish or send it to an ad operations team.
Domain and ID review
Spot malformed advertising system domains, protocol or path mistakes, placeholder seller IDs and obvious domain typos.
DIRECT and RESELLER distribution
See DIRECT and RESELLER counts while the checker normalizes relationship case and flags invalid relationship values.
Duplicate authorization records
Find repeated normalized seller records so the final authorized sellers file stays shorter and easier to audit.
Comments and blank lines
Ignore full-line comments and blank lines while still warning about inline comments that may be worth cleaning.
Suggested cleaned content
Copy a normalized version with lowercase domains, uppercase DIRECT or RESELLER values, supported directives and duplicates removed.
How to use the Ads.txt and App-ads.txt Checker before publishing
This paste-in browser tool runs text format checks only, so it is useful before a live crawl or partner review.
01
Paste the final authorized sellers file
Use the exact ads.txt or app-ads.txt content you plan to publish. The local parser reads comments, blank lines, directives and comma-separated authorization records locally.
- Paste production lines from partner documentation
- Avoid mixing notes into authorization records
02
Review Ads.txt and App-ads.txt Checker results
Start with file type judgment, valid line count, invalid line numbers, duplicate authorization records, DIRECT and RESELLER distribution, missing fields, format errors, main issues and repair suggestions.
This is not an ad platform account check. The checker does not confirm whether a seller ID is real, active, approved or connected to revenue.
Review report 03
Apply the Ads.txt and App-ads.txt Checker cleanup carefully
Copy the suggested cleaned content, then compare seller IDs and domains with your SSP, exchange or ad network instructions before you publish the final file.
Keep partner-provided lines as the source of truth when the local checker flags a spelling or case concern.
Recheck contentAds.txt and App-ads.txt Checker FAQ
Answers about local privacy, accepted files, ads.txt and app-ads.txt format, DIRECT or RESELLER interpretation, duplicate records and tool boundaries.
What does this checker validate?
It validates local text format: comma-separated field count, advertising system domain shape, publisher or seller ID presence, DIRECT or RESELLER values, optional certification authority ID, duplicate records, comments, blank lines, case issues and obvious text mistakes.
Does this checker verify seller IDs?
No. It does not verify whether a seller ID is real, active, approved, owned by your company or accepted by a specific advertising platform. Confirm IDs with the SSP, exchange or ad network that issued them.
Can I use one page for ads.txt, app-ads.txt and authorized sellers files?
Yes. This page intentionally combines Ads.txt Checker, App-ads.txt Checker and Authorized Sellers File Checker tasks because the core authorization record format is shared. App-specific directives are reviewed as local text, not by crawling app stores.
Does this checker check AdSense, AdMob or revenue problems?
No. It does not log in to Google AdSense, Google AdMob or third-party ad platforms, and it does not diagnose revenue, fill rate, approval status, bidding eligibility or account policy issues.
Does this checker query external ad databases?
No. The checker does not query external ad databases because those datasets change frequently and can be platform-specific. It only checks the pasted text in your browser.
What should I do when the checker flags a line?
Fix clear syntax problems first, such as missing fields, extra commas, invalid domains or relationship typos. For seller IDs, certification IDs and partner domains, compare against the exact line supplied by your advertising partner before publishing.
Run the Ads.txt and App-ads.txt Checker before publishing
Paste the final authorized sellers file, fix local format failures, review cleanup suggestions, and then confirm real partner IDs with your ad operations source of truth.
This is a local text format checker, not an official ad platform approval or seller identity verification service.