Guide · 9 min read
App Content Rating Questionnaire: 7 Mistakes That Restrict Your Distribution
Most developers fill out the content rating questionnaire in under two minutes without reading the questions carefully — it looks like a formality. It isn't. Your answers control which storefronts carry your app, whether parental controls hide it, and whether it qualifies for editorial featuring. Both Apple and Google treat wrong answers as misrepresentation, and the consequences can be account-level. Here's what every question category actually affects and where indie apps consistently get it wrong.
What the content rating questionnaire actually controls
Your content rating determines where your app is distributed, whether parental controls filter it from view, whether managed devices (school iPads, enterprise MDM deployments) can install it, and whether Apple or Google considers it for editorial featuring — four outcomes most developers don't realize are linked to a form they filled out in 90 seconds. A 17+ or 18+ rating excludes an app from educational categories and Apple's Today tab. A miscategorized rating silently blocks family sharing purchases, parental control exceptions, and cross-device automatic installs.
Both Apple and Google use self-reported questionnaire answers rather than independent content analysis to generate ratings. The IARC (International Age Rating Coalition) framework sits beneath both stores, and its member organizations — ESRB, USK, PEGI, ClassInd, and others — can trigger post-publish audits when user complaints or category mismatches flag a listing. These audits don't always arrive as a warning: sometimes the outcome is a forced reclassification or removal with no prior notice.
For first-time App Store submissions, the questionnaire is part of the same metadata block you complete alongside category selection and privacy declarations — the full stack is covered in the App Store Connect first-time submission guide. Most new developers complete it at the moment their attention is divided most, treating it as a checkbox rather than a distribution decision.
Apple's 2025 overhaul: the new 13+ and 16+ tiers change what "safe" means
Apple replaced its four-tier rating system (4+/9+/12+/17+) with five tiers in 2025: 4+, 9+, 13+, 16+, and 18+. The 12+ and 17+ tiers were removed. Apps previously rated 12+ were automatically reassigned to 9+ or 13+ during the transition, but all developers were required to answer the updated questionnaire by January 31, 2026 to avoid submission interruptions on future updates. If you haven't revisited your questionnaire since before that deadline, your current rating may not reflect how your app would be rated under the new questions.
The new 13+ tier is where most misratings now land. It covers apps with moderate cartoon violence, mild mature themes, simulated gambling without real money, and — critically — apps that allow users to contact strangers. Any social or messaging feature, even a minimal community section or public comment thread, almost always produces a 13+ rating under the revised questions. Under the old 12+ bracket, the same feature would have been borderline; under the new system it's a clear trigger.
The 16+ tier applies to apps with realistic violence, sexual references, and simulated gambling that approaches real-money mechanics. Very few non-game indie apps intentionally target this tier, but apps with WebView components rendering external content — news aggregators, Reddit clients, social platform wrappers — can hit it automatically if underlying content is flagged. The common App Store rejection reasons include Guideline 1.3 content misrepresentation, which is the enforcement path when a review team and a questionnaire answer are in conflict.
Under-disclosing: the mistake with account-level consequences
Under-disclosing — declaring a lower rating than your app's content warrants — is treated as deliberate misrepresentation by both Apple and Google. On Google Play, this can result in app removal and developer account termination, not just a rejection. Apple's App Review Guideline 2.3.6 is explicit: honest answers are required, and a developer who misrepresents content to obtain a lower rating can lose their developer account across all apps. The enforcement is account-level, not app-level.
Most under-disclosures aren't intentional. The questionnaire includes questions about simulated gambling even for productivity apps — an app with a 'spin to earn a bonus' onboarding mechanic counts. It asks about cartoon violence even for apps with action-game-style animations. It asks about mature themes even for health apps that discuss eating disorders or substance recovery in an educational context. Answering 'no' because you don't think of your app as a gambling or violence app is the most common path into an under-disclosure.
When IARC or a rating authority audits and finds a mismatch, the standard first step is a request to retake the questionnaire. If the developer corrects the rating and the app stays within the permitted content category, it stays live under the revised tier. But if the correction moves the app into a category that contradicts a previous submission claim — or if the developer account carries prior policy strikes — the outcome escalates. Treat the questionnaire as a compliance decision with real distribution consequences, not a marketing one.
6 question categories where indie apps get it wrong most often
Simulated gambling: Any mechanic where users receive randomized rewards for real or virtual currency — loot boxes, spin-the-wheel bonuses, randomized subscription perks — falls here. Most apps with gamification layers need to answer yes. User-generated content: Any surface where users can post, share, or display content visible to others — even a public notes export feature — may qualify. The question is about capability, not observed use. Social features and stranger contact: A direct messaging feature, a public comment section, or a community tab counts as 'ability to interact with strangers,' which is a 13+ floor under Apple's revised system.
Location tracking: Apps that share user locations with other users (not just collecting location for analytics) are flagged here. The question targets capability, not privacy intent — a 'share my location with friends' feature qualifies even when opt-in. Medical or wellness content: Apple added this category explicitly in 2025. Apps covering eating disorders, substance use, sexual health, or self-harm must flag this even when the content is clinical and professional. In-app purchases with randomized outcomes: A separate trigger from simulated gambling — if any IAP produces a randomized result for the buyer (a random theme, a mystery subscription perk), this category applies regardless of whether money is involved or the stakes are trivial.
The practical test: go through each questionnaire question and ask whether your app could trigger that category under any user path, not whether it does routinely. The questionnaire is evaluated for capability, not frequency. An app that exposes simulated gambling in a single promotional screen still answers yes to the gambling question even if 95% of users never see that screen.
Ad networks, WebViews, and SDKs: the hidden content rating inputs
Ad networks can and do serve ads with content above your app's declared rating — and when they do, that content is attributed to your app. A 4+ rated utility app running a broad behavioral ad network has no contractual guarantee that those ads will never show gambling, dating, or alcohol content. Both Apple and Google treat ads served inside your app as part of your app's content for rating purposes. The practical consequence: a 4+ app with an ad SDK is vulnerable to rating reclassification triggered by user complaints about the ads themselves, not the app's own screens.
Third-party SDKs introduce tracking and social features that activate questionnaire triggers independently of your own code. A social login SDK adds a contact-with-strangers pathway. An analytics SDK with behavioral profiling may affect privacy label responses — which the questionnaire now cross-references. The same honest-answer principle that applies to Apple's App Store privacy nutrition labels applies to the rating questionnaire: declare what your SDKs do, not just what your own code does.
The mitigation for ad content is choosing networks that offer category-safe targeting. Google AdMob's Max Rating content filter lets you restrict served ads to your declared rating tier. Meta Audience Network and Apple's ad framework have equivalent controls. Implementing content filters typically takes under an hour per SDK and eliminates the most common path to an unexpected rating escalation from third-party ad content. WebView apps should implement a URL allowlist and content policy at the rendering layer before declaring a rating lower than 13+.
5 update types that require you to redo the questionnaire
Google Play requires retaking the content rating questionnaire whenever an app adds: real-money gambling mechanics, user-generated content surfaces, direct messaging or social features, randomized reward systems, or a significant expansion of ad network integrations. Apple's equivalent requirement is any update that changes content in a way that would affect questionnaire answers — including switching ad networks or adding a WebView to a previously native app. Neither store reliably prompts you to redo the questionnaire when these triggers fire; you have to know to do it.
The most commonly missed trigger is monetization model changes. Moving from a free app to a freemium model with any IAP requires revisiting the questionnaire — particularly if any part of the purchase flow involves randomization. A 'mystery unlock' IAP, a random avatar selection on purchase, or even a randomized welcome message after a subscription conversion can qualify. Most developers who switch monetization models redo their screenshots and analytics tracking setup but skip the content rating update entirely.
A practical cadence: include a content rating review in your feature launch checklist for any sprint that ships social, monetization, ad, or WebView changes. The ASO metadata quarterly audit checklist can be extended to include a content rating confirmation step — it takes five minutes to verify and the consequences of skipping it are disproportionately large relative to the time cost.
Appeals: what to do when your rating is wrong
If a rating authority initiates a review and assigns a higher tier than you believe your content warrants, both Apple and Google provide appeal paths. On Google Play, you retake the questionnaire with corrected answers and Google routes the case to the relevant IARC member authority. Resolution typically takes 5–7 business days for content that is clearly below the disputed threshold, and most well-documented appeals for borderline educational or medical content are decided in the developer's favor.
Apple's process runs through the App Store Connect Resolution Center — the same channel used for standard review rejections. Provide a section-by-section justification for each questionnaire answer you believe was read incorrectly, with screenshots of the specific in-app content in question. Reference the actual content, not the intent. Never submit an app update while an appeal is pending: a new submission during active review resets the review clock and can invalidate the appeal thread.
Build a compliant store listing →
Frequently asked questions
what happens if i get the content rating questionnaire wrong?
Both Apple and Google treat wrong answers as misrepresentation under their developer agreements. On Google Play, deliberate under-disclosure can result in app removal and account termination. Apple's Guideline 2.3.6 covers the same territory. Accidental misratings typically resolve through a questionnaire correction and reclassification, with the app staying live during a cooperative review. Deliberate or repeat violations escalate to account-level enforcement.
does the content rating questionnaire affect app store search ranking?
Indirectly, yes. A higher rating tier restricts your app from appearing in searches filtered by parental controls, excludes it from family sharing purchases, and blocks it from certain editorial featuring slots. Apps rated 13+ or above are filtered out on supervised devices and excluded from Apple's Kids category. These filtering effects reduce effective search impressions without changing keyword ranking position directly — the practical result is lower install volume for a given ranking.
does a webview app get a different content rating?
The same questionnaire applies, but the answers differ. A WebView app is rated for what the underlying content could display, not just what the native app code does. If the rendered site could legally serve graphic news imagery, user-generated content, or behavioral ad targeting, those factors belong in your rating answers. The safest approach is to rate a WebView app for the worst content the site could surface, unless a technical content filter is in place at the rendering layer.
how often should i retake the content rating questionnaire?
Retake it at every major feature launch that adds social, monetization, ad network, or WebView changes — and whenever you switch monetization models. Google Play Console shows a content rating alert when automated review detects a likely mismatch, but this trigger is not reliable. A practical rule: add a content rating confirmation step to every sprint checklist that ships a feature touching social interaction, randomized rewards, or third-party content rendering.
can an app be removed from the app store for a wrong content rating?
Yes. Google Play can remove an app for content rating misrepresentation and in serious cases terminate the associated developer account. Apple can reject an update, remove the app from sale, or issue a policy strike against the developer account. Both stores distinguish between accidental misrating (typically resolves with a correction) and deliberate under-disclosure (triggers enforcement). A rating authority can also initiate a review independently based on user complaints, without the store prompting it.