Google Play Content Rating Refused or Overridden: Next Steps

A refused classification is not the same failure as a wrong rating, and the remedy Google documents for each is different. If a rating authority refuses classification, Play Console shows "Refused classification" in place of a rating and Google Play removes the app in that authority's territory only. If an authority overrides the rating your questionnaire calculated, the badge on your listing changes and your stored answers no longer describe what users see. Neither problem is fixed by a support ticket: Google routes refusals and overrides to the rating authority, and routes bad answers back to the questionnaire in Play Console.

This article covers the remediation path only: what each state looks like inside Play Console, the test that tells you whether to retake the questionnaire or appeal, what the appeal actually has to argue, and the commercial cost of leaving a wrong rating in place. The declarations themselves, and how they fit into listing review, are covered in our store listing review checklist.

The three failing states, and what each one means

Developers use "my rating is wrong" for three different situations. The Console behaviour differs in each.

• No rating at all. The Content Ratings policy does not allow it: "Apps without a content rating will be removed from the Play Store." This is the state you land in when the questionnaire was never submitted, or when a submitted change was never applied to the app.
• A rating that disagrees with your answers. Google warns explicitly that "the calculated rating shown on the Summary page may not be the rating shown to users on Google Play." Your app can hold different ratings in different territories because each authority applies its own standards and its own logic to the same set of answers.
• Refused classification. A rating authority has declined to classify the app for its territory. Google's help states that IARC notifies you by email, that Play Console displays "Refused classification" in place of a rating, and that Google Play "will remove apps and games with the Refused classification designation in the applicable territory only."

Only the second and third states involve a rating authority decision you can contest. The first is an administrative gap on your side.

Retake or appeal: the test that comes before anything else

The choice is decided by one question: were your answers true of the app as it exists now? If they were not, the rating is a symptom and retaking the questionnaire is the only route. If they were, and an authority has still overridden or refused the rating, you appeal. Google describes these as separate mechanisms, and mixing them wastes the one week you cannot get back during a release window.

1. Read the rating you actually hold. Open the App content page in Play Console and look at the rating state, not the Summary page you remember from submission.
2. Compare the answers to the shipped build. If the app has gained chat, user posts, purchases, gambling-like mechanics, mature imagery, or third-party content since you answered, the answers are stale. Retake the questionnaire.
3. Check whether a declaration contradicts the rating. A rating that is fine on its own still fails when the target audience section claims an older audience than the content supports. That mismatch is fixed in the declaration, not by appeal.
4. If the answers are current and an authority still overrode or refused, appeal. Use the link in the certificate email from IARC. Do not retake as a workaround, because a second identical set of answers reproduces the same result.

Retaking the questionnaire: the mechanics that cause trouble

Google's documented path is Policy, then App content, then Start, then an email address for IARC correspondence, a category selection, and the questionnaire. Three details in that flow are where retakes go wrong.

One draft per app

"Each app can have one draft questionnaire at a time," per Google's help page. If a colleague starts a retake and abandons it, the draft persists and the next attempt continues from someone else's half-finished answers. Decide who owns the form before opening it, and treat the draft as shared state rather than a personal scratchpad.

The email address is the appeal channel

The address you enter at step two "will be used for correspondence with International Age Rating Coalition (IARC)." Google's appeal instructions point to "the link provided in your certificate email." A shared inbox nobody monitors, or a developer's personal address that leaves with them, is how an appeal link goes unread. Use a role address that survives staff changes.

Start new questionnaire, not Edit, when the content changed

Edit corrects a response inside a section you have already completed. When the underlying content changed, the rating itself has to be recalculated: Google's instruction is to click Start new questionnaire on the Content rating page. After submission, the ratings and the questionnaires behind them are reviewable under "Target audience and content" on the App content page, which is the record to keep if you later need to show what you declared and when.

Category selection is the one answer that reframes the rest

Google's steps put a category choice before the questionnaire body. In our reading of the flow, that is the structural answer in the form: the section set you are asked to complete follows from it, so a utility app filed under the wrong category can produce answers that do not match how Google later classifies the same features. It is worth re-reading the category you chose before retaking for any other reason, because a retake that reproduces a wrong category reproduces the wrong rating.

Appealing a rating: what the authority can act on

Google states the right plainly: "If you object to the rating assigned to your app by a participating IARC rating authority, you have the right to appeal directly using the link provided in your certificate email." Questions about IARC that are not appeals go through the contact form on the IARC developer site rather than Play Console support.

What an appeal can argue is narrow. It contests how a rating authority applied its methodology to accurate answers: the questionnaire described the app correctly, and the resulting label does not follow from those answers or from the authority's published criteria. An appeal built on commercial harm, competitor ratings, or a wish for a lower badge has nothing in the documented process to attach to. The practical work is documentary: the submitted questionnaire, the certificate email, and screenshots or a build that shows the content the answers described.

Timelines are not published. Google's help pages set out the route and the right, not a response window, so any plan that assumes an appeal resolves before a specific release date is a guess. Treat the appeal as parallel to your release plan, not a dependency of it. One confusion worth closing early: a rating appeal is not an account appeal. Rating decisions go to the rating authority, while account enforcement runs through a different process, covered in appealing a terminated developer account.

Refused classification is territory-scoped, not a suspension

