Google Play Store Listing Requirements Before You Publish

Quick answer: Before you publish on Google Play, your store listing needs an app name, a short and full description, a 512 × 512 icon, a 1024 × 500 feature graphic, at least 2 screenshots, a category and a contact email. In App content you must add a privacy policy, ads declaration, content rating, target audience and Data safety form, and new personal accounts must finish a closed test first.

How to write and design each of these is covered in the Google Play store listing guide. Screenshot rules in detail, including the recommendation thresholds, are in Google Play screenshot requirements.

The App content page in Play Console holds the declarations Google reviews alongside your listing. Most apply to every app.

Privacy policy

Google requires a privacy policy even if your app doesn't access personal data. Its User Data policy asks for a link in the designated Play Console field and a link or text inside the app. The policy must sit on an active, publicly accessible, non-geofenced URL (no PDFs) and be clearly labeled as a privacy policy.

Data safety

All developers with an app published on Google Play must complete the Data safety form, including apps that collect no user data; apps that are active only on internal testing tracks are exempt. Google states that a privacy policy is required to complete it. Remember to include data collected by third-party SDKs. App privacy labels and Data safety covers common mistakes.

Content rating

Complete the rating questionnaire for your app. Google warns that apps without a rating appear as "Unrated" and may be removed. The questions are about content such as violence, user interaction and purchases, so answer for what the app actually contains. See age ratings explained for how ratings compare across stores.

Target audience and content

Declare the age groups your app targets. If children are among them, Google's Families policy requirements apply, which affect ads, data collection and content.

Sign-in details and ads

If any part of your app is behind a login or other authentication, give reviewers working credentials and instructions; Google currently allows up to five sets. For ads, declare honestly whether your app shows any, including through SDKs. Google says misrepresenting ads can lead to suspension.

Completing every field isn't enough; the content has to meet Google's Metadata policy. The key points:

• No misleading, improperly formatted, non-descriptive, irrelevant, excessive or inappropriate metadata, which covers the description, developer name, title, icon, screenshots and promotional images.
• No text or images in the title, icon or developer name that indicate store performance or ranking ("#1", "App of the year"), price or promotions ("10% off"), or Google Play programs ("Editor's choice").
• No emojis or special characters in the title, icon or developer name.
• No unattributed or anonymous user testimonials in the description.
• Screenshots and videos should reflect your app's actual experience.

Google's preview asset guidance goes further for graphics: it asks you to avoid ranking claims, testimonials, awards and calls to action in screenshots and the feature graphic. These are the most common things to fix when you adapt an App Store design for Play.

Your listing can be complete and still not go live if the account side isn't ready:

1. Developer account and declarations. When you create an app, you acknowledge the Developer Program Policies and US export laws and accept the Play App Signing Terms of Service.
2. Closed testing for new personal accounts. Google currently requires personal developer accounts created after November 13, 2023 to run a closed test with at least 12 testers who have been opted in continuously for at least 14 days before production access. The closed testing guide explains how to plan for it.
3. An app bundle on a release track. Google Play requires new apps to be published as Android App Bundles.

1. App name, short description and full description complete in your default language.
2. Icon, feature graphic and at least 2 phone screenshots uploaded, ideally 4 or more at 1,080 px or higher.
3. Tablet screenshots added if your app supports large screens.
4. Category, tags and contact email set.
5. Privacy policy live at a public URL and linked inside the app.
6. Ads, content rating, target audience and Data safety completed in App content.
7. Sign-in details added if any content requires a login, and tested.
8. Closed test completed if you have a new personal account.
9. App bundle uploaded to a release, then sent for review.

For the full release flow, from creating the app to pressing publish, see how to publish an app on Google Play.