Google Play Developer Account Verification: A Simple Guide
Personal or organization account, the details you need and what to do once you are verified.
Read the guide →How to Publish an App on Google Play for the First Time
Quick answer To publish an app on Google Play for the first time, set up your developer account, finish app setup, run a closed test (12 testers, 14 days), apply for production access and roll out your release.
Publishing your first Android app on Google Play has more steps than most people expect, especially on a new personal account. This guide gives you the full path in order, from creating your developer account to rolling out your first release, with links to detailed guides for each hard step.
What are the steps to publish an app on Google Play?
- Create and verify your developer accountPersonal or organization. See our account verification guide.
- Create your app and complete app contentStore listing, privacy policy and Data safety form.
- Run a closed testNeeded for personal accounts created after November 13, 2023.
- Apply for production accessComplete the questionnaire on the Dashboard.
- Roll out your production releaseClick Release to publish.
1. Set up your developer account
Choose between a personal and an organization account. Organization accounts need a D-U-N-S number, and Google requires an organization account for some app types, such as financial services, health and government apps. Read our verification guide for details.
2. Create and set up your app
In Play Console, create your app and fill in the store listing and the app content declarations. Before you submit, Google expects accurate app information, a privacy policy and the Data safety section, plus demo account details if your app needs a login. The privacy policy and data safety form trip up many developers, so read our guide to the Data safety form and privacy policy.
3. Run the closed test
New personal accounts must run a closed test with at least 12 testers opted in for 14 days. Learn the rules in the closed testing requirements checklist, find testers with our guide on getting 12 testers, and add them using the step-by-step guide to adding testers.
4. Apply for production access
When your 14 days are complete, click Apply for production on the Dashboard and answer the three-part questionnaire. Our step-by-step guide explains each question. If it is not approved, see what to do next.
5. Roll out your release
Once you can release to production, create the production release, check the release review summary and click Release. Google says that at the end of the release process, clicking Release also publishes a draft app. If the summary shows errors, you must fix them before you can publish. Warnings do not block publishing but should be addressed. Details are on Google's publishing status page. If your first release is rejected, read app rejection reasons and fixes.
Pre-launch checklist
- Your app installs and runs on real devices.
- The store listing text and images are accurate.
- The privacy policy is public and matches your data practices.
- The Data safety form is complete.
- Demo account details are ready if reviewers need to sign in.
- The closed test has run for 14 days with at least 12 testers opted in.
- Your production access application is approved.
- The release review summary shows no errors.
How long does the whole process take?
For a personal account created after November 13, 2023, plan for at least 14 days of closed testing, plus the time Google takes to review your production access application, which it says is usually seven days or less. Add time to prepare the listing, privacy policy and testers. Starting your closed test early is the easiest way to shorten the overall timeline.
Part of a series: this article is one chapter of Google Play Closed Testing: The Complete Guide. Start there for the full roadmap from setup to production.
What to plan for in time and money
| Item | Typical planning note |
|---|---|
| Developer account | A one-time registration fee. Check Google's current fee when you register. |
| Verification | Allow time for identity checks. See the verification guide |
| Closed test | At least 14 days, plus time to recruit testers |
| Production access review | Usually seven days or less per Google. See the timeline |
| Store listing assets | Icon, screenshots, description, privacy policy |
The mistakes first-time publishers make
- Starting the closed test last-minute when it takes 14 days anyway.
- Skipping the privacy policy and Data safety form. See the Data safety guide.
- Using exactly 12 testers. See how many to recruit.
- Ignoring rejection notices. See app rejection reasons.
A realistic four-week plan
| Week | Focus |
|---|---|
| 1 | Account, verification, app setup, listing, forms |
| 2 | Closed test begins, testers opted in |
| 3 | Closed test finishes, application submitted |
| 4 | Review, production release, rollout |
Frequently asked questions
How long does it take to publish a first app on Google Play?
It depends on the account type and review. Personal accounts created after November 13, 2023 first need a 14-day closed test with at least 12 testers. Google may also take up to seven days or longer in exceptional cases to review some accounts.
What happens when I click Release?
Google says that at the end of the release process, clicking Release also publishes a draft app.
What if the release review shows errors?
You cannot publish until the errors in the errors summary are resolved. Warnings alone do not block publishing, but Google recommends addressing them.
Do I need a privacy policy?
Yes. A privacy policy is required to complete the Data safety form. See our guide on the Data safety form.
