ASO KPIs and ranking factors
App store ranking is driven by three groups of factors: relevance signals from indexed text (app name, subtitle, Apple's keyword field, Google Play's description), performance signals (install volume and velocity, conversion rate from product page views, retention and uninstall rate), and quality signals (average rating, rating volume, crash and ANR rate, update recency). The KPIs that measure your work are different from the factors themselves: track impressions to judge keyword reach, product page views to judge listing appeal, conversion rate to judge the creative, and install velocity to judge whether the two are compounding.
Key takeaways
- Ranking factors are what the store measures; KPIs are what you steer by — do not confuse the two.
- Impressions test metadata, conversion rate tests creative. Installs are the outcome of both and diagnose neither.
- Conversion rate is a ranking factor, not just a business metric, because the install happens inside the store.
- Retention and uninstall rate feed Google Play ranking directly; a spike of low-quality installs can hurt.
- Rating volume matters alongside rating average — a 4.8 from 40 reviews carries less weight than a 4.5 from 40,000.
The ranking factors, grouped and weighted
| Factor | Apple App Store | Google Play |
|---|---|---|
| App name / title | Highest weight | Highest weight |
| Subtitle / short description | High | High |
| Keyword field | High (100 chars, hidden) | Not applicable |
| Long description | Not indexed | Indexed — density matters |
| Install volume and velocity | High | High |
| Conversion rate | High | High |
| Retention / uninstalls | Medium | High |
| Ratings average and volume | High | High |
| Crash and ANR rate | Medium | High (Android Vitals) |
| Update recency | Medium | Medium |
| In-app purchases and events | Medium (indexed on Apple) | Low |
Neither store publishes weights, so these are practitioner estimates drawn from observed movement across listings rather than documented values. What is not in dispute is the grouping: text decides which queries you are eligible for, performance decides where you place among eligible apps, and quality acts as a multiplier or a brake on both.
The KPIs to steer by
| KPI | What it tells you | Act on it by |
|---|---|---|
| Impressions | Keyword reach — are you eligible for enough searches | Rewriting indexed metadata |
| Product page views | Whether search results tempt a tap | Improving icon and first screenshot |
| Conversion rate | Whether the listing sells | Testing screenshots, captions, video |
| Install velocity | Whether reach and conversion compound | Sustaining both, plus release cadence |
| Average rating | Quality signal and conversion multiplier | Prompt timing and review replies |
| Retention day 1 / day 7 | Whether installs were the right ones | Aligning listing promises with the product |
What does not affect ranking
- Backlinks — app stores have no equivalent of web link authority.
- Keyword stuffing in Apple's description, which is not indexed at all.
- Developer website domain authority, which is a web SEO factor and not a store one.
- Paid Apple Search Ads spend, which buys placement above organic results but does not lift organic rank directly.
- Price alone, though price affects conversion, which does feed ranking.
Worked example: diagnosing a flat month from the metrics
A news app's installs fell fifteen per cent month on month and the team's first instinct was that a ranking had been lost. The metrics said otherwise, and the diagnosis took an hour rather than a sprint because the three numbers were already being recorded separately.
Impressions were flat, which rules out a ranking or indexing problem — the app was being shown exactly as often as before. Product page views were flat too, so the search result itself was performing normally. Conversion rate had dropped, and it had dropped from a specific date. That date matched a release in which the screenshots had been updated to show a redesigned interface, tested by nobody.
The correct read is that installs are an outcome, not a diagnostic. Impressions test the metadata, product page views test the search result presentation, and conversion rate tests the page itself. A team recording only installs sees the same fifteen per cent drop and has no way to tell a ranking loss from a creative regression.
Metric habits that hide the problem
The measurement errors that make ASO look unaccountable:
- Reporting installs alone, with no upstream metrics to attribute them to.
- Comparing week to week rather than against the same period a month earlier, so weekday and seasonal effects dominate.
- Reading ranking positions without impression volume, when most tracked keywords have too little demand to matter.
- Failing to record a baseline before a change, which makes the result unattributable however good it is.
- Blending paid and organic traffic in the conversion figure, so paid campaign timing looks like an ASO result.
- Chasing average rating as a headline number while ignoring the recent-review trend, which is what actually moves it.
Frequently asked questions
What is the most important app store ranking factor?
The app name, closely followed by install velocity. The name carries the most text-relevance weight on both stores, and velocity is the strongest performance signal — but neither works without the other, since a well-named app that nobody installs does not hold its position.
Do Apple Search Ads improve organic ranking?
Not directly. Search Ads buy a placement above the organic results. The indirect effect is real though: the installs they drive count as install volume, which is a ranking factor.
Which ASO KPI should I report to leadership?
Conversion rate and organic install volume together. Conversion rate shows the listing is working, and organic installs show it is producing something the business cares about. Impressions alone are easy to move and easy to misread.
appXL Research
App Store Optimization Research Team
The appXL research team analyzes App Store and Google Play ranking data across the apps our agent manages, and publishes what it finds.