App Store Reviews Not Showing? The Full Fix List for Apple and Google Play

If a review you left isn't showing on the App Store or Google Play, the usual reason is moderation: both stores screen new reviews before they go public, and that lag runs from a few hours to roughly a week. The next most common causes are that you're viewing a different country's storefront than the one you reviewed from, the review got filtered or removed for a policy trip, or you're seeing a stale cached version of the listing. Almost every 'my review vanished' case is one of those five things, not a bug in the app.

The tricky part is that the two stores handle each of these differently, and the fix depends on which one you're hitting. Below is the full list, ordered from most to least likely, with a fast cause-to-fix table you can scan. If you're a developer whose own reviews or replies aren't appearing, the last two sections are for you.

Neither Apple nor Google publishes a hard SLA, but in practice a new review commonly appears within a day or two and can take up to about a week. Both stores run submissions through automated moderation, and sometimes human review, to catch spam, profanity, and fake ratings before the review is public. During that window the review often shows to you (signed into the account that wrote it) but not to anyone else, which is why people think it 'posted' and then swear it disappeared.

Google Play tends to surface reviews faster than the App Store, but neither is instant. If it's been more than a week and the review still isn't public in the correct storefront, moderation isn't the answer anymore — move down the list.

This is the cause people miss most. Both stores are region-partitioned: the App Store and Google Play each serve a different set of reviews per country storefront. A review written from the U.S. store shows on the U.S. listing — not on the U.K., German, or Indian one. If you changed regions, use a VPN, or someone else is checking the listing from another country, they're literally looking at a different pool of reviews and yours won't be in it.

On the App Store this bites hard because ratings and reviews are aggregated per storefront. A developer with reviews 'missing' is often just viewing the wrong region. To confirm on the web, open the App Store or Play listing and set the country explicitly, then look again. The two stores diverge on plenty of these mechanics, and we lay the differences out in [App Store vs Google Play review replies](/blog/app-store-vs-google-play-review-replies).

If your review never went public after a week, it may have tripped a policy filter. Both stores quietly remove or withhold reviews that contain profanity, personal information, spam or promotional text, links, competitor mentions, off-topic rants, or content that looks like coordinated rating manipulation. You usually get no notice: the review just never appears to the public, though it may still show to you.

Editing helps more than you'd expect. Reviews get re-screened when you edit them, so trimming a link, dropping the profanity, or removing a personal detail and resubmitting can push a stuck review through. If you're a developer watching off-topic or clearly unfair reviews vanish on their own, that's the filter working in your favor. For the ones that stick around and shouldn't, [how to respond to negative app reviews](/blog/how-to-respond-to-negative-app-reviews) covers what to do next.

Star ratings and written reviews are counted separately. On both stores you can tap a star rating without writing anything, and plenty of people do. So the ratings count can tick up while the reviews list looks unchanged — those are silent star-only ratings, not missing reviews. Nothing is broken; there was just no text to show.

The reverse also confuses people: you post a glowing five-star review and the app's average barely budges. That's expected. Since Google I/O 2019, Play's shown rating is recency-weighted, so recent reviews count for more, but one review out of tens of thousands still rounds away. For the mechanics of how ratings actually shift, [does replying to app reviews raise your rating](/blog/does-replying-to-app-reviews-raise-your-rating) walks through the numbers.

Often, yes — the web and the App Store app both cache listing pages aggressively, so you're seeing a snapshot from before the review posted. Force-quit the store app and reopen it, pull to refresh, or on the web do a hard reload or a private/incognito tab that ignores your local cache. CDN caching at the store's own edge can also hold an old page, so if a hard refresh doesn't fix it, give it an hour and try again. It's the reason two people can see different review counts on the same listing at the same time — it resolves itself, it just isn't instant.

Different problem, same theme. In App Store Connect and the Google Play Console, reviews land on a delay behind the public listing, and the two consoles filter differently. App Store Connect only surfaces reviews for storefronts your app is available in and lags the live store by hours. Google Play Console shows all countries but defaults to filters — time range, language, device — that can hide the review you're hunting for, so clear the filters before you conclude it's gone.

The deeper issue for most teams isn't a single missing review; it's that reviews are scattered across two consoles, dozens of country storefronts, and a dashboard that only shows a slice at a time. That's the exact gap [ReplyArgus](/features) closes: it watches your Apple App Store and Google Play reviews across every storefront in one inbox, so a review can't quietly slip past you because it landed on a storefront you don't check. When one arrives, Argus drafts an on-brand reply grounded in your past approved answers, ready to approve. Keeping a fast, steady answer rate matters more than most developers think — we get into that in [review velocity](/blog/review-velocity).

Developer replies moderate too, and they follow the same rules as reviews: a reply can be delayed, or withheld if it includes a link, an email address, promotional text, or personal data about the reviewer. On Google Play there's an extra trap — replies are capped at a hard 350 characters, so an over-length reply can fail to post cleanly. Apple publishes no official reply length limit; community testing suggests a few thousand characters, so App Store replies rarely hit a wall on length.

If your reply saved but isn't public, wait out moderation, then check it strips any links or emails. A clean, specific reply clears faster and reads better anyway:

Run the list top to bottom and one of these five causes will be it: moderation, storefront, filter, rating math, or cache. If you're the developer, the fix that outlasts any single missing review is never having to check two consoles and thirty storefronts by hand. [Start free with ReplyArgus](/signup) (no card required) and Argus pulls every App Store and Google Play review into one inbox, then drafts your reply the moment it lands, in the reviewer's own language.