Why Did My App's Rating Count Suddenly Drop?

If your app's rating count dropped overnight, the most common causes are deliberate store mechanics, not a bug — and several aren't a real loss of ratings at all. On iOS, shipping a new version resets the summary rating to zero if someone toggled that option in App Store Connect, and the version and territory filters can make your count look far smaller than it is. On Google Play, ratings are now country- and device-specific, so where you look changes the number. And both stores routinely remove fake and policy-violating reviews, which lowers the count on purpose.

So before you panic, figure out whether the count truly fell or you're just looking at a filtered slice of it — a genuine drop from a reset or a fraud purge behaves nothing like an artifact of the view you're on. Below is every cause, sorted by how often it's the real culprit, so you can pin yours down in minutes.

This is the classic overnight-to-near-zero drop, and it's almost always an iOS release. When you submit a new version in App Store Connect, Apple gives you the option to reset the app's summary rating — the aggregate star score and the count on your product page start fresh, reflecting only ratings collected after that version goes live. The written reviews aren't deleted, but the number that headlines your listing gets zeroed out.

It's a toggle someone has to actively turn on, so if your count cratered right after a release, check who submitted the build and whether they enabled it. Teams do it on purpose sometimes: a relaunch sheds a legacy of one-star reviews from an old, broken version. But it also gets flipped by accident, or by a contractor who didn't realize what it does. There's no undo, so you rebuild from the new version forward. The upside is that a reset only makes sense when the release genuinely fixed what people were angry about, and fresh, higher ratings tend to follow a real fix.

If the public listing looks normal but the number inside App Store Connect looks tiny, you're probably reading a filtered slice. The Ratings and Reviews page filters by both version and territory. Set the version filter to your latest release and you'll see only the ratings that version has earned so far — a small fraction of your all-time total, easy to misread as a collapse. Switch it back to All for the real cumulative count.

The territory filter does the same thing geographically. App Store ratings are tallied per storefront, so a view scoped to one country shows that country's ratings alone, and the same app checked from another region's App Store shows a different number. Neither of these is a drop — it's the same data, sliced. The two stores expose these counts and filters differently, and knowing which is which saves you a false alarm; we lay out the mechanics side by side in [App Store vs Google Play review replies](/blog/app-store-vs-google-play-review-replies).

If the drop is on Google Play and it's in how the rating looks to your users rather than in a filter, this is likely why. Google announced in 2021 that Play Store ratings would become country- and device-specific: a user in Germany now sees the rating built from German users, and someone on a tablet or Wear OS watch sees ratings from that form factor, not the phone-heavy global average. The intent was relevance, but the side effect is that the single global number you used to eyeball got split into many smaller, local ones.

So the count a user sees in their market can be far lower than your worldwide total, and it moves independently by country and device. In the Play Console you can still see the aggregate and filter it by country and device type — the honest way to compare like with like. If your headline number looks like it fell, confirm you're not comparing a global figure against a country- or device-scoped one. Often nothing was lost; the rating just got sliced the way Google now slices it.

Both Apple and Google actively moderate ratings, and removal is a real, sudden way for your count to fall. Spam, incentivized review rings, bot-driven ratings, offensive content, and reviews that break the stores' guidelines all get purged — sometimes in batches, which is why the count can step down noticeably in a single day. If a competitor botted you with fake one-stars, or an old growth-hack seeded fake five-stars you've long forgotten, a cleanup sweep takes those out and your number drops.

This stings when it's your positive ratings that got culled, but it's healthy: a count built partly on fakes is a liability, not an asset. If you're trying to work out whether a chunk of your reviews were genuine in the first place, we dig into the tells in [are app store reviews fake?](/blog/are-app-store-reviews-fake). Users can also delete their own reviews anytime, which trims the count gradually rather than in a cliff — so a slow, steady decline is more likely user deletions than a moderation sweep.

One more Play wrinkle, so you don't misdiagnose it. Since Google I/O 2019, the Play rating has been recency-weighted — newer ratings count for more than old ones in the displayed average. That moves your star score, not your raw count, so if your average shifted but your total ratings held, reweighting is the explanation, not a lost rating.

That same I/O 2019 announcement carried a useful number for anyone rebuilding after a real drop: Google reported that developers who respond to reviews see an average lift of 0.7 stars. Replying doesn't restore a reset count, but it's the most reliable lever on the ratings you collect next — a calm, specific answer is quiet reassurance for the hundred people reading before they rate. We make the case in full in [does replying to app reviews raise your rating?](/blog/does-replying-to-app-reviews-raise-your-rating).

That reply names the exact version and fix, and it corrects the scariest part of the complaint, the fear of lost data, in one calm pass, in the reviewer's own language. It also fits both stores: Google Play caps developer replies at a hard 350 characters, while Apple publishes no official character limit and community testing suggests you can run to a few thousand. Write to the tighter Play limit and the reply works everywhere. Responding in the reviewer's language matters more than most teams expect; we cover the how in [reply to app reviews in any language](/blog/reply-to-app-reviews-in-any-language). This is the moment [ReplyArgus](/features) is built for. It watches your Apple App Store and Google Play reviews in one inbox and drafts an on-brand reply for each, in the reviewer's language, grounded in your past approved replies and store listing, so after a reset or a rough release nothing sits unanswered while you rebuild.

A rating count that dropped overnight is rarely a catastrophe, and often not even a real loss. Walk the six checks and you'll know which cause is yours in minutes. Then the way back up is the same no matter what knocked the number down: answer every review from here, in the reviewer's language, without letting the queue slip during a busy week. [Start free with ReplyArgus](/signup), no card, and Argus drafts your first reply in minutes across both stores, already sized for each store's limits.