1. Google's Webviews and Affiliate Spam policy requires you to be the website owner, or hold written authorization from the site owner, before publishing an app that displays the site's content in a WebView - this is the #1 rejection reason for WebView apps.
2. Apps whose primary purpose is to drive affiliate traffic to a website are prohibited outright - the app must deliver value beyond sending users to a website.
3. Keep proof ready: domain registration records (WHOIS), DNS TXT verification, or a signed agreement with the site owner. If Google requests it, submit the documentation via the Advance Notice Form, or attach it to your appeal in Play Console after a rejection.
4. 2026 enforcement has tightened: raw WebView apps that merely mirror a website without app-specific value are rejected under Minimum Functionality - add at least 2-3 native features (push notifications, native navigation, offline fallback, biometric login) so the app offers what a mobile browser cannot.
5. Submission checklist for WebView apps: use AAB format, meet the current target API level, integrate Play Integrity, keep screenshots and descriptions accurate, pick the right category, provide a privacy policy, and offer in-app account deletion if users can create accounts.