A Google Play age-rating rejection almost always means your IARC content-rating questionnaire answers do not match your app's actual content, and the fix is to re-take the questionnaire accurately. Google rejects apps that misrepresent their content in the rating, and the most common mismatches are undeclared user-generated content or social features, ads that are more mature than the app, and understated violence or other mature content. To fix it, go to the content rating section in Play Console, start a new questionnaire, and answer honestly about your app, and the rating updates. If instead you believe an IARC authority rated your app too harshly, that is an appeal rather than a re-rating, using the link in your rating certificate email.
Short answer
An age-rating rejection is a content-declaration problem, not a bug, so you fix it by correcting what you declared. Per Google's content rating requirements, your questionnaire answers must accurately reflect your app, including user-generated content and ads, and misrepresenting content leads to rejection. Per Google's content ratings help, if the rating does not reflect your content you retake it by starting a new questionnaire on the Content rating page. The usual causes are undeclared social or user-generated content, understated violence, and ads more mature than the app. If you believe an IARC authority over-rated the app, you appeal using the link in your certificate email instead.
What the rejection means
Google Play does not assign age ratings by reviewing your app directly; it uses the IARC content-rating questionnaire you complete in Play Console, and IARC turns your answers into ratings for different regions. So an age-rating rejection is really Google telling you that the answers you gave do not match what your app actually contains, which makes the resulting rating inaccurate. The rating system depends on honest self-declaration, and a rejection is what happens when that declaration and the app diverge.
Because the problem is the declaration, the fix is almost never in your code and almost always in your questionnaire answers. Google can flag an app whose content is more mature than its rating suggests, and misrepresenting content in the questionnaire is itself a policy issue. So treat the rejection as a prompt to review, honestly, what your app does, especially around user interaction, violence, and ads, and to redo the questionnaire so the rating it produces is correct.
The most common cause: social and user-generated content
By far the most frequent trigger is user-generated content or social features that were not declared, because these materially affect the rating and are easy to overlook. If your app lets users chat, post, share, comment, interact with each other, or otherwise create and exchange content, that is user-generated content, and the questionnaire asks about it specifically. Declaring that your app has no such interaction when it in fact has a social or messaging feature understates the rating and is a common reason for a rejection.
The fix is to answer the user-generated content questions accurately, since apps with social interaction generally warrant a higher or differently-qualified rating and must disclose it. This does not mean your app is in trouble for having social features; it means those features have to be declared so the rating reflects them. So go through the questionnaire and confirm that every way users can communicate or contribute content is represented in your answers, because an undeclared social or user-generated content feature is the single most likely cause of an age-rating rejection.
Understated violence or mature content
The other common cause is declaring a lower level of mature content than the app actually contains, with violence being the frequent example. If the questionnaire answers describe little or no violence but the app contains realistic or frequent violence, or other mature content such as sexual themes, strong language, controlled substances, or simulated gambling that was understated, the rating comes out too low and the app can be rejected for misrepresenting its content. The questionnaire covers each of these categories, and each answer needs to match reality.
So review the app honestly against every content category the questionnaire asks about, and answer at the level the app genuinely reaches rather than the level you would prefer. If you understated violence or another category, re-take the questionnaire with accurate answers and the rating will rise to match. This is different from a case where you believe the app was rated too harshly; understated content is your own declaration to correct, which is the next section, while an over-strict rating is an appeal, covered further down.
How to fix it: re-take the questionnaire
The direct fix for an inaccurate declaration is to redo the content rating questionnaire with correct answers. In Play Console, open the App content area under Policy, go to the Content rating section, and start a new questionnaire, which lets you answer every category again. Work through the questions on violence, sexual content, language, controlled substances, gambling, user-generated content, and ads, answering each to reflect what your app actually contains.
When you submit the updated questionnaire, IARC recalculates your ratings across the regional systems and applies them to your app, which resolves a rejection caused by the earlier inaccurate answers. This is a self-service fix that does not require contacting anyone, and it is the correct path whenever the rejection stems from your own understated or omitted declarations. So before considering an appeal or support, re-take the questionnaire honestly, since that clears the large majority of age-rating rejections.
Common causes and fixes
Matching the mismatch to its fix makes this quick to resolve. The table below maps the common ones.
| Cause | Why it is rejected | Fix |
|---|---|---|
| Undeclared user-generated content | Social features understate the rating | Declare UGC and interaction accurately |
| Understated violence or mature content | Rating is lower than the app's content | Re-answer at the real content level |
| Ads more mature than the app | Ad content exceeds the app's rating | Declare ads; ensure they are not more mature |
| Wrong category answers | Declaration misrepresents the app | Retake the questionnaire honestly |
| You believe the rating is too high | IARC over-classified the app | Appeal via the link in your certificate email |
Read the first row first, since an undeclared social or user-generated content feature is the most common reason an age rating is rejected.
Ads and the age rating
Ads are a part of the questionnaire that developers often forget, and they can cause a rejection on their own. You must declare whether your app contains ads, and the content of those ads matters: ads shown in your app must not be significantly more mature than the app's own primary content. So a family-oriented app serving mature ads creates a mismatch between the rating and what users actually see, which is a problem even if the app's own content is mild.
The fix has two parts. Declare ads accurately in the questionnaire, and make sure your ad setup does not serve content more mature than your app's rating allows, which you control through your ad network's content settings. So when re-taking the questionnaire after a rejection, treat ads as seriously as your own content, because an app that under-declares ads or serves over-mature ads can be flagged even when its first-party content is perfectly rated.
If you think the rating is wrong: appeal
Sometimes the questionnaire answers were accurate and you believe the IARC authority still rated your app too harshly, and that situation is an appeal, not a re-rating. If you object to the rating assigned by a participating IARC rating authority, you have the right to appeal directly using the link provided in your rating certificate email. Similarly, if an app receives a Refused classification and you want to contest it, you appeal using the URL in the IARC notification email.
So keep the two paths distinct. If your own answers understated the content, re-take the questionnaire, because the rating is correct given wrong inputs. If your answers were honest and you still disagree with the assigned rating, use the IARC appeal link from your certificate email to contest it with the rating authority. Choosing the right path saves time, since re-taking a questionnaire will not change a rating you actually disagree with, and appealing will not fix answers that were genuinely inaccurate.
Fix checklist
Working through these steps clears an age-rating rejection. The checklist below covers them.
| Step | Action | Done? |
|---|---|---|
| Identify the mismatch | Compare your answers to the app's content | [ ] |
| Declare UGC and social | Answer interaction questions accurately | [ ] |
| Match mature content | Re-answer violence and other categories honestly | [ ] |
| Handle ads | Declare ads; keep them within the rating | [ ] |
| Retake the questionnaire | Start a new questionnaire and submit | [ ] |
| Appeal if truly over-rated | Use the IARC link in your certificate email | [ ] |
The step teams skip most is declaring user-generated content, since a social or messaging feature is easy to overlook and is the most common cause of the rejection.
Where a scan fits
An age rating is a content-declaration matter, so a security tool has no role in the rating itself, and it is worth being clear about that boundary.
A scanner like PTKD.com analyzes your Android build for security issues such as exposed keys, over-broad permissions, and risky third-party code, mapped to OWASP MASVS. To be clear about the boundary: PTKD does not complete your content rating questionnaire or change your age rating, which are yours to declare in Play Console and IARC. It reviews the security of the same app you are rating, so a release blocked on the rating is also a good moment to confirm the build is secure.
What to take away
- A Google Play age-rating rejection means your IARC questionnaire answers do not match your app's content, so the fix is to re-take the questionnaire accurately.
- The most common cause is undeclared user-generated content or social features, which materially affect the rating and are easy to overlook.
- Understated violence or other mature content is the other frequent cause, so answer every category at the level your app genuinely reaches.
- Declare ads and ensure they are not significantly more mature than your app, since ads can trigger a rejection on their own.
- Re-take the questionnaire for your own inaccurate answers, but appeal via the IARC link in your certificate email if you believe the rating is genuinely too high, and use a tool like PTKD.com to check the build's security.
