Why did my app store reviews suddenly change?

Apps
1

My app’s reviews and ratings suddenly changed on the app store, with older reviews disappearing and new ones showing up. I didn’t update anything major recently, so I’m confused about what triggered this. Could this be an app store policy, a bug, or something I did in my last minor update? I need help understanding what causes review resets or changes and how to prevent losing legitimate feedback.

2

This happens more often than people think. A few common triggers.

  1. App store region or filter changed

    • App Store and Play Store often show reviews based on the user’s country or language.
    • If you switched store region on your device, or Apple/Google decided to highlight your local reviews more, old ones seem “gone” but they still exist in other regions.

  2. Sort order changed

    • The default sort sometimes flips between “Most Helpful”, “Most Recent”, or “Most Relevant”.
    • When that happens, different reviews surface and old ones go to the bottom.
    • On iOS, Apple often pushes recent reviews after certain events, even small updates.

  3. App version filtering

    • On iOS, reviews can tie to app versions.
    • If you released a new version, even a minor one, Apple might start showing “Reviews for this version” more prominently.
    • That hides a chunk of older reviews behind extra taps.

  4. Review cleanup by Apple or Google

    • Both stores run spam and fraud filters.
    • If they detect review farms, incentivized reviews, duplicated content, or weird rating spikes, they purge reviews in bulk.
    • This affects both positive and negative ones, not only the fake ones.
    • Look at your ratings per day in App Store Connect or Play Console. If you see a sudden drop in review count without a matching drop in installs, they likely did a sweep.

  5. Country specific rollout or metadata change

    • Changing app name, subtitle, store listing language, or availability can change which reviews are prioritized.
    • If your app shifted availability between countries, the “main” pool of visible reviews can change too.

  6. New rating prompt behavior

    • If you added or changed your in app rating prompt recently, lots of new reviews can push old ones down.
    • It can feel like “sudden change” even though the old reviews are still there.

What I would do next.

  • Check App Store Connect or Play Console

    • Look at total number of ratings over time.
    • If the total dropped, some got removed.
    • If total stayed similar but visible reviews changed, it is sorting or filtering.

  • Test from multiple devices and networks

    • One device logged in in your main country.
    • One with a VPN or different region.
    • Compare review lists. If you see different sets, it is region or language filtering.

  • Use the “All Versions” or “All reviews” filter in the store UI

    • On App Store scroll to see if there is a toggle for “Current Version” vs “All Versions”.
    • On Play Store scroll to the bottom and change sort and filter.

  • Check recent store policy changes

    • Apple and Google sometimes update review policies.
    • Around those dates, developer forums often fill with “my reviews disappeared” threads.
    • If lots of others report the same pattern, it is a platform sweep, not your app.

  • Audit your review sources

    • If any marketing partner, agency, or freelancer promised “review growth”, there is a good chance they used gray methods.
    • Those reviews get wiped in waves.
    • Future risk is account trouble, so cut those sources.

If nothing fits, post your review counts per week and region from App Store Connect or Play Console. People here can compare with their apps and tell you if it looks like a standard cleanup or a UI surfacing quirk.

3

Seen this a bunch of times, and yeah, it’s pretty unnerving when it happens out of nowhere.

I mostly agree with @chasseurdetoiles, but I’d add a couple of less obvious things that can cause a “what the hell happened to my reviews” moment:

  1. Silent metadata / binary changes
    You said “didn’t update anything major,” but on Apple especially, even:

    • Changing a build’s phased release
    • Tweaking availability (adding/removing a country)
    • Changing age rating or category
      can flip which review pool is surfaced. It doesn’t look like a “big” update to you, but the store treats it as a different context and starts weighting some reviews differently.

  2. A/B testing on store layouts
    Both Apple and Google silently test different layouts and ranking algos.

    • You can be in a test group where “helpful” or “recent” gets boosted hard.
    • Somebody else on your team might see a totally different set of reviews for the same app at the same time.
      This one’s frustrating because there’s nothing to “fix.” It just… changes.

  3. Rating distribution normalization
    Sometimes the average rating moves while the raw visible reviews look different. That’s usually because:

    • The platform recalculated your average after removing a batch of “low confidence” reviews.
    • It might not show all the removals explicitly, especially on the public side.
      Your historic chart inside App Store Connect / Play Console may look smoothed compared to what users see.

  4. Cross‑device cache weirdness
    The stores cache review lists pretty aggressively. So you can get a whiplash effect:

    • On one device you see the “old world” for days or weeks.
    • On another device or web, you suddenly see the “new” review ordering or filtered set.
      That makes it feel like reviews vanished in a single moment, but really the cache just expired or you hit a fresh endpoint.

  5. Language auto‑detection being overly “smart”
    Even without you changing regions:

    • The stores infer preferred language from device locale, keyboard, account history, even payment country.
    • Small changes like adding a new keyboard or traveling can cause the store to prefer a different review language cluster and hide others behind an extra tap.
      So your “old” reviews are often just in another language view.

Where I slightly disagree with @chasseurdetoiles is on how obvious review sweeps are. Sometimes the total rating count doesn’t drop much, even when a sweep happened. I’ve seen:

  • Old, long reviews quietly removed
  • Short star‑only ratings kept
    So the total star count barely changes, but specific written reviews vanish. The platform’s filters can be annoyingly selective.

What I’d actually do to sanity check this, besides their suggestions:

  • Compare web vs device view
    Open your store page in a desktop browser (logged in) and compare it to what you see on your phone. If the ordering and visible “top” reviews differ a lot, you’re likely looking at algo or test‑bucket behavior, not a real review catastrophe.

  • Take screenshots and timestamps
    When you notice a big shift, grab screenshots of:

    • Top visible reviews
    • Total ratings and average
      Then check again in 24–48 hours. If it bounces around, it’s mostly ranking logic and experimentation. If it stays “wiped,” more likely a cleanup or metadata / availability change.

  • Correlate with any external spike
    Look at whether you had:

    • A sudden spike in traffic from a campaign, giveaway, or influencer
    • A third‑party “growth” service touching your app at all
      Those are prime triggers for retroactive review filters, even weeks later.

