Google Play's Closed-Testing Rule for New Developer Accounts
Short answer: If your Google Play developer account is a personal account created after November 13, 2023, you can't publish to production until you've run a closed test with at least 12 testers who have stayed opted in continuously for the previous 14 days. Then you apply for production access in Play Console and answer questions about the test, your app and its readiness; Google says review usually takes seven days or less. As of November 2026 the help page applies the rule to personal accounts; organization accounts, which require a D-U-N-S number, aren't covered by it.
The requirement, exactly as Google states it
From Google's Play Console Help article on testing requirements for new personal accounts (checked November 1, 2026):
- Who: developers with personal accounts created after November 13, 2023
- What: a closed test with a minimum of 12 testers
- How long: testers opted in continuously for at least 14 days, counted back from the day you apply
- Then: apply for production access from the Play Console Dashboard
- Until then: Production and Pre-registration remain disabled
Older blog posts and forum threads mention 20 testers. Go by the current help page, which says 12.
Does it apply to you?
Google's account-type guidance says to choose an organization account if you're developing for a business, and requires certain categories (such as financial services) to use one. Creating an organization account requires a D-U-N-S number, which Google notes is free to obtain from Dun & Bradstreet. If you're building an app for a company, an organization account is usually the right choice anyway, and the testing article doesn't apply to it. Don't open the wrong account type just to skip testing; account type affects what you're allowed to publish.
Step by step
1. Finish app setup
You can start a closed test after completing your app setup in Play Console: store listing basics, content rating, target audience, data safety and so on.
2. Create the closed test track
In Play Console, open the Testing section and set up a closed testing track. Upload a release build. Internal testing is useful for your own team but doesn't satisfy the requirement; it has to be a closed test.
3. Add testers
Google lets you manage closed testers in two ways:
- Email lists: you can create lists of tester email addresses (Google's limits are generous, up to 2,000 users per list)
- Google Groups: only members of the specified group can join; handy because people can join the group without you editing the list
Testers need a Google Account or Google Workspace account.
4. Share the opt-in link
Add a feedback URL or email address (it appears on the tester opt-in page), copy the shareable link and send it to testers. Each tester must open the link, accept the invitation, and install the app from Google Play. Being on your list isn't the same as being opted in.
5. Keep them opted in for 14 days
The count is about continuous opt-in. If testers leave and you drop below 12, you're effectively starting over. Plan for a margin: invite 15 to 20 people.
6. Collect real feedback
The application asks how engaged testers were: whether they used all the features, whether their usage matched what you expect in production, what feedback you got and how you collected it. A test where 12 people installed the app and never opened it makes this section hard to answer honestly.
7. Apply for production access
Dashboard > Apply for production. The form has three parts:
- About your closed test: how easy recruiting was, tester engagement, feedback summary
- About your app/game: target audience, value, expected installs in year one (Google says these answers aren't shown publicly)
- About your production readiness: what you changed after testing and how you decided the app was ready
8. Wait for review
Google says review usually takes seven days or less, and the result goes by email to the account owner. If more testing is needed, typical reasons Google lists are fewer than 12 opted-in testers or insufficient engagement.
How to recruit 12 real testers
- Your own circle first: colleagues, friends and family with Android phones
- Your future users: customers of an existing business, a waiting list, a community or club the app serves
- A small incentive: early access, a free month or a mention in release notes
- Give them tasks: a short checklist ("create an account, book something, cancel it") produces better feedback than "have a look"
- Use a feedback channel: a simple form or email address set as the feedback URL
Be wary of services that sell "testers". The application asks about real engagement and feedback, and testers who never use the app don't help you answer it.
Common mistakes
| Mistake | Result |
|---|---|
| Testers added to the list but never accepted the invite | Not counted as opted in |
| Testing on the internal track | Doesn't meet the requirement |
| Exactly 12 testers, one drops out on day 13 | Below the minimum when you apply |
| Applying on day 13 | Fewer than 14 continuous days |
| No feedback collected | Weak answers in part 1 of the application |
| Treating review as QA | Google warns that review isn't a troubleshooting step; policy problems lead to rejections and delays |
| Wrong account type for a business app | Problems later with policies that require an organization account |
Plan the timeline
A realistic minimum from finished build to public listing is about three weeks: a few days to recruit, 14 days of testing, and up to a week of review. Build it into your launch plan rather than discovering it the week before a marketing date.
FAQ
Can I keep updating the app during the closed test?
Yes. Pushing new builds to the closed track is normal, and changes made after feedback are exactly what part 3 of the application asks about.
Do testers have to be in a particular country?
Google's help page doesn't set a tester location rule, but your closed track's country availability affects who can install. Make sure your testers' countries are included.
Does this apply to every app I publish?
Google's article describes running a closed test for your app before that app can reach production. Check the Dashboard for each app; it shows whether production access is still locked.
What if my application is rejected?
Keep the closed test running, address the reasons given, increase engagement, and apply again.
Need an Android app tested and launched without the scramble? Tell us where your build stands.