Google Play webviews and Affiliate Spam policy: fixes and checks

Google prohibits apps whose main purpose is generating affiliate traffic or presenting someone else’s website in a WebView without permission. A native shell around a site doesn’t resolve either issue.

What to check

Identify the app’s primary user task and how much of it is a referral destination. For embedded websites, confirm permission from the owner or administrator.

Check redirects, affiliate parameters, and catalog pages. A useful-looking browsing screen can still mainly exist to earn referral credit elsewhere.

How to address the rejection

Remove the affiliate-first experience or build substantial functionality that serves users within a legitimate app. Obtain and document website permission where needed.

Website ownership doesn’t automatically solve a separate limited-functionality problem. Test the app’s core tasks and explain the value beyond opening the site. In review notes, provide the relevant authorization and a concrete feature walkthrough, rather than claiming that every WebView is allowed or that all website wrappers are prohibited.