Google Play spam policy: fixes and checks
By The Draftbit team · Updated
Sources checked
This guide is for Apps that send unwanted messages or add repetitive, low-value experiences to Google Play.
Google’s Spam policy covers several different problems. Start with the specific example in the notice: unsolicited messages, affiliate traffic, unauthorized WebViews, or repetitive content each require a different fix.
What to check
Review the app’s main purpose and complete its core task. Compare it with other apps in your own catalog and inspect sharing or invitation flows.
Ask what users gain from installing this particular app. A changed name and icon don’t create a distinct experience if the content and functionality remain the same.
How to address the rejection
Use the relevant policy below to fix the actual behavior. Give users control over outgoing messages, obtain permission for third-party website wrappers, and consolidate near-identical apps where appropriate.
Describe the resulting user experience in your response. Don’t submit a cosmetic variation of the same rejected app. If the notice identifies harmful unsolicited sending as malware, also check the separate spam malware category.
Messages this guide can help with
Spam; Spam policy violation; Spam rejection; Spam denied
Official sources
We checked these instructions against the sources below. The console layout may change, and your review decision may call for different steps.
- Google Play: Spam Checked 22 September 2026