To publish on Google Play, create a Play Console developer account (a one-time $25 fee plus identity verification), create the app, upload a signed Android App Bundle, and complete the store listing and the App content declarations. Then test on a testing track and roll out to production. New personal accounts must first run a closed test with at least 12 testers for 14 days before they can apply for production access.
Choose the right account type before anything else
Play Console offers personal and organization developer accounts, and the choice matters more than most first-time publishers expect. An organization account needs a D-U-N-S number and verified business details, but it is exempt from the closed-testing requirement for new personal accounts. Google also expects apps in certain regulated categories, such as financial services, health, and VPNs, to come from organization accounts. If you are a company, register as one from the start rather than migrating later.
Whichever type you choose, the developer name appears publicly on your listing and in search, so treat it as a brand asset. Use the name users will recognize, keep contact details accurate, and expect identity verification to take anywhere from a few days to a couple of weeks. Starting verification early is the simplest way to avoid a launch-week bottleneck.
Prepare a build Google Play will accept
New apps must be uploaded as Android App Bundles (AAB), not APKs, and most teams enroll in Play App Signing so Google manages the distribution key while you keep an upload key. Pick your package name carefully, because it is permanent once you publish: it becomes the app's ID in the Play Store URL and cannot be changed or reused.
Google also enforces a minimum target API level for new apps and updates, typically within a year of the latest Android release. Check the current requirement in the Android developer documentation before you build, and run the pre-launch report on a testing track. It installs your app on real devices and flags crashes, accessibility problems, and security warnings before reviewers or users find them.
Build a store listing that ranks and converts
The main store listing has three text fields: an app name of up to 30 characters, a short description of up to 80, and a full description of up to 4,000. All three are indexed for search on Google Play, so they deserve real Google Play keyword research rather than a last-minute paste from your website. The short description is especially valuable because it sits right under the screenshots; our guide to writing the Google Play short description covers proven patterns.
Graphics carry most of the conversion weight. You need a 512 x 512 icon, a 1024 x 500 feature graphic, and at least two screenshots, with at least four high-resolution screenshots recommended so the app is eligible for more promotional surfaces. Our Google Play screenshot sizes and asset specs guide lists every dimension, and the feature graphic guide explains how to design the banner that frames the listing.
Complete the App content declarations honestly
Before you can publish, Play Console asks you to complete the App content section: a privacy policy URL, app access instructions for reviewers, an ads declaration, the IARC content rating questionnaire, target audience and content, and the Data safety form. Apps in some categories, such as finance, health, news, or government, have extra declarations. Each answer must match what the app really does, and mismatches are one of the most common reasons for rejection.
Treat the Data safety form as a product document, not a checkbox. It is shown to users on the listing and can affect conversion, and it must account for data collected by third-party SDKs as well as your own code. Our guide to privacy labels and Data safety explains how to keep it accurate, and the age rating guide shows how content ratings affect reach.
Use testing tracks, including the 12-tester rule
Play Console has three testing tracks. Internal testing reaches up to 100 testers and is available almost immediately, which makes it ideal for fast QA. Closed testing reaches a list of email addresses or a Google Group, and open testing lets anyone join from the store listing. Builds on testing tracks can still be reviewed, so keep them policy-compliant.
If you created a personal developer account after November 13, 2023, you must run a closed test with at least 12 testers who stay opted in for at least 14 continuous days before you can apply for production access. You then answer questions about the test and what you changed. Our dedicated guide to the Google Play closed testing requirement explains how to recruit testers who give useful feedback instead of simply meeting the count.
Release to production and understand review
When you create a production release, you choose the countries and regions, add release notes, and decide whether to roll out to everyone or start with a percentage. A staged rollout limits the damage from a bad build, and our guide to staged rollouts and ratings protection shows how to use percentages safely. Managed publishing lets you hold an approved release and publish it at a time you choose, which is useful for coordinated launches.
Google says most reviews complete within a few days but some can take seven days or longer, especially for new developer accounts, sensitive permissions, or apps in regulated categories. Plan a buffer of at least a week for the first submission, and read our guide to app review times for ways to avoid delays.
Why first submissions get rejected
The most common problems are predictable. Reviewers cannot log in because test credentials are missing or expired. The Data safety answers do not match what an SDK collects. The listing uses restricted words such as best or number one in the title, or the screenshots show functions the app does not have. Sensitive permissions such as SMS, call log, background location, or all-files access are requested without an approved use case.
Each of these is avoidable with a pre-submission checklist. Walk through the app as a reviewer would, starting from a fresh install, and confirm that every claim in the listing is visible in the product within a minute or two. Our white hat vs black hat ASO guide covers the metadata practices that keep listings safe.
What to do in the first 30 days after launch
Publishing is the start of ASO, not the end. In the first month, watch Android vitals for crash and ANR rates, read every review, and compare store listing visitors with installers in the Google Play Console store performance reports. Stability problems at launch can depress both ratings and visibility, which is why crash rate is an ASO metric.
Once you have steady traffic, run store listing experiments on the icon, screenshots, and short description, one change at a time. Use the app launch ASO checklist to make sure nothing important was skipped during the rush to ship.
How to do it, step by step
- Register and verify a developer accountChoose personal or organization, pay the one-time $25 registration fee, and complete identity verification. Organizations need a D-U-N-S number, so request one early if you do not have it.
- Create the app and lock the package nameIn Play Console, create the app, set the default language, and confirm whether it is an app or game and free or paid. Double-check the package name in your build, because it cannot be changed after publishing.
- Upload a signed App Bundle to internal testingEnroll in Play App Signing, upload the AAB to the internal testing track, and review the pre-launch report for crashes and warnings before inviting anyone else.
- Finish the store listing and App contentWrite the name, short description, and full description, upload the icon, feature graphic, and screenshots, then complete every App content declaration, including Data safety and the content rating.
- Run the required closed test if it appliesNew personal accounts need 12 or more testers opted in for 14 continuous days. Collect feedback, fix issues, and document what you changed for the production access questions.
- Create a production release with a staged rolloutSelect countries, add release notes, start with a small rollout percentage, and expand only when crash rates and early reviews look healthy.
Before and after examples
Illustrative examples written for a generic app in this category, not client results. Swap in your own product, audience, and data.
Best Budget App - #1 Free Money Tracker
Pennywise: Budget & Bill Planner
Why it works: Google Play metadata policy restricts terms like best, #1, and free in titles. A brand plus a clear keyword phrase is compliant and still descriptive.
Login required.
Use demo account review@example.com / password Review2026. Sample data is preloaded. The premium tab is unlocked for this account.
Why it works: Reviewers who cannot reach the core features will reject the app. Specific credentials and notes remove the guesswork.
The ultimate app for all your needs. Download now!
Track spending, plan bills, and get reminders before payments are due.
Why it works: It states concrete benefits with natural keywords instead of vague hype or a call to action.
Action plan
- Register as an organization if you are a company
- Start identity verification at least two weeks before launch
- Lock the package name and enroll in Play App Signing
- Write metadata from keyword research, not the website
- Complete Data safety including all SDK data collection
- Plan for the 14-day closed test on new personal accounts
- Launch with a staged rollout and watch vitals daily
Metrics to monitor
- Time from first submission to approval
- Pre-launch report crash and warning count
- Store listing visitor to installer conversion
- User-perceived crash and ANR rates
- Average rating in the first 30 days
Record the baseline, release date, audience, markets, and external changes before interpreting movement. Rankings and conversion are useful signals, but a decision is stronger when activation, retention, and business value confirm that the page attracted the right users.
Frequently asked questions
How much does it cost to publish an app on Google Play?
Registering a developer account costs a one-time $25 fee. There is no annual renewal. Google takes a service fee on paid apps and in-app purchases, covered in our guide to App Store and Google Play fees.
How long does Google Play review take?
Many reviews finish within a few days, but Google says some take seven days or longer. New accounts, sensitive permissions, and regulated categories tend to take longest, so plan at least a week for the first submission.
Do I need 12 testers to publish on Google Play?
Only if you have a personal developer account created after November 13, 2023. Those accounts must run a closed test with at least 12 opted-in testers for 14 continuous days before applying for production access. Organization accounts are exempt.
Can I change my app's package name after publishing?
No. The package name is permanent and cannot be reused, even if you unpublish the app. Changing it means publishing a new app with new reviews and rankings.
Do I need a privacy policy for a Google Play app?
Yes. Google requires a privacy policy link in Play Console, and its contents must match your Data safety declarations and what the app and its SDKs actually do.
Keep reading
Go deeper on this topic
More in Platform Guides
Browse all 9 Platform Guides guides
Work with ASOWin
Primary sources
Platform capabilities and limits can change. Verify current requirements in these official resources:
