What Play Console requirements must I complete before submitting an app for review?

What Play Console requirements must I complete before submitting an app for review

Complete the Play Console setup that Google uses to evaluate your app before you ask for review. The core items are App content, Data safety, target audience and content, content rating, privacy policy, permissions declarations, app access instructions, and the required testing path for your account type. Google says these items are part of preparing an app for review, and they must be accurate and current.

Start with the App content page. Google uses it to collect policy declarations and other review details, including whether the app contains ads, the app’s target audience, privacy and security practices, and any special access instructions for reviewers. If your app uses sensitive permissions or data, the privacy policy must be on an active URL, apply to the app, and also appear in the app itself when required.

The part people get wrong is access. If reviewers cannot reach the main features, the submission stalls or gets rejected. Google asks for instructions when app access is restricted, and the permissions review flow also asks for a way to demonstrate the core functionality, plus a video when needed. If some features require sign-in, include exact steps for reviewer access and avoid leaving the reviewer to guess credentials, demo paths, or hidden menus.

Data safety is not optional. Google says every developer must complete the Data safety section in Play Console, and the information must match how the app actually collects, shares, and protects data. Keep the answers aligned with the code and the store listing. If your app changes its behavior later, update the declarations before the next submission, not after a reviewer finds the mismatch.

Target audience and content also need to be filled out before review. Google checks whether the disclosed audience is accurate and whether the app follows the relevant policy rules for that audience. If your app includes children in any target audience group, extra Families policy rules apply, and Google requires a privacy policy on the store listing and in the app. The common failure here is picking an audience that is broader than the app really supports.

Permissions and sensitive APIs need a separate declaration when the app asks for restricted access. Google says the permission request must match the app’s core functionality, and the request must make sense to users. For certain permissions, Google also expects instructions for access and a video demo so the review team can evaluate the feature. If the permission is not essential to a current, visible feature, remove it before submission instead of hoping the review will pass.

Content rating comes from the questionnaire in Play Console, and it has to be completed before the app can move through review. Google uses it to classify the app and the ads served in it. Answer the questionnaire based on the real content in the app, not the intended audience or the brand positioning. Mismatched answers here often create a second review round because the store listing and the questionnaire do not line up.

The testing requirement is the part that blocks new personal accounts most often. Google says personal developer accounts created after November 13, 2023 must complete a closed test path before they can apply for production access. The current requirement is at least 12 testers opted in continuously for 14 days, and internal testing does not count toward that closed-test requirement.

Do not try to buy testers or installs to move faster. Google says incentivized and inauthentic engagement can trigger enforcement, and that can put the developer account at risk. Use real testers who actually install, opt in, and keep the test active for the full window. If your count drops below the required level, the clock restarts, so the practical job is recruiting more than the minimum and keeping them engaged.

Internal testing is useful for debugging, but it is not a shortcut to production readiness. Google allows internal tests and says they support a different testing stage, yet they do not satisfy the closed testing requirement for new personal accounts. If you need a clean path, keep internal testing for quick fixes and use the closed test to satisfy the production-access gate.

A practical submission checklist looks like this: complete App content, finish Data safety, set target audience and content, answer the content rating questionnaire, publish a privacy policy where required, declare sensitive permissions, add reviewer access instructions, and verify the required testing track is active. If your app is gated by login, test the reviewer path yourself before you submit. If you want a simple place to organize testers and feedback, use your own workflow and keep it on property you control, such as DevConnect at https://devconnectplatform.com.

When submission fails, the fix is usually not more text. It is usually one missing declaration, one inconsistent answer, or one inaccessible screen. Review the App content page again, check the live app against the store listing, and verify that every access path works from a clean account. That is the difference between a first-pass review and another round of delays.