App store ranking works in two steps: keywords and metadata decide whether your app is indexed for a search, then product signals decide its position. Fix them in that order. First keyword placement and exact matches, then download velocity, then ratings and conversion rate, then reliability, market pressure and browse influence. Product quality breaks ties between apps targeting the same keywords.
Key takeaways
- Check indexation before anything else: an app not indexed for a keyword cannot rank for it.
- Keywords and metadata get you into the race. Downloads, ratings, stability and engagement decide the order.
- The playbook's top five to fix once metadata is done: download velocity, technical health, ratings, engagement, and one platform-unique factor.
- Benchmarks I use: 4.8+ stars for a top-three keyword rank, 4.9 for #1, and 100+ new ratings a week.
- Don't rewrite metadata to fix a rank that product quality is holding down.
How does app store search ranking work?
Store search narrows in two steps. I call this the Index-Then-Rank Search Model: keywords index apps into a database for each term, then the ranking algorithm orders the indexed apps for each query.
Indexation means the store recognizes your app as a match for a keyword. So the first check for any target term is simple:
- Search the keyword in the store and check your app appears.
- If it is absent, add the keyword to your metadata before chasing rank.
- Then work the ranking factors for that query.
- Track your position among the results over time.
Teams regularly treat a missing app as a ranking problem when it was never indexed. That wastes weeks.
Which ranking factors should you fix first?
Fix keyword placement first, then downloads, then ratings and conversion, then the rest. I call this the Ranking Factor Priority Ladder. It orders ten factor groups from first to last to work on:
| Priority | Factor group | What it covers |
|---|---|---|
| Highest | Keyword | Occurrences, exact matches |
| Highest | Metadata | Where keywords appear and in which field |
| High | Downloads | Download velocity and count |
| High | Algorithm updates | Temporary or permanent shifts |
| Middle | Ratings | Average, velocity, count |
| Middle | Conversion rate | Overall and per keyword |
| Lower | Reliability | Android vitals, retention, uninstall rate |
| Lower | Market factors | External and internal pressure |
| Lowest | Browse influence | Editors' choice, Similar Apps, categories |
| Lowest | Others | Release boost, search ads, backlinks |
Download velocity is how fast an app gains installs over a short period; stores treat a rise as a ranking signal. Conversion rate (CVR) is the share of people who saw your app and installed it, overall and for each keyword.
The Appkitekt playbook gives a parallel list for the work after metadata is right, the top five factors to fix first:
- Download velocity.
- Technical health.
- Ratings.
- Engagement.
- A platform-unique factor: on iOS, whether your screenshots, description and the app itself match the keyword's search intent; on Google Play, backlinks from high-quality sites to your listing.
Why does an app with the same keywords outrank yours?
Because product signals decide the order among apps targeting the same keywords. I call this Product Signals Behind Rankings, and it has four causes:
- Ratings. I aim for 4.8+ stars for a top-three keyword rank and 4.9 for #1, with 100+ new ratings every week. The playbook's floor is 4.5 stars on Android and 4.8 on iOS.
- Stability. Keep crashes near 0%, avoid spikes, and cut freezes and app size. Android vitals, Google Play's quality measures such as crash and freeze rates, can reduce visibility when they are poor.
- Tech. On iOS, building an Apple Watch app and supporting the latest watchOS are part of the picture.
- Engagement. Lower uninstalls, grow session count and length, and extend 30-day use.
On ratings, ask at the right moment and through the right door: Apple's native rating prompt and Google's In-App Review API, triggered after a popular, successful in-app moment. Never put a "Do you enjoy the app?" question in front of the native prompt to filter out unhappy users. More in how to get more app ratings.
How much weight does each listing element carry?
At Appkitekt we weight App Store listing elements in four groups: visuals first, then text, then reliability, then extra display spots. I call this App Store Element Weights. It is how we work, not a published Apple formula.
- Order work by group: visuals (four stars), text (three), reliability (two), extra display (one).
- In visuals, start with the icon (45% of the group), then screenshots (35%), videos (15%) and product page artwork (5%).
- In text, start with the title (45%) and subtitle (25%); the long description comes last (5%).
- Treat ratings and reviews (75% of reliability) as listing work, not just a support queue.
- In extra display, pursue featuring (50%) before Apple Search Ads (30%).
The weighting explains why polishing the long description before the icon, or chasing featuring before the visuals work, are such common misallocations. On iOS the long description is not even indexed for store search. For where keywords sit in the text you do control, see the iOS keyword field rules.
Signs you are fixing the wrong factor
- Backlinks are discussed before exact-match keywords are in place.
- Rank drops are blamed on metadata during a store algorithm update.
- Retention and stability scores are ignored as ranking inputs.
- You share keywords with a rival and still rank lower.
- Crash spikes show up just before rank drops.
- Only a few new ratings arrive each week.
- Ratings are treated as a support issue, not ASO.
- Rank work starts before anyone checks indexation.
Does adding a keyword guarantee a ranking?
No. Adding a keyword gets you indexed; ranking for it depends on the factors above. Keyword optimization finds the best keywords your app can rank for under its current health and marketing conditions. If the barriers are product signals, improve those rather than rewriting metadata again.
Choosing the right terms is its own discipline; see the five tests for choosing ASO keywords.
Frequently asked questions
What are the most important App Store ranking factors?
Keywords and metadata come first, because they decide whether your app is indexed for a search at all. After that, product signals decide the order: download velocity, technical health such as crash rates, ratings, and engagement like retention and uninstalls. Each store also has a unique factor: on Google Play, backlinks to the listing; on iOS, how well your screenshots and description match the search intent.
Why does a competitor with the same keywords rank higher?
Because keywords only get both apps into the race. The order among apps targeting the same keywords comes from product signals: ratings average, count and weekly growth, crash rate and app size, and engagement such as uninstalls, sessions and 30-day use. Rewriting metadata will not fix a gap that product quality is holding down.
What rating do I need to rank in the top three?
On the benchmarks I use, 4.8 stars or more supports a top-three keyword rank and 4.9 supports first place, with 100 or more new ratings a week. Ask for ratings with Apple's and Google's native in-app prompts at a success moment, never behind a filter that asks users first whether they like the app.
Should I change metadata after a ranking drop?
Not straight away. If the drop came with a store algorithm update, the cause may be temporary or permanent, and changing metadata adds a new variable that hides the real one. Check indexation first, then look at download velocity, ratings and stability. Rewrite keywords only once the evidence points to them.
If you want your ranking factors checked in this order on your own app, that is the starting point of our ASO strategy service.
About the author
Binh Dang founded Appkitekt after leading ASO at Flo, Kovalee and Jellyfish, where he was Senior Director of ASO, and starting out as an ASO consultant at Phiture. He wrote The ASO Black Book.
See how Appkitekt runs ASO