Why Aren't My App Ratings and Reviews Showing? 5 Reasons They're Delayed, Hidden, or Removed

TL;DR: Most "missing" ratings and reviews are not lost - they are delayed, shown to a different audience than the one you are checking from, or still below the store's display threshold. A smaller share are removed by the store's spam filters, usually because they arrived too fast or from traffic that does not look like real users of your app. Check timing, storefront, device, and rating volume first. If reviews are actually being removed, the fix is almost always slower pacing and better-matched traffic, not more volume.

Few things frustrate a developer more than seeing a rating notification in the console and then finding nothing on the public store page. It feels like the review vanished, or like the work that produced it was wasted. In our day-to-day conversations with developers, "my reviews are not showing" has become one of the most frequent questions of the season - on both the App Store and Google Play.

This guide walks through the five most common reasons, how to tell them apart in under ten minutes, and what actually helps ratings stick.

Are Your Reviews Missing, or Just Not Visible to You Yet?

Before assuming anything was deleted, separate three very different situations:

1. Delayed - the rating exists but has not been published yet.
2. Not visible from where you are looking - it is live, but on a different storefront, device type, or summary than the one on your screen.
3. Removed - the store filtered it out or took it down.

Only the third one is a real loss, and it is usually the least common. The table below is the fastest way to work out which one you are dealing with.

Reason 1: Processing Delays Are Normal

Neither store publishes ratings instantly. Reviews pass through automated checks before they appear, and the lag varies. In practice, developers commonly see a delay of two to three days, and longer during busy periods or after a new release.

Two habits cause most of the panic here:

• Checking the same day. A review submitted this morning is often not public by tonight.
• Comparing the console to the store page. Developer consoles and public listings do not update on the same schedule, so they will disagree for a while.

What to do: Give it at least 72 hours before treating a review as missing. If you are running any review campaign, judge it on a weekly view, not a daily one.

Reason 2: Your Rating Count Is Below the Display Threshold

A brand-new app with a handful of ratings will often show no star average at all. On the App Store, listings below the threshold display "Not Enough Ratings." Google Play also needs a minimum volume before an average appears.

This matters more than most developers expect. With a very small rating base, every new rating is checked against very little history, which makes the listing more sensitive to anything unusual. In our experience, apps with a tiny base see much lower display rates for new ratings than established apps do.

What to do:

• Build the base gradually and from real usage first. Turn on in-app rating prompts at a natural moment - after a completed task or a successful session, not at first launch.
• Make sure the users arriving at your app actually match what the app does. Users who searched for a relevant keyword and found what they needed are far more likely to leave a rating that sticks. This is where well-targeted keyword installs help: relevance builds the rating base, not raw volume.

Reason 3: You're Looking at the Wrong Storefront or Device

Ratings are not one global number.

• App Store: Ratings and reviews are tied to each country's storefront. A review left in Germany will not show on the US page.
• Google Play: Ratings are shown per country and per device type (phone, tablet, Chromebook, wearable). A phone user and a tablet user can see different averages for the same app.

This also explains a related complaint we hear constantly: "the ranking on my phone doesn't match what the data tool shows." Device model, OS version, signed-in account, and region all change what a single phone displays. A tracking tool aggregates; your phone shows one slice.

What to do: Before reporting a problem, confirm the country, device type, and account you are checking from. If your campaign targeted a specific country, check that country's storefront - through a tracking tool or a correctly configured test device.

Reason 4: The Rating Summary Was Reset After an Update

On iOS, developers can choose to reset the summary rating when they release a new version. If someone on your team ticked that option, the star average starts from zero and older ratings stop counting toward the headline number. Written reviews may still exist, but the summary that users see on the listing looks empty.

What to do: Check your recent version release settings in App Store Connect. Resetting can make sense after a major fix that resolves the complaints behind old low ratings - but it should be a deliberate decision, not an accident.

Reason 5: Reviews Are Being Filtered or Removed

This is the case everyone fears, and it does happen. Both stores remove reviews that look like spam, are off-topic, or appear to violate their policies, and Apple's terms give it discretion to remove reviews without a detailed explanation.

