ads.txt found
The seller file is publicly reachable. Review whether the Google seller line and ID match are also correct.
ads.txt Checker
Verify whether ads.txt exists and includes a valid Google seller line.
This checker fetches the public /ads.txt file. It cannot edit your AdSense account or publish the file for you.
ads.txt statusgoogle.compub IDDIRECT / RESELLER
Overview
About this ads.txt Checker
The ads.txt Checker verifies whether a website has a public authorized digital sellers file at the root of the domain. For AdSense publishers, this file should normally include a valid Google seller line with the correct publisher ID and relationship value.
A missing or incorrect ads.txt file can create monetization warnings, reduce demand, or make ad serving harder to troubleshoot. This checker helps you confirm the file location, Google record, relationship value, and publisher ID matching signals without logging in to AdSense.
How it works
Check a domain or URL in three steps
- 1
Enter the website domain or URL.
- 2
The checker requests the root /ads.txt file and parses active seller records.
- 3
It extracts Google publisher IDs and compares them with ca-pub IDs found in public page code when available.
What this checker looks for
Seller file check
File availability
Whether https://yourdomain.com/ads.txt is reachable and returns a readable text file.
Google seller line
Whether the file contains google.com and a pub ID in the expected ads.txt format.
Relationship value
DIRECT or RESELLER values that describe how the inventory is sold.
Publisher ID matching
Whether pub IDs in ads.txt can be compared with ca-pub IDs found in the page code.
Output language
ads.txt: Found / Missing.
Google seller line: Found / Missing.
Publisher ID match: Match / Mismatch / Unable to verify.
Fix seller file issues before ad serving
Publish ads.txt at the root of the domain, include the correct google.com seller line, and make sure the publisher ID matches your AdSense account.
Features
- Checks whether root /ads.txt is reachable.
- Parses google.com seller lines from the file.
- Detects DIRECT and RESELLER relationship values.
- Extracts pub IDs from ads.txt and ca-pub IDs from page code.
- Flags missing, malformed, or mismatched seller signals.
Benefits
- Fix seller file problems before they affect ad serving.
- Confirm that the published file points to the right Google publisher ID.
- Troubleshoot common AdSense setup warnings faster.
- Review a domain before moving ad code or monetization setup.
Use cases
- Publishers responding to an ads.txt warning in AdSense.
- Site owners checking whether a new domain has the correct seller file.
- Developers validating deployment after moving CMS, hosting, or CDN rules.
- Teams comparing page code publisher IDs with root seller file IDs.
How to interpret results
Read the result as a public signal report
Google seller line missing
The file exists but does not include a google.com record. Add the correct AdSense publisher ID from your account.
Publisher ID mismatch
The page code and ads.txt appear to reference different IDs. Check copied code, old themes, plugins, or ownership changes.
Limitations / disclaimer
What this tool cannot confirm
- The checker reads only the public root ads.txt file and public page HTML.
- It cannot edit your file, access your AdSense account, or confirm private account status.
- Some sites use ad managers, partners, or multiple sellers, so ID matching should be reviewed in context.
Related tools
Continue checking related AdSense signals
ads.txt Checker FAQ
Common questions about what this checker can verify and how to interpret the public report.
Where should ads.txt live?
It should be available at the root of the domain, for example https://example.com/ads.txt.
What does a Google seller line include?
A typical line includes google.com, your pub ID, the relationship value such as DIRECT, and Google's certification authority ID when applicable.
Can missing ads.txt stop all ads?
It can reduce or limit demand and create monetization warnings. It is one of the first public setup files to fix.
Why compare ads.txt with page code?
A mismatch can indicate that the page and seller file reference different publisher IDs, which may cause setup confusion.