Why App Store Ratings and Reviews Matter More for ASO
By Anil Ozdemir, who heads the ASO team at Redbox Mobile. Ratings and reviews now do more than reassure hesitant visitors. They appear where discovery happens, feed store ranking signals, and give teams a direct window into what users value or dislike. As keyword tweaks have become less reliable and privacy changes have reduced post-install visibility, a deliberate ratings and reviews programme has become a core part of app store optimisation.
Where ratings and reviews show up
Rating score and rating count show up in search results and on the product page, so they shape the first impression before a visitor even opens the listing. Both major stores also take those signals into account when deciding how visible an app is. Reviews work differently: they sit further down the product page, but the words people use can matter for search. Google Play indexes review text, meaning phrases in reviews can influence which keywords an app ranks for. Tracking recurring keyword combinations and long-tail wording in reviews can therefore surface language worth testing elsewhere in the listing.
Each store also groups reviews so visitors can filter them. The App Store offers most helpful, most favourable, most critical and most recent. Google Play offers all, critical and positive, and both stores let people sort by most relevant or most recent.
A useful way to think about the funnel is:
- Search results: icon, name, score and count drive the click to the product page.
- Product page: screenshots, description and the first reviews drive the install decision.
- After install: reviews become feedback about bugs, onboarding, pricing friction and features people enjoy.
The default reviews carry extra weight
Visitors who scroll to the reviews section usually meet the most useful reviews on iOS and the most relevant reviews on Google Play first. Those entries set the tone before someone reads the full set, so they deserve priority when you reply and when you encourage helpful signals.
On Google Play, tapping yes under a review marks it as relevant; the reviews with the highest yes totals rise to the top by default. On the App Store, press and hold a review for about a second and choose the helpful option. The practical takeaway is to monitor the default view as a new visitor would see it, respond to the reviews shown there, and treat a drop in helpful or relevant marks as a visibility problem, not just a vanity metric.
Why their influence has grown
Three developments have raised the stakes for ratings and reviews. The first is diminishing returns from metadata work: compared with several years ago, adjusting keywords moves visibility and conversion far less, while the score and review signals appear to matter more. The second is measurement. When Apple introduced its iOS 14 privacy changes in 2021, including SKAdNetwork, post-install tracking became considerably harder, and written feedback turned into one of the more dependable ways to learn how people actually experience an app. The third is a ranking threshold on Google Play: as of February 2023, an app whose average rating score is 3.0 is not eligible for the top charts, which cuts it off from a meaningful share of browse-driven discovery through the Apps and Games tabs and category charts. For an app already earning strong chart positions, that exposure is worth protecting; for a weaker one, the score becomes a gate to clear before other optimisation work can pay off.
Asking for ratings without wasting the prompt
Few installers ever leave a review, and people with a bad experience are more likely to do so than satisfied users. A prompt strategy should therefore be selective, timely and routed by sentiment.
For iOS, Apple permits an in-app prompt only three times in a 365-day period. A preliminary question can divert unhappy users to private feedback instead of a public review, so you still learn about performance problems without publishing every complaint. For Android, the Google Play in-app review flow lets people rate without leaving the app, linking directly to the listing, and Google enforces a time-bound quota on how often the dialog can appear.
Timing checklist:
- Give users enough time to experience the app before asking.
- Ask after a likely positive moment: payment method added, content favourited or starred, subscription, purchase or deposit, level passed, game or bet won, or an achievement reached.
- Avoid asking immediately after a failure, crash or paywall rejection.
- Review the default most useful and most relevant entries weekly, and reply to the ones shaping first impressions.
Google Play can recalculate the star distribution
Google Play does not always display a simple lifetime average. It recalculates the star distribution from current quality, leaning on recent reviews, and can move ratings between star buckets when it does so. One observed pattern involved a sports betting app whose average stayed below 2.5 for months and then jumped above 4.5 in a single day as negative ratings were redistributed into positive ones.
That behaviour has a rationale: long-lived apps change through new features, bug fixes and experience improvements, so a single new low rating should not necessarily overwhelm a large base of older positive ratings. For reporting, treat a sudden distribution shift as a recalculation event first, and check recent review sentiment before concluding that users suddenly changed their minds.
Main takeaways
Treat ratings and reviews as a growth system, not a support inbox. Protect the score because it affects search visibility, top-chart eligibility on Google Play (where a 3.0 average keeps an app out of the charts) and the click from results to product page. Manage the default reviews because they form the first impression. Use prompts sparingly, after positive events, and route unhappy users to private feedback. Finally, read reviews as product research: with post-install tracking harder than before, they often reveal complaints and delights that analytics no longer show clearly.
What a prompt did for one iOS app
One iOS sports app in the UK added the ratings and reviews prompt around November. Over the following six months, the number of ratings gained per star rose steadily rather than spiking once and fading. The pattern is a useful benchmark: a well-timed prompt can lift rating volume over time, not just in the week it ships.
Frequently asked questions
What is the difference between a rating score and a review?
Ratings are visible earlier, in search results, and both stores factor score and count into visibility. Reviews appear after a visitor reaches the product page and scrolls down, so they mainly shape the decision once someone is already considering your app.
How do I mark a review as useful or relevant?
On iOS, press and hold a review for about a second, then choose the helpful option. On Google Play, tap the yes button under a review to mark it relevant. Reviews collecting the most of those signals tend to surface first by default.
When should an app ask for a rating?
Wait until people have had time to use the app and have just completed a likely positive action, such as adding a payment method, favouriting content, subscribing or purchasing, passing a level, winning, or reaching an achievement.
How often can I prompt users for a review?
Apple limits the in-app prompt to three times in a 365-day period, so use it sparingly. Google Play applies its own time-bound quota to the review dialog, so design the trigger to respect that limit and avoid repeated interruptions.
Why can a Google Play rating distribution change suddenly?
Google Play calculates the displayed distribution from current quality rather than a simple lifetime average, giving more weight to recent reviews. That means a sudden change in the star distribution can reflect recalculation, not necessarily a wave of new ratings on that day.