Google Play Store Listing Checklist: Everything You Need Before You Publish

Between the closed testing requirement, the data safety form, and the actual app build, your store listing is easy to leave for last, right up until the Play Console blocks your release because something's missing. Here's the complete list, in the order Google actually asks for it, so you can knock it out in one sitting instead of hunting for missing pieces at the worst possible time.

App identity

• App name. 30 characters max, shown under your icon everywhere on the Store. Keep it recognizable and avoid keyword-stuffing, Google has cracked down on names that cram in search terms.
• Short description. 80 characters, shown in search results and category listings. This is effectively your ad copy, write it like one.
• Full description. Up to 4,000 characters, shown on the full listing page. Lead with what the app does and who it's for in the first two sentences, since that's what shows before "read more."

Visual assets

• App icon. 512x512 PNG, no transparency, no rounded corners baked in (Google applies its own mask).
• Feature graphic. 1024x500, shown at the top of your listing and sometimes in Store promotions. This is more visible than most developers expect.
• Phone screenshots. Minimum 2, Google recommends 4-8. Use real screens, not just marketing mockups, since misleading screenshots are a policy violation, not just a bad look.
• Tablet and other device screenshots. Optional but recommended if your app supports those form factors; Google surfaces device-appropriate screenshots automatically when available.

Classification and policy items

• Category. Pick the closest match; miscategorized apps get flagged in review and can be manually reassigned by Google, which is worth avoiding.
• Content rating questionnaire. A detailed set of questions about violence, language, and content that generates your official age rating. Answer accurately; understating content here is a policy violation.
• Target audience and content. Whether your app targets children, which triggers additional Families Policy requirements if so.
• Data safety form. Covered in full detail in our plain-English walkthrough, but the short version: declare everything your app and its SDKs actually collect.
• Privacy policy URL. Required for every app, even simple ones with no data collection. Free generators exist, but read what they actually produce and make sure it matches your real practices.
• Ads declaration. Whether your app shows ads, required regardless of whether you think it's obvious.

Pricing and distribution

• Free or paid. Free-to-paid can't be reversed once set, so decide deliberately.
• Countries and regions. Where your app is available. Defaulting to all countries is fine for most apps, but review this if you have region-specific content or compliance concerns.
• Device categories. Phone, tablet, Wear OS, Android TV, Chromebook, whichever your app actually supports and has been tested on.

The step everything else depends on: closed testing

None of the above gets your app to Production on its own if you're on a new personal developer account. You'll still need to clear the 12-tester, 14-day closed testing requirement first, covered start to finish in our complete setup guide. A common mistake is polishing every listing detail while treating testing as an afterthought, when it's actually the longest and most failure-prone part of the whole process.

A pre-submission checklist you can actually use

1. App name, short description, and full description written and proofread
2. Icon, feature graphic, and at least 4 screenshots uploaded
3. Category and content rating questionnaire completed
4. Data safety form filled out accurately, cross-checked against your actual SDKs
5. Privacy policy live at a real, working URL
6. Ads declaration answered honestly
7. Pricing and country availability set deliberately, not left at default without thinking about it
8. Closed testing track configured and 12+ real testers ready to go