Neither Apple nor Google publishes its ranking algorithm. But both say enough, and enough is visible from the outside, to know which factors matter. Apple puts it in one line: search results are based on text relevance and user behavior. Here’s what that means in practice.
Two kinds of ranking factors
- Relevance: does your app match the search? Decided mostly by your metadata.
- Performance: do people who see your app download it, like it and keep using it? Decided by user behavior.
You need relevance to be considered at all, and performance to rank above the other relevant apps.
App Store ranking factors
Metadata (relevance)
| Field | Limit | Indexed for search |
|---|---|---|
| App name | 30 characters | Yes — strongest |
| Subtitle | 30 characters | Yes |
| Keyword field | 100 characters | Yes (hidden) |
| In-app purchase names | 30 characters each | Yes |
| Developer name | — | Yes |
| Description | 4,000 characters | No |
| Promotional text | 170 characters | No |
Words count once across name, subtitle and keyword field, and Apple combines them into phrases. Check yours with the free ASO keyword tool. More in App Store keywords.
User behavior (performance)
- Downloads and download velocity, especially for the keyword in question.
- Conversion rate from search result to install — your icon, first screenshots and rating sell or don’t. See App Store conversion rate.
- Ratings and reviews — average and number, especially recent ones.
- Engagement and retention — apps that get deleted quickly are widely believed to lose ground.
Google Play ranking factors
Metadata
Google Play has no keyword field. It reads the title (30), short description (80) and full description (4,000). The description counts, so use your main keywords naturally a few times — but Google’s policy forbids keyword stuffing. Check density and policy issues with the Google Play ASO tool.
Performance and quality
- Installs, conversion rate and retention, as on iOS.
- Ratings and reviews.
- Technical quality. Google publishes thresholds: keep the user-perceived crash rate under 1.09% and the ANR rate under 0.47% overall (8% per phone model). Above them, Play may reduce your app’s visibility and show a warning on the listing.
More in our Google Play ASO guide.
What you can control
| Factor | What to do |
|---|---|
| Keyword relevance | Main keyword in the name; different words in subtitle and keyword field |
| Conversion | Strong first three screenshots, clear icon, test with product page optimization |
| Ratings | Ask with the in-app review prompt at a good moment; reply to low ratings |
| Retention | Better onboarding; fix what reviews complain about |
| Quality | Watch crash rate and roll out gradually with phased release |
| Freshness | Regular updates with real release notes |
Myths
- “Repeating a keyword helps.” Not on iOS — each word counts once. On Google Play it can get your listing rejected.
- “The description matters on iOS.” Not for search; it matters for conversion.
- “Ratings only matter for conversion.” They also feed into ranking, so a run of one-star reviews after a bad update hurts twice.
Ratings are the factor teams neglect
Metadata is a one-off task; ratings are daily work. A broken update can drop your rating in two days — and with it, your conversion and ranking. allstarsbot sends every new App Store and Google Play review to Slack or Microsoft Teams, so you see problems the day they start and can reply while it still changes the rating. More in App Store ranking.



