App Store Optimization basics: the fields and policies that actually move installs
Name, subtitle, screenshots and store listing rules - what Apple's and Google's own documentation says drives discovery and conversion, and what gets apps suspended.
App Store Optimization (ASO) is the search-and-conversion work for your app's store listing: being found for the right searches, and turning the listing view into an install. The stores document the fields and rules precisely; most ASO advice is decoration on top of a short list of things that actually move results.
This guide follows Apple's product page documentation and Google Play's store listing guidance, checked on 19 November 2026.
The fields that carry the weight
On the App Store, Apple's documentation states that an app name can be up to 30 characters, and a subtitle up to 30 characters appears below the name throughout the store. Both are indexed for search and both are visible everywhere your app appears - they are the most valuable text you own. Google Play's store listing works the same way in spirit, and Play's policy has teeth: repetitive or irrelevant keyword usage in your app name, short description or full description can create an unpleasant user experience and result in app suspension. Keyword stuffing is not a gray tactic on Play; it is a policy violation.
Screenshots: your conversion surface
Apple allows up to 10 screenshots on your product page, and its guidance is to focus each subsequent screenshot on a main benefit or feature so you fully convey the app's value. Treat the first two or three as the whole game - they show in search results and most visitors scroll no further. Show the app in use, lead with the outcome the user wants, and add short captions; a gallery of unexplained UI is the most common wasted asset on the store. Apple's App Review Guidelines separately require that screenshots show the app in use, not merely title art, a login page or a splash screen.
The levers beyond the basics
- Product page optimization (App Store). Apple's documentation describes testing alternate versions of your product page elements to learn what converts better - run these before spending on ads, since ad traffic multiplies whatever conversion rate you already have.
- Custom product pages (App Store). Apple supports creating custom product pages, letting paid campaigns land on a page tuned to the audience you targeted.
- Store listing experiments (Play). Play provides listing experiments through Play Console; your listing is shared across tracks including testing tracks, so plan experiments with that in mind.
- Ratings and reviews. They feed both ranking and conversion; ask at moments of demonstrated value, and answer negative reviews visibly.
What to do in week one
Write the name and subtitle for the search terms your users actually type (check how they describe the problem, not your internal vocabulary), build the first three screenshots around the single strongest use case, complete every store field (categories, descriptions, support URL), and set a baseline: impressions, conversion rate, keyword rankings. ASO is iterative - change one element, measure, keep what wins. If your app is still in planning, Android or iOS first covers the platform choice these listings sit on.
Sources
- Apple Developer, Creating Your Product Page: https://developer.apple.com/app-store/product-page/
- Apple App Review Guidelines (metadata and screenshots): https://developer.apple.com/app-store/review/guidelines/
- Google Play Console Help, Create and set up your app (store listing policy): https://support.google.com/googleplay/android-developer/answer/9859152
Drafted with AI assistance from these sources. Store ranking algorithms are not published in full; this guide sticks to documented fields and policies rather than ranking folklore.