Google AdMob has strict policies governing app content, ad placement, and publisher behaviour. Violating these policies can result in ad serving being disabled or your AdMob account being permanently suspended. This article covers the key policies and practices that keep your account in good standing.
app-ads.txt: Required for Ad Serving
app-ads.txt (Authorized Digital Sellers for Apps) is a text file that you publish on your developer website. It tells ad buyers which advertising systems are authorized to sell ad inventory for your app. AdMob requires this file to serve non-test ads.
Creating your app-ads.txt file
AdMob generates the exact content for you:
- In AdMob Console, go to Apps → app-ads.txt
- Copy the provided text: it looks like:
google.com, pub-XXXXXXXXXXXXXXXX, DIRECT, f08c47fec0942fa0
Hosting app-ads.txt
The file must be hosted at the root of your developer domain: the website URL you used when registering in AdMob. For example, if your developer domain is yourwebsite.com, the file must be accessible at:
https://yourwebsite.com/app-ads.txtWordPress: Upload the file to your server's web root (typically /public_html/app-ads.txt) via FTP, cPanel File Manager, or your host's file manager. Alternatively, use a plugin like Ads.txt Manager.
Other platforms: Most website builders allow you to add files to the site root. Check your platform's documentation for "custom files" or "root files".
After publishing, AdMob crawls and validates the file within 24–48 hours. You can verify it's accessible by visiting the URL in your browser.
Content Policy
AdMob will not serve ads on apps containing:
- Adult content, explicit material, or nudity
- Content promoting drugs, tobacco, weapons, or violence
- Hate speech or content targeting protected characteristics
- Content infringing copyrights or trademarks
- Deceptive or misleading content
- Content directed at children under 13 (or 16 in some regions) without appropriate COPPA compliance settings
For WebView apps, this applies to your website's content: AdMob evaluates what the WebView displays, not just the app itself.
Invalid Click and Impression Activity
Never click your own ads, ask others to click them, or use any automated means to generate clicks. Google's systems detect this and will disable your account. Common violations that publishers don't realize are violations:
- Telling family, friends, or social media followers to "click the ads to support me"
- Clicking ads yourself while testing
- Placing ads in positions where users accidentally click them (adjacent to buttons, near page edges that require scrolling)
- Auto-refreshing pages to generate impressions
Ad Placement Rules
Google's Ad Placement Policies require that ads are placed so users can clearly distinguish them from content:
- Ads must not be placed near interactive elements in ways that cause accidental clicks
- Full-screen interstitial ads must be dismissible and must not appear excessively (no more than once every 30–60 seconds)
- Ads must not cover content in a way that forces interaction before the content is accessible
- Ads must be labelled as advertisements (AdMob handles this automatically with the "Ad" badge)
WebToAppConvert's default ad placement follows these guidelines. If you configure custom ad positions, review the placement policies before publishing.
New Account Approval
When you first set up AdMob and publish your app, there is typically a review period (1–7 days) before live ads begin serving. During this time, test ads may serve, but you won't earn revenue. This is normal: AdMob reviews new apps and publishers before enabling monetization.
If ad serving doesn't begin after 7 days, check your AdMob account for policy violations or incomplete setup. Common issues include a missing app-ads.txt file, incomplete payment information, or an app not yet published on Google Play.
Payment Setup
AdMob pays monthly, with a minimum payout threshold of $100 (in most countries). Payment is processed via bank transfer or check, depending on your country. Set up your payment method in AdMob Console under Payments. Revenue is reported in real time, but payments are issued approximately 21 days after the end of each month.