This distinction saves developers from overreacting. A refusal is a decision by one authority about one territory. IARC emails the developer, Play Console replaces that authority's rating with "Refused classification", and Google Play removes the app in that territory only. The rest of your distribution is untouched, and nothing in Google's description frames it as an account-level enforcement action.

The appeal for a refusal uses the URL in the IARC notification email. Two practical options sit alongside the appeal: correct the content that triggered the refusal and resubmit through the questionnaire, or stop distributing to that territory. The second is a business decision rather than a policy fix, and it does not erase the refusal from the Console record.

A wrong rating costs distribution, not just cosmetics

Ratings are used for more than a badge on the listing. Google's help lists the operational uses, and one of them is expensive to get wrong: in the European Economic Area, Australia, Brazil, Indonesia, Singapore, Switzerland and the United Kingdom, for users determined to be minors, ratings are used to block the acquisition and purchase of mature content such as 18+ rated apps, and to block or filter that content from Google Play search and browse pages except through deep linking.

Read that in the other direction and the risk becomes clear. An answer given defensively, which pushes an app into an 18+ band it does not belong in, removes that app from browse and search for minor users across several large markets. Ratings also feed eligibility for special developer programs. And the icons are not free to reuse: Google notes they are protected trademarks of the respective authority, with display guidelines published by IARC, so a listing that restyles a rating badge is a separate problem from a wrong rating.

Ratings expire with your content, not with your launch

The questionnaire is not a launch task. Google requires it for new apps, for existing active apps that lack a rating, and for "all app updates where there has been a change to your content or features that would affect the responses to the questionnaire." The changes that most often invalidate an answer are the ones shipped quietly: added chat or comments, user-generated posts, digital purchases or loot-box mechanics, a webview or embedded content source, new categories of imagery, or targeted advertising that changes age suitability.

Based on our analysis of 1,500+ closed-testing campaigns, the rating problems we see at intake are rarely missing questionnaires. They are questionnaires answered for a build the developer has since changed, still describing the app as it was three releases ago. When a content change lands mid-test, redo the questionnaire in the same publishing cycle as the release, so the declaration and the build under review agree; the deadline pattern for declaration changes is set out in the policy deadlines that hit apps already live.

Ads have to match the rating you end up with

One dependency runs the other way. Google requires that ads and their associated offers be appropriate for the app's content rating, and says to check with your ad service provider that the campaigns you enabled only serve content matching that rating; for AdMob it points to the blocking controls in AdMob help. A developer who retakes the questionnaire and lands on a lower age band, without adjusting ad filters, has created a mismatch between the rating and what the app shows. The ad filter is part of the fix, not an afterthought to it.

Frequently Asked Questions

Can I appeal a content rating I disagree with?

Yes, for ratings issued by a participating IARC authority. Google states you have the right to appeal directly using the link in your certificate email. The appeal argues that accurate answers were rated incorrectly, not that the rating is commercially inconvenient. Refusals are appealed through the URL in the IARC notification email.

What does "Refused classification" mean in Play Console?

A rating authority declined to classify your app for its territory. Play Console displays "Refused classification" instead of that authority's rating, and Google Play removes the app in that territory only. It is scoped to one authority's market rather than a global removal or an account-level action.

Should I retake the questionnaire or appeal first?

Retake if your answers no longer describe the shipped build, and appeal if they do. Retaking with the same answers reproduces the same calculated rating, which makes it a wasted cycle rather than a workaround. Check the app's current content against the stored answers before choosing.

Will a rating authority change my rating after I submit it?

It can. Google states that rating authorities participating in IARC may change an app's rating after a review, and that if an authority overrides the rating and you want to update your responses, you must complete the questionnaire again. The override is not something the questionnaire prevents.

Can the same app have different ratings in different countries?

Yes. Google explains that an app can earn different ratings in different territories because rating standards and each authority's logic differ. One questionnaire produces ratings from multiple authorities; ESRB covers the Americas, PEGI covers Europe and the Middle East, USK covers Germany, ClassInd covers Brazil, the ACB rates games in Australia, GRAC rates games in South Korea, South Korean apps and Russia use the Google Play Rating system, and territories without a participating authority receive the IARC generic rating.

What happens if my app has no content rating at all?

Google Play removes it. The Content Ratings policy states that apps without a content rating will be removed from the Play Store, and the questionnaire is required for new apps and for active apps that lack a rating. This is the one state in this article that never involves an appeal.

How long does a rating appeal take?

Google does not publish a timeline for rating appeals, and this article will not invent one. The documented process sets out the route and the right of appeal without a service level. Plan the release around the appeal rather than assuming it lands before a date.

Sources

• Content rating requirements for apps, games, and the ads served on both — Play Console Help (questionnaire steps, draft limit, IARC email address, override behaviour, appeal route, refused classification, territory blocking for minors, rating authorities; read 2026-11-15)
• Content Ratings policy — Play Console Help, Developer Program Policies (requirement for every app, removal of unrated apps, rating appeals; read 2026-11-15)
• Manage target audience and app content settings — Play Console Help (target audience declarations, prerequisites, Families policy; read 2026-11-15)
• Prepare your app for review — Play Console Help (App content declarations and their order; read 2026-11-15)
• Ad content rating and blocking controls — AdMob Help (ad filters matched to an app's content rating; read 2026-11-15)
• Rating icon display guidelines — International Age Rating Coalition (icon usage for advertising; read 2026-11-15)
• IARC developer contact — International Age Rating Coalition (non-appeal questions about ratings; read 2026-11-15)