Is your app ready for Google AdMob?

We pull your app from the Play Store or App Store, then run automated checks for: store listing completeness (name, icon, screenshots, description, content rating), developer website and privacy policy reachability, and app-ads.txt validation per Google's spec (file present, served as text/plain, valid UTF-8, correct DIRECT entry for google.com, valid publisher ID format). We also surface a manual checklist for items only you can confirm: ad placement, content originality, traffic sources, account verification, and COPPA tagging.

No. The auto checks cover what we can verify from outside your app. AdMob's review also considers content originality, ad placement quality inside the app, and traffic source legitimacy. The manual checklist below the score covers the items only you can confirm. A high score plus a clean manual checklist is the right pre-submission signal.

Starting January 2025, AdMob requires app-ads.txt verification for new apps before full ad serving begins. Existing apps are being phased in throughout 2025. The file proves you authorized Google to sell your inventory. If it's missing, malformed, or not served as text/plain, AdMob will not verify your app and ads will not serve at full rate.

A Play Store URL like https://play.google.com/store/apps/details?id=com.example.app, an App Store URL like https://apps.apple.com/us/app/.../id123456789, or a bundle ID alone (com.example.app for Android). Bundle ID alone defaults to the Play Store. App Store needs a track id or full URL.

No. Each check runs fresh and the result is sent directly back to your browser. We do not log inputs, save reports, or maintain accounts.

The most common cause is a developer website URL that exists in your Play Console but is not yet propagated on the public listing, or an app-ads.txt file that is served as text/html instead of text/plain. Click into each failed check for the specific fix.