App Store and Google Play Age Ratings: Answering the Questionnaires
Short answer: Both Apple and Google ask you to complete a questionnaire about your app's content and features, and the answers produce the age rating that customers see. Be literal about what your app does, not about what you intend it to be used for. Features that raise a rating include user-to-user chat, unfiltered user posts, web pages you show inside the app, simulated gambling, and content about violence or alcohol. Answer each question as if a reviewer will test the feature the same afternoon, because a wrong answer can lead to a rating that does not match the app, or to a review problem after launch.
What the rating is for
An age rating tells customers, parents and app stores whether the content suits the people who will download it. It is not a judgement of quality. A booking app for a dog groomer and a fitness app for adults can both be rated for everyone, while a social app for neighbours might need a higher rating simply because strangers can message one another.
The questionnaires look similar on both platforms, but they produce ratings in different systems. Apple shows a tier based on its own questions. Google's answers pass through the International Age Rating Coalition, usually called IARC, which issues ratings for several regions from one set of answers. You complete the form once per store, and the store does the rest.
Features that change the rating
Go through your app screen by screen and mark anything from this list:
- User-to-user chat or messaging, including comment threads and direct messages between customers.
- User-generated content that other people can see, such as reviews, photos or profile pages.
- Web views, where the app shows a website inside itself. The rating depends on what the website may show, which you cannot fully control.
- Gambling or simulated gambling, such as prize draws, loot boxes or random reward wheels.
- Mature themes such as violence, alcohol, drugs or sexual content, including text, images and sound.
- Location sharing with other users, which is a safety matter even if the rating is not directly affected.
A simple example: a small restaurant app shows the menu, takes orders and links to the restaurant's reservation page in a web view. It has no chat and no user posts, so the rating is usually low. If the same app adds a "message the chef" feature, the rating and the moderation rules change, because the app now carries messages written by people you do not control.
Answering the questionnaire
Work through the form in this order:
- List every screen and feature in a spreadsheet, including the parts you have not yet launched.
- For each feature, note whether users can see content created by other users, and whether they can send messages to one another.
- Check the web views and any embedded content, and note whether they open external sites.
- Answer the questions on violence, sexual content, substances and gambling against the actual content, including sample images and text in the app.
- Save the answers, then preview the rating and check that it matches your expectations.
Answer for the app as it is now, and as it will be at launch. If you plan a chat feature for the next version, complete the questionnaire again when that version is ready, rather than launching with a rating that no longer matches.
What a wrong answer risks
A wrong answer carries two kinds of risk. The first is a rating that understates the content. That can lead to complaints from parents or customers, and a store may remove the app or ask you to correct the rating. The second is inconsistency between your answers and what reviewers find in testing. Reviewers do test features, and a chat function that was not declared can cause a rejection or a request for more information.
Overstating the content is also a mistake, though a less harmful one. A rating that is too high can limit your audience, and it can make a family-friendly app look restricted when it is not.
Correcting a rating after launch
If you realise after launch that an answer was wrong, correct it in the questionnaire and save the change. The updated rating usually applies once the store processes it, which can take time. Mention the change in your next version notes if the content has changed, and keep a record of the answers you gave and the reason.
Do not wait for a complaint. A proactive correction is far easier to explain than a takedown notice.
Review issues to check
Ratings and review guidelines overlap. If your app has user content, the store will also expect moderation tools, such as a way to report content, block users and contact you about abuse. Check the current App Review guidelines on Apple's developer site, and the Google Play policies in the Play Console help, because both require these tools in some cases.
Steps for a small app team
- Map every feature that involves other users or external content.
- Decide what the app will do at launch, and answer for that version only.
- Complete the questionnaire on each store, one answer at a time, with the feature list open.
- Check the preview rating against your intended audience.
- Add a rating review to your release checklist for any version that adds a feature.
FAQ
Is a chat feature always a reason for a higher rating?
It is a common reason, and it also affects moderation requirements. The exact rating depends on the answers to the whole questionnaire, so a chat feature alone does not settle it.
Can I rate my app for everyone if I restrict who can join?
Restrictions do not change the answers about the content and the features. Answer for what the app does, and describe the restrictions in your listing and terms.
Does a web view affect the rating?
It can. The rating reflects what the external site may show, and you cannot fully control a third party's content. Keep web views limited to sites you trust, and say so in your answers.
What if the store rejects my rating?
Read the reason, correct the answers that do not match the app, and resubmit. If the reason is unclear, contact the store's developer support and ask which answer caused the issue.
If you would like us to walk through your app's features and prepare the questionnaire answers with you, tell us what your customers can do inside the app and we will help you complete it: contact us.