Uploading your Android App Bundle (AAB) to the Google Play Store is only part of the publishing process. Before Google's human reviewers will even look at your code, you must pass a gauntlet of administrative requirements in the Google Play Console.
For a traditional native app, these requirements are straightforward. However, for a website-based app (a WebView), these requirements can be tricky to navigate, as your app relies entirely on external web content.
To ensure a smooth approval process, here is a comprehensive checklist of the Google Play Console requirements for website-based apps.
1. The Privacy Policy URL (Non-Negotiable)
This is the single most common reason website-based apps are rejected.
Google requires every app to have a publicly accessible Privacy Policy. Because your app is essentially your website, your website must have a dedicated Privacy Policy page.
- It must explicitly state how you handle user data, cookies, and tracking.
- You must paste the exact URL of this page into the "App Content" section of the Google Play Console.
- The link cannot lead to a PDF download; it must be a live webpage.
2. Advanced Notice / Proof of Web Ownership
Google has strict anti-spam policies to prevent scammers from turning other people's websites (like Wikipedia or YouTube) into apps and monetizing them.
If Google cannot immediately verify that you own the website inside your app, they will reject it and ask for "Advance Notice." To proactively prevent this, ensure that:
- The Developer Name on your Google Play account matches the business name on your website's footer.
- If they ask for proof, you can provide a screenshot of your domain registrar (showing you own the domain) or link to a contact page on your site that explicitly lists your Google Play developer email address.
3. Data Safety Declarations
Google requires developers to declare exactly what user data their app collects.
Even if your native Android wrapper does not collect data, your website does. If your website has a contact form, a checkout page, or a newsletter signup, you are collecting data through the app.
- In the Data Safety questionnaire, you must declare that you collect Names, Emails, Passwords (if you have user accounts), or Financial Info (if you are an e-commerce store).
- You must state that this data is securely transmitted (which is why your website must use an SSL/HTTPS connection).
4. Minimum Functionality (The UX Test)
Google’s human reviewers will download your app and use it. If it feels like a broken website, they will reject it under the "Minimum Functionality" policy.
- No Pinch-to-Zoom: If the reviewer has to pinch the screen to read your text, your mobile CSS is broken, and the app will be rejected.
- Working Navigation: Every link must work. If a menu link leads to a 404 page, the app will be rejected.
- No Trapping: If your app links to an external site (like Facebook), it must open in the user's native browser, or your app must have a built-in back button. If the user gets stuck on Facebook and cannot return to your app, it will be rejected.
5. Age Ratings
You must fill out an IARC content rating questionnaire. Be incredibly honest about the content on your website. If your website contains user-generated content (like a forum), you must declare that. If you aim your app at children (under 13), Google will put your app through a significantly more rigorous privacy review. For most business websites, target an adult audience to simplify the process.
Conclusion
Passing the Google Play Console review is about transparency and quality. By ensuring you have a clear Privacy Policy, honestly declaring the data your website collects, and providing a flawless mobile-responsive design, your website-based app will easily meet Google's requirements and achieve a successful launch.