App Store Rating Recency: Why Old 5-Star Reviews Don't Help Anymore

• •A 5-star rating from last week carries more weight than a 5-star rating from two years ago
• •A recent 1-star review drags your ranking more than an old 1-star review
• •Your rating trend matters: apps with improving recent ratings can outrank apps with higher overall averages but declining trends

This is a shift from the old model, where all ratings contributed equally to your average, and your average was the primary ranking signal. Now, the recency-weighted rating matters more than the all-time average.

Why Apple made this change: they want to surface apps that are good now, not apps that were good in the past but have deteriorated. An app that was 4.8 stars in 2023 but is getting 2-star reviews in 2026 is probably worse now, even if its average still shows 4.5. Rating recency lets Apple detect this.

Note: Apple hasn't published the exact formula for how they weight rating recency. The observations here are based on ASO practitioner analysis and ranking data from tool vendors like AppFollow and Phiture.

Scenario 1: The declining app

• •All-time average: 4.6 stars (from 10,000 ratings over 3 years)
• •Recent 90 days: 3.8 stars (from 200 ratings)
• •Result: Apple may rank this app lower than its 4.6 average suggests, because recent ratings indicate declining quality.

Scenario 2: The improving app

• •All-time average: 4.0 stars (from 5,000 ratings over 2 years)
• •Recent 90 days: 4.7 stars (from 300 ratings)
• •Result: Apple may rank this app higher than its 4.0 average suggests, because recent ratings indicate improving quality.

Scenario 3: The stable app

• •All-time average: 4.3 stars (from 8,000 ratings over 2 years)
• •Recent 90 days: 4.3 stars (from 250 ratings)
• •Result: consistent — the app's ranking reflects its stable quality.

The key insight: your recent rating trend can override your all-time average. This is why some apps see ranking drops even though their overall rating hasn't changed — their recent ratings declined, and the recency-weighted score dropped.

What this means for you: you can't rely on old ratings to maintain your ranking. You need a continuous stream of positive recent reviews.

1. 1.App Store Connect: go to your app → Ratings and Reviews. You can filter reviews by date and see your rating for different time periods. Compare your recent rating (last 30, 60, 90 days) with your all-time average.

1. 2.ASO tools: AppFollow, AppTweak, Sensor Tower, and Data.ai show rating trends over time. They display your rating by month or week, making it easy to spot trends.

1. 3.Version-based analysis: compare ratings across app versions. If your latest version has a lower rating than the previous one, the update introduced a problem. This is the most actionable view — it tells you which update caused the decline.

1. 4.Country-based analysis: check your rating by country. You might have a 4.5 average in the US but a 3.8 in Japan due to localization issues. Country-specific declines can hurt your ranking in those markets.

1. 5.Set up alerts: most ASO tools can alert you when your recent rating drops below a threshold (e.g., 'alert me if my 30-day average drops below 4.0').

What to look for:

• •Is your recent rating (30/60/90 days) higher or lower than your all-time average?
• •Did a specific version update cause a rating drop?
• •Are specific countries or languages showing lower recent ratings?
• •Is your rating trend improving, stable, or declining?

1. 1.A buggy update: the #1 cause. If your latest version introduced crashes or bugs, recent ratings will drop sharply. Check your crash rate and review topics for the affected version.

1. 2.An unwanted redesign: users often react negatively to major UI changes, even if the new design is objectively better. This is the 'change aversion' effect. It usually recovers after a few weeks, but the temporary rating drop can hurt your ranking.

1. 3.New monetization: adding a paywall, increasing prices, or adding ads can trigger negative reviews. Users who were used to the free experience feel betrayed.

1. 4.iOS updates: when Apple releases a new iOS version, some apps break. If your app doesn't work well on the latest iOS, recent ratings will drop.

1. 5.Increased competition: if a competitor launches a better app, some of your users may leave negative reviews comparing your app unfavorably.

1. 6.Localization issues: if you expanded to a new market without proper localization, users in that market may leave negative reviews.

1. 7.Feature removal: removing a feature users relied on generates negative reviews, even if the removal was necessary.

1. 8.Performance degradation: if your app got slower over time (e.g., due to growing data or server load), users notice and rate accordingly.

1. 9.Neglected support: if you stop responding to support requests, frustrated users leave negative reviews instead.

1. 10.Account or data issues: any issue that causes users to lose data or access generates immediate 1-star reviews.

1. 1.Test updates thoroughly before release: the #1 cause of rating decline is buggy updates. Use TestFlight beta testing with real users before every release.

1. 2.Monitor crash rates: use Crashlytics or Sentry to monitor crash rates in real time. If a new version increases crashes, fix it immediately.

1. 3.Respond to negative reviews quickly: in App Store Connect, respond to negative reviews within 24 hours. Many users will update their review after you address their issue.

1. 4.Time your rating prompts strategically: prompt after positive moments (completed tasks, milestones, streaks). Don't prompt after errors, paywalls, or on first launch. See our guide on getting app ratings.

1. 5.Release updates regularly: active development signals a maintained app. Users are more forgiving of occasional issues if they see the developer is responsive.

1. 6.Communicate major changes: if you're doing a redesign or changing monetization, communicate with users beforehand (in-app announcement, email, social media). Informed users are less likely to leave negative reviews.

1. 7.Fix the top complaints: read your recent negative reviews and identify the #1 complaint. Fix it in the next update. Mention the fix in release notes.

1. 8.Don't force updates: if an update is optional, don't force users to update. Forced updates that break workflows generate negative reviews.

1. 9.Maintain performance: as your app grows, ensure performance doesn't degrade. Monitor load times and optimize regularly.

1. 10.Keep support responsive: a quick, helpful support response can turn a frustrated user into a 5-star reviewer. Invest in support infrastructure.

1. 1.Identify the cause: read recent negative reviews. What are users complaining about? Is it crashes, a specific feature, pricing, or something else?

1. 2.Fix the #1 issue: prioritize the most common complaint. If it's crashes, fix crashes. If it's a broken feature, fix the feature. Don't try to fix everything at once.

1. 3.Release a fix quickly: submit the fix as soon as possible. If the issue is critical, consider requesting an expedited review.

1. 4.Mention the fix in release notes: 'Fixed the crash that some users experienced when opening the app.' Users who had the issue will see this and may update their review.

1. 5.Respond to recent negative reviews: acknowledge the issue, explain that it's fixed, and ask users to try the new version. Many will update their rating.

1. 6.Prompt for ratings after the fix: once the fix is stable, prompt satisfied users for ratings. New positive reviews will dilute the negative ones.

1. 7.Monitor the trend: watch your 30-day rating over the next 2-4 weeks. If it's recovering, you're on track. If not, there may be additional issues.

1. 8.Be patient: rating recovery takes time. Even after a fix, it may take weeks for enough positive reviews to outweigh the negative ones. Don't panic if the recovery is gradual.

1. 9.Don't fake reviews: never buy reviews or use review-swapping services. Apple detects coordinated review patterns and removes them, which can further damage your ranking and may result in account termination.

1. 10.Learn from the decline: after recovery, analyze what caused the decline and put processes in place to prevent it (better testing, more gradual rollouts, improved communication).