Guides
Google Play's UGC Policy for Website Apps: Report and Block Rules (2026)
If your site lets visitors post comments, reviews or messages, Google Play expects report and block tools inside your app. Here is what the policy covers, what reviewers flagged in real cases, and how to fix a rejection.
Yes, if your website lets people post anything that other users can see, such as comments, forum threads, reviews, profiles or chat messages, Google Play treats your app as a user-generated content (UGC) app. That includes apps that are only a browser or client pointing at a UGC site. Google then expects accepted terms, a definition of objectionable content, and in-app ways to report content and users and to block other users. If your site has no user posts, none of this applies. The rules below were checked against Google's Play Console Help page in November 2026.
Does Google Play's user-generated content policy apply to my website app?
Google defines UGC as content that users contribute to an app and that is visible to at least some of the app's other users. In a rejection notice posted by one developer, Google's reviewers added that this includes user profiles, comments, media and posts. The policy page also names apps that act as specialized browsers or clients for a UGC platform, which is exactly what a website wrapper is when the site hosts user posts. In practice, and this is our reading, the question a reviewer asks is what a user can do inside the app, not what your site's admin panel can do.
| Your site has... | Counts as UGC? | What Google's policy asks for |
|---|---|---|
| Blog or news site with visitor comments | Yes | Publicly accessible UGC (the policy names blogger apps): in-app reporting of content and users, plus blocking users |
| Forum or community | Yes | Same as above: report content, report users and block users, all inside the app |
| Direct messages, tagging or @mentions between users | Yes | In-app blocking of users, at minimum |
| Closed portal for one school or company | Yes, if members post content others can see | In-app reporting of content and users |
| Marketplace or store with user reviews or seller listings | Likely | Treat it like public UGC and add report and block controls |
| Brochure site, booking forms, store with no reviews | No user content visible to others | The policy does not appear to apply |
What does Google require inside the app?
Google's page lists four obligations for any app that features UGC. In short:
- 1Users accept your terms of use or user policy before they can create or upload anything.
- 2Those terms define objectionable content and behavior and prohibit it.
- 3You moderate in a way that fits the type of content, including an in-app system to report and block objectionable content and users, and you take action where appropriate.
- 4You put safeguards in place so in-app monetization does not encourage objectionable behavior.
How much you have to build depends on the kind of UGC. An app for a known set of users, such as one school or company, needs in-app reporting of content and users. Features that let users interact one to one, like messaging, tagging or mentioning, need in-app blocking. Publicly visible UGC, such as social networks and blogs, needs reporting of both users and content, plus blocking. Apps whose main purpose is hosting objectionable UGC are removed from Google Play, and failing to act on user complaints is listed among common violations. Source: Google's User Generated Content policy.
Do my website's own report and block buttons count as in-app?
Google's policy says "in-app" but does not say whether a control that your website renders inside the WebView counts. The best evidence we found is one developer's public account, so treat it as a data point rather than a ruling. In September 2022 the team behind an app embedding a Discourse forum was rejected for lacking in-app functions to flag content, flag users and block users. Those are web features of the forum, and after roughly 18 days and two appeals Google approved the update on September 23, 2022, once the developer sent screen recordings showing each control. The developer also reported that a labeled link opening a message to the moderators was accepted as the way to report a user, and concluded that the requirement is that the function be in-app, not that it be a button literally named "report user".
Two warnings from the same thread. First, the developer said a reviewer flagged a post with the test account and still cited missing reporting, so assume reviewers will not hunt for controls. Second, a commenter advised lowering the site's trust-level settings so that brand-new accounts can see the flag and mute controls. Reviewers sign in with the test account you give them, which is usually a new, low-privilege user (our inference), so test every control as a fresh account. Source: the Discourse thread.
How do I fix a UGC rejection step by step?
- 1
Map every place users post
List each page where visitors can post, upload or message: comments, reviews, profiles, listings, chat. Anything visible to other users counts.
- 2
Add report-content controls
Put a clearly labeled report or flag option on every post, comment or listing, and check that a brand-new account can see it.
- 3
Add a way to report users
A profile-level report is the obvious route. In the documented case, a clearly labeled link that opens a message to the moderators was accepted instead.
- 4
Add block or mute
Let any user block or mute another user from a profile or post, with no trust level or paid tier needed.
- 5
Require terms at sign-up
Make accepting your terms mandatory before the first post, define objectionable content in them, and describe what you do about violations.
- 6
Give reviewers a working login
Provide a stable test account under App access so the reviewer can reach the controls.
- 7
Resubmit with evidence
Add notes or a short screen recording showing each control. Google's notice in the Discourse thread invites you to contact policy support if all required features exist and are reasonably identifiable.
Step six is covered in detail in our app access instructions guide, and the wider list of causes is in why Google Play rejects WebView apps. If you cannot add these controls to your site, one option (not something Google's page describes) is to hide the user-posted sections from the app version of the site. Another is access control: in a Google message quoted on a Discourse support thread, Google suggested a private track for apps meant only for private or limited access, while noting that moderation tools are still required. Source: that support thread.
What else does the UGC policy check?
Three smaller points on Google's page matter for sites with open communities.
- Incidental sexual content must be hidden by default behind a filter that takes at least two user actions to turn off, and children must be kept out with age screening.
- Your answers to the content rating questionnaire about UGC must be accurate.
- Illegal sexual content and child endangerment content are never treated as incidental.
If users create accounts and post, the same features also affect what you declare in the Data safety form.
Frequently asked questions
- Does my app need report and block buttons if my site has no comments?
- No, as far as the policy goes. It covers content that users contribute and that other users can see. Brochure sites and booking forms with no visible user posts fall outside it. If you add comments or reviews later, the rules start to apply.
- Is a WebView app really covered by Google Play's UGC policy?
- Yes, when the site hosts user posts. Google's policy page names apps that are specialized browsers or clients pointing users to a UGC platform, so a wrapper is not exempt.
- Do I need native report buttons, or will my website's buttons work?
- The policy says in-app and does not define it further. In one public 2022 account, web-based flag and mute controls inside an embedded forum were accepted after two appeals and screen recordings. Make the controls visible and clearly labeled, and test with a new account.
- How long does it take to resolve a UGC rejection?
- It varies. The one documented case we found took about 18 days across two appeals in 2022. That is a single example, not a guarantee, and fixing the controls before you resubmit is faster than appealing.
- What if my app is only for a private group of users?
- The policy has a tier for apps serving a specified set of users, such as a school or company, which still need in-app reporting of content and users. Google has also suggested a private track for apps meant only for limited access, with moderation tools still required.
- Can Google remove my app over user posts?
- Google's page says apps whose primary purpose is hosting objectionable UGC are removed, and apps that become known for hosting it can be too. Continually failing to address user complaints is listed as a common violation.