From what we see across many campaigns, removals cluster around a few patterns:

• Bursts. A large number of ratings landing in a short window is the single clearest risk factor. Developers who pushed a lot of ratings in a few days have seen large-scale removals - and on Google Play, alerts on the account.
• Mismatch with real activity. Ratings rising much faster than organic downloads, or arriving in countries where the app has almost no users, look unnatural.
• Thin rating base. As covered in Reason 2, a small base makes everything new more visible to filters.
• Repetitive content. Very similar wording across many reviews.

Even modest daily volume can be cleared in bulk if the overall pattern looks off - so pacing is about the total shape of activity, not only the daily number.

What to do:

1. Slow down. Spread ratings over weeks, not days. Avoid concentrated pushes, especially on a new listing.
2. Grow ratings alongside downloads. Ratings should rise roughly in step with installs and active users.
3. Prioritise quality over quantity. A small number of detailed, relevant reviews per day beats a large batch of short ones.
4. Watch for warnings. If you receive a store notice, pause all non-organic review activity and fix the root cause before doing anything else.

If you use an external review service, read the retention terms carefully. ASOWorld's Guaranteed Reviews, for example, states that more than 80% of reviews should remain for at least 30 days, or the order is refunded - a concrete, checkable standard rather than a vague promise. No provider can guarantee that a store will never remove a review, and you should be wary of anyone who claims otherwise.

A 10-Minute Self-Check

Run through these questions in order. Stop at the first "yes."

How to Build Ratings That Actually Stick

Long-term, the apps with stable ratings share a few traits:

• Relevant traffic first. Users who find exactly what they searched for leave better and more durable ratings. Keyword targeting and listing clarity do more for rating quality than any review campaign.
• Smart in-app prompts. Apple's native prompt can be shown at most three times in 365 days per user, and Google's in-app review flow also has quotas - so timing matters. Ask after a moment of success.
• Fix the cause of bad reviews. If a recent update introduced a bug, new five-star reviews will not outweigh fresh one-star complaints. A structured process for negative review and reputation management - diagnose, recover, improve sentiment, then monitor - protects the rating over time.
• Reply to reviews. Responses show active support to future users and sometimes lead reviewers to update their rating.
• Treat rating as a conversion lever. A higher average turns the same traffic into more installs. If your rating is hovering below 4.0, work on improving organic conversions and user experience alongside the rating itself.

Common Misconceptions

"If I order more ratings, more will stick." Usually the opposite. Volume beyond what your organic activity can support raises the chance of bulk removal.

"A missing review means the service didn't deliver." Check delay, storefront, and threshold first. Most "missing" reviews turn up within a few days.

"Ratings and reviews are the same thing." A star rating without text counts toward the average but will never appear as a written review.

"The store owes me an explanation for every removal." Both stores reserve the right to remove reviews; detailed explanations are rare. Focus on the pattern you can control.

FAQ

How long does it take for an App Store review to appear?

Often two to three days, sometimes longer after a release or during peak periods. Wait at least 72 hours before treating it as missing.

Why does my app say "Not Enough Ratings"?

Your rating count in that country is below the App Store's display threshold. The average appears once enough ratings accumulate.

Why can my colleague see reviews that I can't?

Ratings and reviews are tied to the storefront (country) and, on Google Play, to the device type. You are likely viewing a different slice of the listing.

Why did a group of reviews disappear at the same time?

Batch removals are usually caused by automated integrity filters, often triggered when many ratings arrive in a short window or out of line with real usage.

Can I get deleted reviews restored?

Rarely. It is more productive to slow pacing, improve traffic relevance, and let new ratings build steadily.

Do keyword installs help my rating?

Indirectly. Relevant users who find what they searched for are more likely to rate the app, and to rate it well. They help build the base; they are not a substitute for a good product experience.

Ratings that stick come from the right users at a believable pace. If you are not sure whether your problem is visibility, conversion, or rating quality, start with a diagnosis before spending more.