ads.txt File Verification FailuresA scenario may arise where the ads.txt file is not recognized by our platform's verification tool, even if it has been correctly installed. This discrepancy is often attributable to technical conflicts such as site-level caching, the presence of duplicate files, or interference from third-party security services like Cloudflare.
Please review the following troubleshooting checklist to resolve common issues.
Clear Website Cache:
You must ensure that all server, CDN, and website caches (including plugin-level caches) have been thoroughly purged after the file was uploaded or updated. The most current version of the file must be publicly visible and accessible at the URL: [yourdomain.com]/ads.txt.
Check for Duplicate Files:
A common conflict occurs when an automated integration method (such as our plugin) is used while a separate, manually-created ads.txt file still exists on the server. You must verify that no duplicate or obsolete versions of the file are present in your site's root directory.
Review Third-Party Services (e.g., Cloudflare): If you utilize Cloudflare or a similar CDN or security solution, it may be configured to block or challenge automated crawlers, thus preventing our system from verifying the file.
Action Required: If this is the case, please inform our support team. It is often necessary to create a specific firewall or page rule (an "exception") for the /ads.txt page to allow our crawler—and those of our advertising partners—to access it.
Importance: This step is essential, as advertising partners cannot purchase ad inventory on your site without first being able to crawl and validate this file.
Should you continue to experience verification issues after reviewing these items, please do not hesitate to contact our support team for further diagnostics.