App Review Moderation: What Apple and Google Filter Before You Ever See It

App review moderation is the screening layer both Apple and Google run over every user review and every developer reply. Each store checks for spam, profanity, personal information, fake or incentivized ratings, and off-topic support gripes, then removes or holds whatever breaks policy before, or shortly after, it appears. Neither store shows you the raw feed. What lands in App Store Connect and Play Console is already filtered.

That's why a one-star you screenshotted yesterday can be gone today, why a glowing five-star from a friend never shows up, and why your carefully written reply doesn't post the instant you hit send. None of it is a bug. It's moderation doing its job — sometimes in your favor, sometimes not. This walks through exactly what each store screens for, why reviews disappear, and why a reply can sit in limbo or get pulled after it went live.

Both stores publish content policies for reviews, and the categories overlap heavily. A review or a rating gets caught when it does any of the following — and the filter runs on user reviews and on your developer responses alike:

Apple applies its App Store rating and review guidelines to both user reviews and your responses. On the user side, Apple removes reviews that are spam, fake, offensive, contain personal information, or are off-topic, and it runs storefront-level filtering — a review left in one country's store shows in that storefront and counts toward that region's rating, which is why a review a colleague swears they left in Germany doesn't appear in your US view.

The part developers forget is that Apple moderates *your* reply too. When you respond to a review in App Store Connect, the response goes through a review step before it publishes — it isn't instant. If your reply includes a customer's personal details, a promotional link, or anything that trips the guidelines, it can be rejected or removed after the fact, and you won't always get a loud notification. Apple also lets you flag a specific user review with 'Report a Concern,' choosing a reason like spam, offensive material, or personal information, which sends it to Apple's team to evaluate.

One honest caveat: Apple publishes no service-level target for how long response moderation takes. In practice it ranges from minutes to about a day. If your reply has genuinely vanished rather than just pending, work through [why a developer reply isn't showing on the App Store](/blog/developer-reply-not-showing-app-store) before assuming a policy strike.

Google Play runs a comment-posting and reviews policy that reads a lot like Apple's: no spam, no fake or incentivized ratings, no hate speech or sexual content, no personal or confidential information, no impersonation, no conflict-of-interest ratings. Google enforces it with a mix of automated systems and human review. When Google's systems detect fabricated ratings or a review-bombing pattern, it removes the offending reviews and can recalculate the app's rating afterward, which is why a score sometimes moves without any new reviews arriving.

Developers flag reviews from Play Console rather than emailing support: you mark a review as inappropriate and pick the violated policy. Google evaluates the flag, but removal is not guaranteed and it isn't instant — a legitimate-looking-but-abusive review can take days to come down, if it comes down at all. Your reply is moderated here too, and Google enforces a hard 350-character limit on developer responses; anything past 350 characters is cut off, so an over-long reply effectively gets truncated by the platform rather than held. The rules differ enough between the two stores that it's worth reading them side by side in [Apple vs Google reply guidelines](/blog/apple-vs-google-reply-guidelines).

This is the question that sends people hunting for a conspiracy when the answer is usually mundane. A review you saw and can't find again went one of these ways:

If reviews are missing at scale rather than one-offs (whole days with nothing, or a listing that looks frozen), that's a different diagnosis, and the full checklist lives in [App Store reviews not showing: troubleshooting](/blog/app-store-reviews-not-showing-troubleshooting). And if the ones vanishing are suspiciously coordinated in the *other* direction, a wave of five-stars you didn't earn, the moderation you actually want is the store's fake-review detection, which we cover in [are App Store reviews fake?](/blog/are-app-store-reviews-fake).

Your response passes through the same moderation your users do, so treat it like something that has to clear a filter. The usual reasons a reply doesn't behave:

Sometimes — but set your expectations honestly. If a review genuinely breaks policy (it's spam, it's a competitor's smear, it contains a slur, it names a private person), flagging it through the store gives you a real shot. Report it from App Store Connect ('Report a Concern') or Play Console (flag as inappropriate), pick the specific violated policy, and be patient; human review takes days and removal is never guaranteed.

What almost never works is flagging a review for being *negative but true*. 'This app crashed and I lost my work' is a bad review, not a policy violation, and no amount of reporting removes it. The move there isn't moderation — it's a good public reply and a shipped fix. If you suspect an organized attack rather than honest anger, the playbook for evidence and escalation is [a competitor is leaving fake reviews](/blog/a-competitor-is-leaving-fake-reviews).

That reply does everything moderation wants and everything a prospective installer wants: it owns the problem, it deliberately keeps the order number and email out of the public text, and it points to a private channel for the specifics. It's the kind of response that clears the filter on the first pass and still reads like a team that's on it. Getting there review by review, in every language your users write in, across both stores, is the part that quietly eats a founder's week.

The reason any of this is worth the effort: answering moves the number. When Google shipped recency-weighted ratings at I/O 2019 it reported that responding to reviews correlates with an average lift of 0.7 stars, and across 4.5 million reviews Hassan et al. found users who received a response were roughly six times more likely to raise their rating (4.4% versus 0.7%). Moderation decides which reviews exist; your reply decides which way they move.

So the raw truth is that you never see the raw feed. Both stores are moderating the reviews and the replies on your behalf, catching spam and fakes and personal-info leaks, occasionally taking down something you wanted to keep. You can't control the filter, but you can control what you send into it: replies that stay inside the rules, keep private details private, and give the next reader a reason to trust you. [Start free with ReplyArgus](/signup), no card, and Argus drafts your first App Store and Google Play replies in minutes, each one in the reviewer's own language and built to clear moderation on the first pass. When the reviews turn harsh, [how to respond to negative app reviews](/blog/how-to-respond-to-negative-app-reviews) is the field guide.