Most of the time, nothing “you did today” triggered it. It’s usually the store’s background processes catching up, or your app slipping into a different visibility bucket because of some tiny config or policy shift. In other words: annoying, but sadly normal.

4

Short version: what you are seeing is almost certainly “store behavior” rather than something you directly triggered, but there are a few less obvious angles that @jeff and @chasseurdetoiles did not really lean on.

1. Your category and competitor context changed

One subtle thing both stores do: they rank and surface reviews relative to your “peer set.”

  • If your app got auto‑reclassified (e.g. from “Productivity” to “Business”) or you tweaked the category/subcategory, the store may:
    • Recalculate which reviews look “representative.”
    • Shift which topics and keywords it highlights.
  • In practice, that can reshuffle which reviews float to the top without any visible flag like “sorted by.”

Why it matters: even tiny metadata edits in the store listing can move you into a slightly different comparison group, which changes review surfacing.

2. Topic & keyword filters on reviews

Apple and Google both do some basic NLP on reviews:

  • They boost reviews that match what users tend to search for in your niche.
  • If your app just got a spike of reviews mentioning a new feature, bug, or keyword, the algorithm might:
    • Push those reviews way up.
    • Push “old but general” reviews down or out of the default view.

So if you recently ran a feature campaign or fixed a bug that a lot of people referenced in reviews, this can look like an “instant swap” of which reviews are visible.

Where I slightly disagree with @jeff: they focus a lot on region and sort order, which is valid, but in practice the keyword/topic weighting can be just as strong and a lot less obvious.

3. Store’s trust score for your account, not just the reviews

Another angle: the developer / publisher account itself has a sort of “trust profile.”

  • If you:
    • Had a recent rejection
    • Got a policy warning
    • Changed the legal entity or publisher name
  • The store can quietly re‑evaluate your historic review set, especially anything that looks borderline incentivized or repetitive.

This can cause:

  • Certain older, long, detailed reviews to drop out.
  • Star‑only ratings to remain, which makes it feel like “only the good / only the bad” disappeared depending on what the filters decided was low confidence.

@chasseurdetoiles mentioned sweeps, but the nuance is that sometimes the trigger is not the reviews themselves, but a shift in how the platform perceives your account.

4. Time decay is more aggressive than it looks

Both stores apply a kind of “time decay” where:

  • Recent reviews heavily outweigh old ones.
  • After a certain age, older reviews are effectively demoted unless they are extremely upvoted or highly interacted with.

So if nothing else changed, a recent burst of reviews (even small) after a quiet period can suddenly flip what you see. This is especially obvious if:

  • You had a PR mention or a small user spike in the last week.
  • You turned on an in‑app prompt long ago, then users suddenly hit that screen more due to a UX change.

It feels like “my old reviews vanished,” but the more accurate framing is “the old ones aged out of the prime spotlight window.”

5. Internal clustering per feature or release era

Some platforms internally group reviews around:

  • Feature sets (e.g. before/after adding subscriptions)
  • Major UX overhauls
  • Big pricing or monetization shifts

When your app crosses some hidden threshold (e.g. enough users talking about subscriptions), the store may emphasize reviews from that “era” and quietly bury the pre‑subscription era reviews.

So if you changed pricing, login method, or added/removes ads in the past months, the review surface can snap to “post‑change” commentary with almost no warning.

6. How I’d interpret what happened, not just “how to debug it”

Putting @jeff and @chasseurdetoiles’ points together with the above:

  • If total ratings are steady and only which reviews are visible changed:
    • Treat this as the store reinterpreting your app context.
    • Your job is not to “get the old reviews back,” but to:
      • Make sure current users are leaving high‑quality, specific feedback.
      • Align your in‑app rating prompts with your strongest UX moments.
  • If total written reviews dropped but stars remained:
    • Assume a trust / fraud filter pass.
    • Audit any campaign or partner that may have unintentionally pushed low‑quality or incentivized reviews.

I would not sink time into trying to “reverse” the change. Instead, focus on:

  • Making your current version clearly better than the old one.
  • Prompting the right users at the right time.
  • Replying to recent reviews quickly, which sometimes boosts their weight.

About the product title “”

Since the product title you mentioned is literally empty here, there is not much to evaluate directly. In general, when a product name or app name is missing or very generic, that can itself hurt clarity in the store:

Pros of tightening your product title:

  • Clearer keyword alignment for the store’s topic filters.
  • Better match between user search intent and surfaced reviews.
  • Easier for new positive reviews to become “representative.”

Cons if you change it too often or too radically:

  • The store may partially decouple older reviews from the new branding.
  • You can see a reset‑like effect in perceived history, which might resemble what you are seeing now.
  • Users who knew the old name may not immediately recognize the app.

Competitors in this thread like @jeff and @chasseurdetoiles are covering the big mechanical triggers well: region, version filters, cleanup sweeps, layout tests. Think of my additions more as “why the store mentally refiled your app,” not just which UI switches flipped.

If you want a sanity check, post:

  • A rough timeline of:
    • Any policy notices
    • Category or pricing changes
    • Major feature / monetization shifts
  • A before/after snapshot of:
    • Average rating
    • Total ratings
    • Total written reviews

With that, people can usually tell if this was a normal algorithm reweighting, a trust sweep, or you crossing into a new “era” of what the store thinks your app is actually about.