Google Play Content Ratings for TWA Apps

When preparing to publish your Trusted Web Activity (TWA) on the Google Play Store, you must complete the target audience and content rating questionnaires in the Google Play Console. This process uses the International Age Rating Coalition (IARC) system, which dynamically generates age ratings for different regions, such as PEGI in Europe, ESRB in North America, and ClassInd in Brazil. Because a TWA is structurally a wrapper around your Progressive Web App (PWA), developers often struggle to answer questions designed for native Android applications. Answering incorrectly can lead to an artificially high age rating, store rejection, or eventual suspension.

The Core Objective of the IARC Questionnaire

The IARC questionnaire is designed to determine if your application contains content that is inappropriate for certain age groups. For a native app, this content is baked into the code and local assets. For a TWA, the content is delivered dynamically from your web server. Google requires you to rate your app based on the maximum potential exposure a user might have within your application. However, you do not need to assume worst-case scenarios for general web access unless your app functions as an open-ended web portal.

Key Questionnaire Sections and How to Answer Them for TWAs

The Play Console breaks the content rating process down into several clear categories. How you respond depends directly on your web application's functionality. Below are the most critical sections you will encounter when rating a web-to-app conversion.

User-Generated Content and Social Features

If your PWA includes comment sections, forums, chat rooms, or direct messaging, Google classifies this as User-Generated Content (UGC). The questionnaire will ask: Does the app natively allow users to interact or exchange content with other users through voice, text, or images?

If your web app is a closed SaaS platform, an e-commerce storefront, or a single-player game with no social layer, you should answer No. If you answer Yes, you must ensure that your PWA implements robust moderation tools, user-blocking mechanisms, and abuse-reporting features. Failure to have these web-based moderation tools visible to Google reviewers during the testing phase will result in an immediate rejection under the UGC policy.

Physical Location Sharing

The questionnaire asks if your application shares the user's physical location with other users. If your web app uses the Geolocation API to show nearby physical stores, local weather, or delivery tracking, this is considered local usage. You only need to answer Yes if your PWA actively transmits and displays the user's real-time coordinates to other app users, such as in a social mapping or ride-sharing environment.

Digital Purchases and Financial Transactions

You will be asked: Does the app allow users to purchase digital goods? This is a crucial point of confusion. If your PWA processes payments for physical goods, physical services, or subscriptions managed outside the app via Stripe, Lemon Squeezy, or similar web payment gateways, this does not count as digital purchases in the context of Google Play's native billing. However, if you are selling digital features, premium access, or virtual currency that bypasses Google Play's billing library where Google Play rules require it, answering incorrectly here can flag your application for compliance reviews. Ensure your answer matches your payment implementation strategy.

The Web Browser Trap

The most common and costly mistake TWA developers make occurs when answering the following question: Is the app a web browser or search engine?

Because a TWA loads web pages from a remote origin, developers often assume they must answer Yes. This is incorrect. Answering yes indicates to the Play Console that your application is a general-purpose tool designed to navigate to any URL on the internet. If you answer yes, your application will receive a 17+ or 18+ age rating in almost all jurisdictions, and you will be forced to comply with strict safety policies designed for browser engines.

A TWA is scoped to a specific domain (and its verified subdomains) via Digital Asset Links. Because users cannot type arbitrary URLs into your app to browse the open web, your app is categorized as a dedicated client application, not a web browser. You should answer No to this question.

Mapping Questionnaire Answers to App Types

The table below provides a reference mapping for common types of PWAs converted to Android apps via TWAs, illustrating how to approach key rating questions.

Handling Content Rating Updates When Your PWA Changes

One of the major benefits of a TWA is that you can deploy updates to your web app instantly without submitting a new APK or AAB to the Google Play Store. However, you must remain mindful of your content rating. If you introduce new features to your web frontend that alter your answers to the content rating questionnaire, you are legally and contractually obligated to update your rating inside the Play Console.

For example, if your PWA was originally a simple content portal and you subsequently introduce a public forum or user-to-user messaging system, you must log in to the Play Console, navigate to the Content Rating section, and fill out a new questionnaire. Google's automated systems and manual reviewers periodically audit published apps. If they detect a discrepancy between the web content served in your TWA and the declared rating parameters, your app may be temporarily removed from the store until a new rating is established.

Final Checklist for TWA Content Rating Success

• Do not classify your scoped TWA as a web browser.
• Declare location sharing only if coordinate data is actively distributed to other users.
• Ensure web-based moderation tools are fully operational on your frontend before submitting if your app features user-to-user communication.
• Align your digital purchase declaration with Google Play's billing policies to avoid compliance audits.
• Re-evaluate and update your rating in the Play Console whenever your PWA introduces major structural changes.