Rating Count Thresholds That Unlock Higher App Store Visibility
Most app teams treat ratings as a vanity metric — something to glance at before a pitch deck. That's a mistake. App ratings and reviews don't just reflect quality; they function as a ranking signal. Both Apple and Google use rating count (not just average score) to determine how broadly to surface your app in search results, category charts, and editorial surfaces. Hit the right thresholds at the right time, and visibility compounds. Stay below them, and you're fighting the algorithm with one hand tied behind your back.
This post breaks down what those thresholds approximately look like by category, how the two stores treat rating count differently, and a concrete playbook for getting there faster.
Why Rating Count Is a Separate Signal from Rating Score
It's tempting to conflate the two. Don't.
A 4.9-star average with 12 reviews tells the algorithm almost nothing. A 4.2-star average with 1,400 reviews tells it a lot: real users installed your app, used it enough to form an opinion, and cared enough to leave one. That behavioral signal carries weight.
Apple's App Store uses rating count as a confidence interval. The higher the count, the more weight the average carries in ranking calculations. Below a certain threshold per category, Apple's algorithm treats your rating as statistically insignificant — and it surfaces apps with more social proof instead. Apple also resets ratings on major version updates by default (unless you specifically opt out in App Store Connect), which means teams that aren't actively collecting ratings can fall off the confidence curve after a big release.
Google Play takes a slightly different approach. Its algorithm weights recency heavily — ratings from the past 30–90 days carry more signal than older ones. This means a high all-time count doesn't protect you if your recent collection rate drops. Google also surfaces "Editor's Choice" and featured placement based partly on sustained rating velocity, not just total count.
The practical takeaway: you need both a healthy total count and an ongoing collection rate. One without the other leaves you exposed.
Visibility Thresholds by Category (Approximate)
These ranges are based on observable patterns in store rankings and what we've seen in our engagements across multiple app categories. They are not officially published by Apple or Google — neither store releases its algorithm weighting publicly. Treat these as directional benchmarks, not hard rules.
| Category | Tier 1 Threshold (basic visibility) | Tier 2 Threshold (broader surfacing) | Tier 3 Threshold (competitive positioning) |
|---|---|---|---|
| Health & Fitness | ~50 ratings | ~250 ratings | ~1,000+ ratings |
| Productivity | ~75 ratings | ~300 ratings | ~1,500+ ratings |
| Food & Drink | ~100 ratings | ~400 ratings | ~2,000+ ratings |
| Finance | ~150 ratings | ~500 ratings | ~2,500+ ratings |
| Games (Casual) | ~200 ratings | ~1,000 ratings | ~10,000+ ratings |
| Business / B2B | ~30 ratings | ~150 ratings | ~500+ ratings |
| Navigation / Travel | ~100 ratings | ~500 ratings | ~2,500+ ratings |
| Medical | ~25 ratings | ~100 ratings | ~300+ ratings |
A few observations worth flagging:
- B2B and Medical categories have lower thresholds. The install bases are smaller by nature, and the competition for ratings is lighter. Getting to 150 ratings in a B2B app puts you in stronger relative position than 150 ratings in Casual Games, where top apps have millions.
- Games are in a different universe. If you're building a casual game and you're not thinking about rating count in the tens of thousands for top-chart positioning, recalibrate your expectations.
- Finance apps face higher scrutiny. Users are cautious, which makes collection harder. But the floor for meaningful algorithmic trust in Finance is also higher than most other categories.
How Apple and Google Differ in What They Reward
Understanding the mechanics matters because your collection strategy should be calibrated per store.
Apple App Store:
- Ratings are shown as a cumulative all-time average (unless reset at version update)
- Apple limits how frequently you can prompt users natively via
SKStoreReviewRequest— approximately three times per 365-day period per device - Apps with fewer than a category-specific threshold of ratings may be suppressed from "You Might Also Like" and related placement surfaces
- Apple Search Ads Quality Score is influenced (indirectly) by conversion rate, which is partially driven by social proof including rating display
Google Play:
- Rating recency matters significantly — Google weights the trailing 30/60/90-day window
- There is no system-level cap on in-app review prompts via the In-App Review API, but Google's documentation strongly discourages prompting in ways that interrupt user flows
- Google Play's "Install Rate" metric (how often a store listing converts a viewer to an install) factors ratings prominently — low rating count suppresses conversion, which feeds back into ranking
The net effect: Apple rewards accumulation and stability; Google rewards velocity and recency. Your collection playbook needs to account for both.
The Collection Playbook
Getting more ratings isn't about begging users. It's about timing the ask correctly. Here's what works in practice:
1. Prompt after a win, not after a task. The worst time to ask for a rating is mid-flow ("Please rate us!" immediately after a form submission). The best time is after the user has experienced a clear success moment — a completed workout, a delivered order, a streak milestone, a successful booking. In our engagements, this timing shift alone meaningfully improves prompt acceptance rates.
2. Use the native prompt — don't build a custom gate.
Both Apple and Google's guidelines prohibit asking users to rate you only if they're happy (i.e., routing happy users to the store and unhappy users to a feedback form). This used to be common practice. It's now a policy violation on both platforms and grounds for removal. Use SKStoreReviewRequest on iOS and the In-App Review API on Android and show it to all eligible users.
3. Segment by engagement depth before prompting. Don't prompt after the first session. Trigger the prompt logic only after a user has completed N sessions, or hit a specific engagement threshold. For most apps, that's somewhere between 3–7 sessions or a meaningful in-app action. Users who've invested time are more likely to rate positively and more likely to respond at all.
4. Respond to reviews — both positive and negative. Responding to reviews signals active maintenance to both the algorithm and prospective users. On Google Play, response rate and response recency are observable; on the App Store, responses appear publicly. A replied-to negative review converts skeptical browsers better than a wall of silent five-stars.
5. Re-engage lapsed users around version updates (carefully). A major version update is an opportunity to re-prompt users who haven't rated yet, especially if the update addresses known pain points. Time the prompt for after they've experienced the improvement, not at first launch of the new version.
What a Stalled Rating Count Actually Costs You
If you're sitting at 40 ratings six months after launch, here's what's likely happening underneath the surface:
- Search suppression. Your app is appearing lower in keyword searches than its metadata would otherwise warrant, because rating count is part of the confidence signal the algorithm uses to rank results.
- Lower browse conversion. Users browsing category charts see your 40-rating count next to a competitor's 800-rating count. The conversion gap is real and compounds.
- Weaker Apple Search Ads efficiency. Your CPT (cost per tap) and TTR (tap-through rate) on Apple Search Ads are being partially suppressed by lower store listing conversion — which lower rating count contributes to.
- Ineligibility for editorial features. Apple's Editorial team and Google's featuring algorithms both look at rating health. Sub-threshold apps are passed over.
This is why we treat rating count as an ASO infrastructure problem, not a PR problem. It connects directly to deep linking and traffic routing strategies — because how you route users post-install affects when and whether they reach the win-moments where prompt timing works.
Rating Count and App Store Conversion Rate Optimization
Rating count is one of the highest-leverage conversion levers in your store listing. Conversion rate optimization (CRO) for app store listings covers screenshots, preview videos, description copy, and icon — but rating count is often the fastest variable to move and one of the most impactful.
A listing with a strong visual asset set but 15 ratings will frequently underperform a listing with average visuals and 400 ratings, simply because social proof overrides aesthetic judgment for most users scanning category results.
If you're running A/B tests on your store listing (via App Store Product Page Optimization on iOS or Google Play Store Listing Experiments on Android), don't overlook that your test results are confounded if your rating count is too low to generate statistical confidence in conversion data. The two systems are entangled.
Need a structured ASO strategy that covers rating collection, metadata, and conversion optimization together? Our mobile app marketing team handles the full stack — from prompt timing to store listing testing to paid UA.
FAQ
Does rating count affect Apple Search Ads performance?
Indirectly, yes. Apple Search Ads Quality Score isn't publicly defined, but store listing conversion rate feeds into ad efficiency. Rating count influences conversion rate, which means low rating counts can raise your effective cost per install even on paid campaigns.
If I reset ratings on a major version update, do I lose all progress?
On iOS, you choose whether to reset ratings when submitting a new version in App Store Connect. If you opt out of resetting, your cumulative count carries forward. The decision depends on whether your existing rating distribution helps or hurts you — if you've addressed major complaints in the new version, carrying forward a poor average may be worse than starting fresh.
How many ratings do I need before ASO keyword ranking starts working properly?
There's no exact published number, but in our engagements we typically see keyword ranking starting to respond more predictably once an app crosses approximately 50–100 ratings in less competitive categories, and 200–500 in more competitive ones. Below those ranges, metadata quality has to work harder to compensate.
Can I ask my existing users to rate the app via email or push notification?
Yes — sending a notification or email that directs users to leave a review is permitted by both Apple and Google. What's not permitted is filtering based on expected sentiment (i.e., only asking happy users). The prompt must be open to all users.
Does Google Play's recency weighting mean my old ratings hurt me?
Not exactly — older ratings don't negatively weight your score, but they also contribute less to current ranking signals than recent ones. If your app had an active rating period two years ago but hasn't collected many ratings recently, your effective "algorithmic rating signal" is weaker than your all-time count suggests.
How do rating count thresholds interact with category charts?
Category chart positioning on both stores is driven by a combination of install velocity, engagement signals, and rating health. Rating count doesn't directly determine chart position, but it influences the conversion rate of your listing, which affects install velocity — which does directly affect chart position. It's circular, which is why momentum matters.
If your app's rating count is stalling visibility and you want a concrete plan to fix it — collection strategy, prompt timing, store listing CRO, and paid UA working together — talk to our mobile app marketing team or book a 30-minute call with Marco directly. We work with apps that are post-launch and ready to grow, not just apps that are pre-launch and hoping.
