Why did my google play rating drop

A practical checklist to diagnose why your Google Play rating suddenly dropped — and what to do about it.

A rating drop is always caused by something. Here's how to find it.

Seeing your Google Play rating go from 4.3 to 3.8 overnight is alarming. But it's always caused by something specific — a bad update, a wave of negative reviews, a change in how Google weights ratings, or occasionally something entirely outside your control.

Work through this checklist in order.

Step 1: Check when the drop happened

Go to Google Play Console → Ratings → Rating over time. Identify the exact date or date range when the drop began.

Now compare that date to:

  • Your last app update release date
  • Any server-side change you made (API, backend, configuration)
  • A spike in 1-star or 2-star reviews visible in the Reviews tab

A drop that coincides exactly with an app update is almost certainly update-related. A drop with no corresponding update may be a Google Play algorithm change or a review manipulation issue.

Step 2: Read the recent negative reviews

Sort your reviews by "Most recent" and filter by 1-star and 2-star. Read the last 20–30 negative reviews carefully. Look for patterns:

  • Same complaint repeated: "App crashes on Android 14," "Can't login," "Notifications broken" — these point to a specific bug
  • Timing mention: "Used to work fine, broke after last update" — confirms an update regression
  • Different devices mentioned: If reviews mention specific device models (Samsung Galaxy S24, Pixel 8), there may be a device-specific bug
  • No specific complaint: One-word reviews ("Bad," "Doesn't work") with no detail often indicate review manipulation from a competitor or spam wave

Step 3: Check your crash rate

Google Play Console → Android vitals → Crashes & ANRs. Look for a spike in crash rate corresponding to your rating drop date.

A crash rate above 1.09% (Google's bad behavior threshold) affects your store visibility and can trigger a warning from Google. If you see a spike here, the rating drop is directly related.

Step 4: Check for a Google Play algorithm update

Google periodically changes how ratings are calculated. The biggest change in recent years was Google's shift to rating weighting by recency — newer ratings count more than older ones. This means:

  • If you had a great rating 2 years ago but have been getting average reviews recently, your rating will trend down even if you haven't made any changes
  • If you made a bad update 6 months ago and recovered, older bad reviews are slowly being de-weighted

Check the ASO community forums (r/androiddev, AppFollow blog) for mentions of a Google Play algorithm update around your drop date.

Step 5: Check for review manipulation

If your rating dropped without a corresponding spike in crash reports, no recent update, and no clear complaint pattern — you may be the target of fake negative reviews.

Signs of review manipulation:

  • Multiple reviews posted within hours of each other
  • Generic complaint language ("This app is terrible, don't download")
  • Reviews from accounts with no other review history
  • Reviews mentioning competitors or unusual topics unrelated to your app

What to do: Flag each suspicious review using the "Flag as inappropriate" button in Play Console. Google reviews flagged reports and removes reviews that violate policy, though this can take weeks.

Step 6: Respond to negative reviews immediately

For every 1-star review with a real complaint: write a clear, human response. Acknowledge the issue. Say what you're doing about it. Invite them to email you.

Users who receive a thoughtful developer response sometimes update their rating. More importantly, future users reading the review thread see a responsive developer — which partially mitigates the damage of the negative review.

Do not respond defensively. Do not argue. Do not offer incentives for changing the review (this violates Play policy).

How to recover a dropped rating

There's no shortcut. The path back is:

  1. Fix the underlying problem (bug, UX issue, whatever caused the negative reviews)
  2. Ship the fix as an update with clear release notes: "Fixed crash on Android 14 — thank you for your reports"
  3. The fix update often generates positive reviews naturally from users who notice the improvement
  4. Implement a proper in-app review prompt (see our guide on asking for reviews) to increase the volume of positive reviews over time

Rating recovery typically takes 4–8 weeks of consistent positive reviews to meaningfully move the average back up.

What not to do

  • Do not ask friends and family to leave 5-star reviews to compensate — Google detects coordinated review patterns and can remove them or penalise your listing
  • Do not respond to all negative reviews with the same template — users can see your response history and templated responses look dismissive
  • Do not release a new update just to "reset" the rating — ratings are tied to your app, not individual versions

Apporb's unified review inbox shows all your Google Play and App Store reviews in one feed — filter by 1-star, respond instantly, and never miss a critical issue. Free plan at apporb.com.

← Back to all posts