Skip to content
webtoapkfree

Can I put AdMob ads in a WebView app?

Yes. An AdMob WebView app can show SDK ads next to the WebView, and AdSense inside it needs the WebView API for Ads. Framing other sites is not allowed.

GuidesNookesh Karri

Light cover card with the title 'Can I put AdMob ads in a WebView app?' in dark text and a green accent bar

Yes, you can put AdMob ads in a WebView app, as long as the ads come through the Google Mobile Ads SDK and the site inside the WebView is yours. Google allows AdMob ads shown next to a WebView, and if your pages already run AdSense, you register the WebView with the SDK so those web ads keep working. What you can’t do is wrap someone else’s website and sell ads around it.

What Google’s policy says about ads in a WebView app

Google’s policy allows ads in a WebView app through two routes, and both depend on the Google Mobile Ads SDK. The technical requirements for web content viewing frames say AdMob and Ad Manager in-app ads may appear “next to a WebView” when the SDK is in use and you follow the other program policies.

The same page covers ads served by the web page itself. If you monetize AdSense or Ad Manager ads through a web frame, you must use one of these options:

  • The WebView API for Ads, which registers each WebView with the SDK.
  • Another supported frame. On Android, that means Chrome Custom Tabs or Trusted Web Activities.

Google adds that content inside the WebView “is subject to the same content policy requirement as when it is in a browser.”

The framing rule: why the site has to be yours

The framing rule is what gets most site-wrapper apps in trouble. The AdSense Program policies (last updated August 4, 2026) say Google ads may not sit on pages that frame content. Framing means showing someone else’s site in a frame or window without permission from the owners.

The textbook case is a WebView app that loads a news site you don’t run, with your banner at the bottom. Developers on the Kodular community forum describe AdMob flagging WebView apps under “Valuable Inventory: Framed Sites”. Those are user reports, not official rulings, but they match the policy text.

Keep the WebView on your own domain and send links to other sites out to the browser. Our guide on opening external links in the browser shows how.

Three ways to monetize an AdMob WebView app

An AdMob WebView app can earn from native ad units, from the website’s own ads, or from both. Which one fits depends on where your ads live today.

Setup What shows the ad What you need Best for
Native AdMob units around the WebView Google Mobile Ads SDK (banner, interstitial, rewarded) An AdMob app ID and ad units Sites with no ads yet
Web ads inside the WebView AdSense code or Google Publisher Tag on your pages The WebView API for Ads and a registered WebView Sites already earning with AdSense
Both SDK units plus web ads Both integrations, careful placement Rarely worth the clutter

My take: if your site already earns with AdSense, register the WebView and leave the ads on the web side. You keep one ad setup and one set of placements, and you never stack an SDK banner on a page that already shows ads. Native units only make sense when the site has no ads and the app adds real features of its own.

How to set up the WebView API for Ads on Android

The WebView API for Ads connects the Google Mobile Ads SDK to the ad tags inside your pages. Google’s integration guide says it makes app signals available to those tags, which helps monetization and protects advertisers from spam. It only talks to the SDK in response to ad events from AdSense code, Google Publisher Tag or IMA for HTML5.

  1. Check the prerequisites. You need Google Mobile Ads SDK (Legacy) version 20.6.0 or later and Android API level 21 or higher.
  2. Add the manifest tag. Put <meta-data android:name="com.google.android.gms.ads.INTEGRATION_MANAGER" android:value="webview"/> in AndroidManifest.xml. Without it, the SDK throws an IllegalStateException on app start.
  3. Register the WebView. Call MobileAds.registerWebView(webView) on the main thread, as early as possible, for example in onCreate() of your MainActivity.
  4. Configure the WebView for ads. Turn on JavaScript, DOM storage, autoplay and third-party cookies (details below).
  5. Test before going live. Load the test page linked from Google’s integration guide first. Green status bars mean the WebView is connected to the SDK. Then swap in your own URL.

WebView settings that affect ad revenue

Default WebView settings are not tuned for ads, and leaving them alone costs revenue. Google’s WebView optimization guide asks you to enable JavaScript, local storage, automatic video play and third-party cookies on every WebView instance.

How the page loads matters too. Google says cookies and page URLs “only function as expected” when loadUrl() points at a network-based URL. It tells you to avoid WebViewAssetLoader, loading assets from the device, or generating web content on the fly.

This hurts offline HTML apps. Pages bundled inside the APK so they work without internet are a poor home for web ads, and ad tags need a connection anyway. For a fully offline app, use native AdMob units. Our post on whether a WebView app works without internet explains which parts need a connection.

Consent is the step people miss. Google’s guide says the WebView API for Ads does not pass consent collected in the app with IAB TCF v2.3 or IAB CCPA to the tags in your web views. If your app shows a consent form in native code, the web ads won’t see the answer. Gather consent inside the WebView as well, or work with your consent platform on a single flow.

Then there’s the store listing. The Play Console has an Ads declaration on the App content page, and third-party SDK, display, native and banner ads all count. Apps that declare ads get a “Contains ads” label. Misrepresenting ads can get the app suspended.

Ads also change other forms. An ad SDK collects device data, so your Data safety form and privacy policy need to mention it.

Can a no-code builder add AdMob for you?

A no-code WebView builder only adds AdMob if it offers an ad SDK option. Webtoapkfree.com shows where that line sits. Its options cover the app name, package name, icon, colour, theme, navigation and Website, HTML and Text sections. An ad SDK is not on that list, and the tool adds no vendor advertising to the app it builds.

In practice:

  • Web ads on your own site still load in a Website section, because the page is your live site. Without the WebView registered, though, you’re outside Google’s listed integration options, so treat that as a risk, not a plan.
  • Native AdMob units need an Android project where you add the SDK yourself, for example in Android Studio.

That’s the hard limit of any no-code wrapper: monetization that needs native code needs a real Android project. If ads are central to the app, start in Android Studio. Ads alone also won’t save a thin wrapper from review, so read why Google Play rejects WebView apps for minimum functionality before you publish.

FAQ

Is it against AdMob policy to show ads in a WebView app?

No. Google’s policy says AdMob in-app ads may be shown next to a WebView as long as the Google Mobile Ads SDK is in use and you follow the other program policies. Showing ads on pages that frame someone else’s site without permission is not allowed.

Can I use my website’s AdSense code inside the app?

Yes, if you register the WebView with the Google Mobile Ads SDK through the WebView API for Ads. Google lists that, Chrome Custom Tabs and Trusted Web Activities as the supported ways to monetize AdSense and Ad Manager ads in a web frame on Android.

Does the WebView API for Ads need an AdMob app ID?

No. You add a meta-data tag named com.google.android.gms.ads.INTEGRATION_MANAGER with the value webview, which bypasses the application ID check. Leave it out and the SDK throws an IllegalStateException when the app starts.

Do I have to declare ads on Google Play?

Yes. The Play Console App content page has an Ads declaration, and banner, native, display and third-party SDK ads all count. Apps with ads get a Contains ads label, and misdeclaring can lead to suspension.

Sources