[CRITICAL Bug] AdMob Crawler Fails to Verify app-ads.txt Despite ALL Steps Verified (3 weeks Failure)

3 views
Skip to first unread message

seihyung oh

unread,
4:20 AM (4 hours ago)  4:20 AM
to Google Mobile Ads SDK Developers
Hello,

Hello, I am experiencing a critical issue with AdMob app verification. My app, [ LoanCalc+ Pro] (App ID: ca-app-pub-4199049212356445~8408044728), has been stuck in the 'Unverified' state for 3 weeks or more  due to a persistent app-ads.txt crawl failure. All required steps have been strictly followed, suggesting a potential system-side bug.

I have thoroughly checked and verified the following points as per AdMob guidelines:

  • Developer Website URL in Store: The developer website URL [ https://c00012.github.io/LoanCalcProPlus/ ] is correctly registered in both the Google Play/App Store listing.

  • Correct File Placement: The app-ads.txt file is located at the root domain ( https://c00012.github.io/LoanCalcProPlus/app-ads.txt ).

  • File Content: The file contains the correct publisher ID: google.com , pub-4199049212356445, DIRECT, f08c47fec0942fa0

  • HTTP 200 Response: Accessing the app-ads.txt URL returns an HTTP 200 OK status, confirming accessibility.

  • robots.txt Check: The robots.txt file does NOT block Google crawlers (Google-adstxt, Mediapartners-Google, Googlebot).

  • Wait Time: I have waited for more than 3 weeks or more  for the crawler to update.

Since all prerequisites have been met and the issue persists for an extended period, I strongly suspect a technical malfunction or bug within the AdMob crawling system.

ACTION REQUESTED:

  1. Please investigate this issue as a system-side bug , not a user configuration error.

  2. Manually initiate the crawl or provide an internal path to escalate this to the L2 Technical Support Team .

Your prompt attention to this matter is greatly appreciated as this is blocking ad serving and revenue.


Thank you for your time and assistance in reviewing this critical issue. I look forward to your prompt response and a resolution from the technical team. 

Best regards, 

seihyung

Reply all
Reply to author
Forward
0 new messages