Google Play rejection
Google does not ban apps that are built around a WebView. It bans apps that wrap a website the developer does not own, and apps that add nothing a user could not get in Chrome. If the site is yours, this rejection is fixable, usually in a single resubmission.
From $109 one-time per platform, or let our team do it all from $698.
Two separate parts of the Play policies produce this rejection. The Spam policy covers apps whose main purpose is to show a website the developer has no permission to wrap, apps that exist only to push affiliate traffic, copy-paste apps with the same content under different names, and apps with no real function. The Minimum Functionality policy asks that an app installs, runs reliably and offers a basic, engaging experience instead of a placeholder or a broken page.
Reviewers see a lot of apps that wrap somebody else's site, so a WebView app is checked more carefully than a native one. Your job is to make two things obvious within seconds: the website belongs to you, and the app is better than opening the URL in a browser. Everything below serves one of those two goals.
Developer name, app name, the domain in the WebView, the privacy policy URL and the verified website in your developer profile all point to the same brand. A reviewer should never have to guess whether you are allowed to wrap this site.
No desktop header, no cookie banner, no footer with a sitemap, no "Install our app" bar, no link that opens a second copy of your site. Bottom navigation, full-width buttons and a fast first paint behind the splash screen.
Push notifications, a native offline screen, the system share sheet, biometric lock, QR scanning or App Links. One or two real native features, used for something meaningful, change the category of the app in the reviewer's eyes.
Every menu item leads somewhere, forms submit, the login works with the credentials you provided under App access, and nothing says "coming soon" or "lorem ipsum".
Work through all six; most rejected apps fail on two or three of them at once.
Play Console lets you link a website to your developer account and verify it through Google Search Console (a DNS TXT record or an HTML file on your domain). Use the same domain the app loads. A preview domain from Lovable, Bolt or Replit cannot be verified, which is one more reason to move to a custom domain first.
The app name, the developer name, the store listing and the domain should tell one story. "Acme Fitness" by "Acme Fitness Ltd" loading app.acmefitness.com is clear. "Fitness Tracker Pro" by "John" loading a .lovable.app subdomain looks like a wrapper of somebody else's product.
Enable push with PUSH_ENABLED (OneSignal) or FIREBASE_PUSH_ENABLED, keep the offline fallback with FALLBACK_USE_LOCAL_HTML_FOLDER_IF_OFFLINE, and add the in-app rating prompt with SHOW_RATE_DIALOG. Then use at least one of them for a real purpose in your web app, such as order updates or reminders. See the Android push documentation.
Use the custom CSS and JavaScript injection to remove the cookie banner, the desktop header and the app-store badges when the page is loaded inside WebViewGold, or set a custom USER_AGENT and detect it in your web app to render an app-only layout.
If any part of the app is behind a login, add working demo credentials under App content → App access and describe what the reviewer will find. A reviewer who cannot get past the login screen sees an app with no functionality.
Bump the version code, rebuild in Android Studio or the Cloud Builder, and roll out again. If you believe the reviewer simply missed that you own the site, add an appeal with proof instead of only resubmitting; the appeal guide has a template for exactly this case.
My iOS WebView is finally approved. Thanks!!
| Passes review | Gets flagged | |
|---|---|---|
| Site ownership | Your own product on your own domain, verified in the developer profile | A third-party site, a scraped news site, an affiliate storefront |
| Content | Logged-in product, tool or community with real users | A landing page, a blog with three posts, a form that leads nowhere |
| Layout | Mobile-first, app-like navigation, safe-area aware | Desktop layout with pinch-to-zoom, cookie banner on every launch |
| Native features | Push, offline screen, share sheet, QR, biometrics used for something | None, or features declared in the listing but not present |
| Listing | Screenshots from the real app, honest description | Screenshots of the website in a browser, generic keywords |
Yes. The Spam policy targets apps that wrap a website without permission or without adding value, not the WebView component itself. Apps that wrap the developer's own product with native features are published every day.
Often, in combination with an app-like layout and a complete, working product. Reviewers look at the whole picture; a push feature that is enabled but never used helps less than one that is visibly part of the product.
A rejection for the technical wrapper itself is a non-content rejection and is covered by the approval guarantee when claimed within 14 days of purchase. A rejection because the wrapped site is not yours or has no real content is a content issue and is not covered.
Same result, different amount of work on your side. All three come with the approval guarantee and 24/7 human support.
$109 per platform, one-time
The WebViewGold license: a finished Xcode or Android Studio project. Paste your URL, set name and icon, switch on features, build and submit. Free updates forever.
See plans on the main page$349 per license, one-time add-on
No Mac, no Xcode, no Android Studio: configure in the browser, we build both apps in the cloud and hand them to App Store Connect and the Play Console.
How the Cloud Builder works Try the free demo$698 per platform $798
Send us your URL and icon. Our team configures, builds and delivers your app within 72 hours, white-label, with source projects. Both platforms for $1,158.
Full Service details Powered by
Winter Sale prices valid until December 31, 2026.
App Store & Google Play approval guarantee – or your money back within 14 days
Rather hand it over? Full Service: we configure, build and deliver within 72 hours, from $698 per platform. Questions? Chat with us 24/7.
Refunds are granted under the conditions listed in our FAQ: a non-content rejection by Apple and/or Google, claimed within 14 days after purchase.
