There's a step in the Google Play publishing flow that doesn't get talked about much, but it quietly controls where your app can be installed and who can see it.
It's the content rating questionnaire.
Google requires every app to go through an IARC rating before it can go live. The questionnaire itself only takes about five minutes. But the answers you give determine whether your app gets rated Everyone, Teen, or Mature 17+, and that rating directly affects distribution. Some countries restrict apps with higher ratings. The Designed for Families program is locked behind an Everyone rating. And once your rating is set, changing it means resubmitting and waiting for a new review.
Here's where it gets tricky.
The questionnaire asks about things like violence, language, sexual content, controlled substances, gambling, user-generated content, and location sharing. Most of those are straightforward if your app is simple. But the user-generated content question catches a lot of people off guard. If your app has a WebView that loads external pages, Google may consider that UGC. If you say yes to UGC, your rating jumps, and you might lose access to distribution in certain markets.
The other common mistake is over-disclosing. If you're building a health app and one screen mentions nicotine or alcohol in an educational context, you might be tempted to flag it. But doing so can push your rating higher than it needs to be. The questionnaire is about what your app enables or depicts, not what it references in passing.
A few things worth knowing before you start:
The rating applies globally, but each store interprets the IARC rating slightly differently. Google Play tends to be stricter on UGC and gambling triggers.
If your app changes significantly, like adding a chat feature or in-app purchases tied to chance, you're supposed to redo the questionnaire. Google doesn't always catch this right away, but when they do, your app can get suspended until the rating is updated.
The questionnaire is also one of the gates you have to pass before your first production release. If you skip it or leave it incomplete, the Publish button stays grayed out and Google gives you almost no feedback about why.
I built IOn Emit to walk through this step as part of the publishing flow, so you don't have to guess at the answers or realize three weeks later that your rating is limiting installs. It's freemium and handles the content rating alongside the rest of the Play Console checklist.
theionproject.com/ionemit
Anyone else run into a situation where their content rating unexpectedly changed their app's reach?
Top comments (0)