Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Checklists

App Store Listing Checklist

A checklist for an App Store or Google Play listing: title and keywords, screenshots and preview video, privacy details, ratings prompts and attribution links.
Checklistbeginner6 min readUpdated

When to run this checklist

Run it before a listing is submitted for the first time and before every update that touches the listing itself: text, screenshots, preview video, icon, pricing or the privacy declarations. Many teams treat the listing as part of the app release and let it ride along with a build, which is exactly how an outdated screenshot or a feature claim that was cut from the release reaches the store. If the build changes what the app does, the listing needs this pass even when nobody meant to change it.

The person who owns the listing runs the list, usually a growth or product marketer, with the developer who submits the build on hand for the specification and privacy items. Run it for each store separately. The App Store and Google Play differ in fields, specifications and review rules, and a listing that passes in one can be rejected or truncated in the other.

Before you start

  • The release notes or ticket, so the listing can be checked against what the app actually does now.
  • The keyword research for each priority market, with the terms the listing is meant to rank for.
  • Both store consoles open, with the current live listing visible for comparison.
  • The final screenshots and preview video, exported for every device size the stores ask for.
  • The privacy inventory: what data the app and its software development kits collect, and why.
  • The current conversion baseline from each console, noted before anything changes.

The checklist

The groups follow the listing from top to bottom, then add the work that happens after release. Text and visuals decide whether the listing is found and chosen; compliance decides whether it is published at all; ratings, links and the after-release group decide whether anyone can tell what the change did. Being found in store search and chosen on the listing are the two outcomes ASO sets out to improve.

0/14

Text

Visuals

Compliance

After release

Where each check is explained

The widget keeps each line short enough to tick; the reasoning sits in the guides. Each check links to the page that explains it.

CheckExplained in
Title and subtitle built around searchesApp store optimisation
Keyword field without repeated title wordsApp store optimisation
Description leads with the main benefitApp store optimisation
Opening screenshots show the main benefitApp store optimisation
Screenshots and preview video meet specificationsApp store optimisation
Screenshots and text localised per marketTranslation and transcreation
Listing checked against review guidelinesApp store optimisation
Privacy and data safety details accuratePrivacy, consent and measurement
Claims and prices match the appApprovals and compliance reviews
Ratings prompted after a moment of successPush notifications and in-app messaging
Replies to recent reviewsService recovery and complaints
Campaign links attributableApp attribution: MMPs and SKAdNetwork
Change recorded and conversion comparedApp store optimisation
Store experiments for larger changesA/B testing guide

The two ratings lines are set up as a standing routine, with the prompt moment, triage, reply owners and the reset decision, in the tutorial on app rating prompts and review replies.

If an item fails

Compliance failures stop the submission. A listing that misdescribes the app's data collection, promises a feature the build does not have or shows a price that differs from the in-app price is a rejection risk at best and a consumer protection problem at worst. Fix the declaration or the claim, and if the answer depends on what a software development kit collects, get it from the developer rather than guessing. The store review guidelines in the sources are the reference for what each store will accept.

Text and visual failures can usually be fixed in an hour, so fix them rather than ship around them. The one exception is localisation: if a priority market's screenshots are not ready, it is better to ship the update with the previous localised set for that market and a note in the ticket than to show an untranslated set, because an English screenshot in a local-language listing reads as an app that does not serve the market.

Ratings, links and after-release items rarely block a submission, but they decide whether the update can be judged. Ship with a note if the attribution links are not ready, and do not start paid install campaigns against the listing until they are; the app install campaigns guide explains why CPI only means something once installs are attributed. If the listing change is large enough that you want to know whether it worked, run it as a store listing experiment rather than a straight swap, because a before-and-after reading of store CVR mixes the change with seasonality and whatever campaigns were running.

Illustrative example — not a real result

A beekeeping log app's spring update

A small team behind a beekeeping log app plans a spring update with a new hive-inspection feature. The product marketer runs the checklist on the Google Play listing and finds three problems. The second screenshot still shows a sync feature the team removed last year. The data safety form says the app collects no location data, but the new feature tags inspections with the apiary's position. And the description's opening line talks about the company, not the benefit. The team replaces the screenshot, updates the data safety form with the developer, and rewrites the first line around keeping inspection records in the field. They note that the listing converted around 28% of store visitors in the month before, and set a reminder to compare the month after. Because they want to know whether the inspection feature should lead the screenshots, they run that question as a store listing experiment instead of guessing.

Common mistakes

  • Letting the listing ride along with a build. The release changes the app and nobody re-reads the listing, so the screenshots and description describe the previous version.
  • Copying one listing into both stores. Fields, specifications and review rules differ, and text written for one store is truncated or rejected in the other.
  • Translating keywords instead of researching them. The direct translation of a search term is often not what people in that market type.
  • Guessing the privacy answers. The marketing team fills in the data safety form from memory, and a software development kit collects something nobody listed.
  • Asking for a rating on first open. The prompt arrives before the user has had any experience worth rating, and the store's limited prompts are spent on indifference.
  • Changing everything at once. Title, screenshots and icon change in the same update, store conversion moves, and nobody can say which change did it.

The checklists library holds the rest of the pre-flight lists, including the ones for launching paid campaigns against a listing once it is live.

Terms used on this page

Where this page is used

Also related

Sources

  1. App Store — Apple Developer
  2. App Store Review Guidelines — Apple Developer
  3. Google Play Console Help — Google

Related