Google Play listing checklist before publishing

Review the listing copy and graphics

Check the title, short and full descriptions, icon, phone and tablet screenshots, and feature graphic. Verify that every asset matches the app and follows current format and content rules.

Complete content and audience declarations

Check the content rating questionnaire and target-audience settings. Keep answers aligned with the actual audience and features rather than copying a previous release without review.

Verify data safety and privacy links

Compare the Data safety form with the app’s current SDKs and data handling. Confirm privacy-policy links work and explain the practices represented in the Play Console declarations.

Use the pre-launch report

Review device test results and address crashes, layout problems, or compatibility issues that affect the release. Retest after fixes and keep the supported-device expectations clear.

Preview and stage the release

Check the listing on relevant devices and locales, then follow the current track and rollout process in Play Console. Keep a release note and a response plan for issues after launch.

Check declarations against the release build

Review Data safety, target audience, content rating, permissions, and privacy links against the exact release candidate and its SDK behavior. A declaration copied from an older version can become inaccurate after a dependency or feature change.

Keep a record of who verified each Play Console form and when. If the binary changes after review, revisit any declaration that depends on app behavior.

Preview the public-facing listing

Check the listing on a phone and tablet where possible, and inspect localized storefronts rather than only the default language. Confirm that the feature graphic, screenshots, and short description appear in the expected order.

After publishing, verify the live store page and report any asset-processing or device-eligibility issue before expanding a staged rollout.

Check release and listing status together

Review warnings, policy declarations, asset processing, and rollout status in Play Console before announcing the release. A production build can be available while a listing locale or graphic still needs attention.

Make sure the store description and screenshots refer to features available in the released track. If staged rollout or country availability is limited, avoid copy that implies universal access.

Prepare a rollback and correction path

Know who can halt a staged rollout, replace a listing asset, or respond to a policy notice. Keep the previous approved creative available so a campaign image can be removed quickly if its offer expires or a claim changes.

Record the release and listing update dates separately. This helps the team distinguish app behavior changes from store-page changes when reviewing early feedback.

Review every declaration against app behavior

SDK updates, advertising changes, account features, or new permissions can affect content-rating and data-safety answers. Recheck those forms for the current release rather than assuming a previous declaration still applies.

Make sure the privacy policy is reachable and describes the product’s actual practices. Resolve discrepancies before submitting instead of treating console declarations as a separate paperwork step.

Confirm device and country availability

Check the supported device catalog and country rollout alongside the listing copy. Do not advertise a feature or offer in a market where the app or the relevant functionality is unavailable.

After publishing, verify that the listing is visible from the intended test account and storefront before sharing the public link.