Are App Store Reviews Fake? How to Spot Them and What to Do

Yes, some App Store and Google Play reviews are fake, but far fewer survive than the internet's cynicism suggests, because Apple and Google delete fraudulent reviews at enormous scale before most people ever see them. Bought five-star praise, bot-farm ratings, incentivized reviews, and the occasional competitor smear are all real. They're also the exception, not the rule, and both stores run automated plus human detection specifically to strip them out.

The reviews you actually need to worry about aren't the obvious spam. They're the plausible-looking fakes: a cluster of generic 5-stars right after launch, or a burst of one-star reviews on your app that read like they were written by someone who never opened it. Learning to spot those, and knowing exactly what to do when they land on your own listing, matters more than the philosophical question of whether reviews "can be trusted."

Here's how fake reviews actually work, the signals that give them away, what the law now says about them, how each store polices its own listings, and the playbook for when they target your app.

Less common than the outrage cycle implies, mostly because removal is aggressive. Apple publishes an annual App Store fraud-prevention report and says it evaluates over a billion ratings and reviews a year, removing a large share flagged as fraudulent — in 2024 it removed more than 143 million fraudulent ratings and reviews from the roughly 1.2 billion submitted (Apple, reported May 2025). Google Play similarly runs ratings-and-reviews policies that prohibit manipulation and pull fake reviews, penalizing apps that buy or incentivize them.

So the realistic picture is: fakes get planted constantly, and most get swept before they gain traction. What slips through tends to be low-volume and short-lived. That's the opposite of the assumption a lot of shoppers carry, that half of all 5-stars are paid. For a legitimate app, your genuine reviews vastly outnumber any fraud, which is exactly why responding to real reviewers is the higher-leverage move: it's the signal you fully control, and it compounds.

Fake reviews come from a handful of recognizable playbooks. Knowing the source helps you read the pattern:

No single signal is proof — real reviews can be short, and fakes can be detailed. But fakes cluster around a recognizable set of tells, and two or three together is a strong pattern. Watch for these:

In 2024 this stopped being just a platform-policy issue and became a legal one. The U.S. Federal Trade Commission's Rule on the Use of Consumer Reviews and Testimonials took effect in October 2024, and it explicitly bans a list of fake-review practices: writing or selling fake and AI-generated reviews of products the reviewer never used, buying positive or negative reviews, undisclosed insider reviews, and suppressing honest negative reviews. It also prohibits fake indicators of influence like purchased followers.

The teeth are civil penalties, which run up to $53,088 per violation as of 2025 (the FTC's inflation-adjusted maximum). Because each fake review can count as its own violation, a bought batch adds up fast. The practical takeaway for an honest developer: never buy reviews, never run an incentivized-review program without clear disclosure, and never quietly delete or hide legitimate negative feedback. The safe path is boring, and it's also the legal one. Earn reviews, respond to them, and let the honest average stand.

This is federal rulemaking, not a platform quirk, so it applies regardless of which store your app lives on.

Both stores treat review fraud as a policy violation with real consequences, and both give you tools to flag suspect reviews on your own listing.

Apple runs fraud detection across ratings and reviews and lets developers report a specific review through App Store Connect using "Report a Concern" when a review is spam, fake, or offensive. Apple reviews the flag and can remove reviews that violate its guidelines. Note that Apple doesn't publish a hard character limit for developer replies either: community testing suggests a few thousand characters, but Apple states no official number, so keep replies concise.

Google Play prohibits ratings and reviews manipulation in its Developer Program Policies, removes fake reviews, and can penalize apps that solicit or buy them. In Play Console you can flag an individual review as inappropriate for Google's team to assess. Google Play also enforces a hard 350-character limit on public replies (that one *is* official), so your response has to be tight. The two stores differ in more ways than most people expect — limits, notifications, edit windows — which we map out in [App Store vs Google Play review replies](/blog/app-store-vs-google-play-review-replies).

Reporting works, but it's not instant, and the store won't always agree with you. Which is why flagging is only half the response.

If a cluster of suspicious one-stars lands on your listing — the competitor-astroturf scenario — reporting is step one, but a public reply is what actually protects you while the store decides. Future readers see your response next to the suspect review, and a calm, factual answer neutralizes the smear far better than a takedown request nobody can see. Here's the sequence:

That reply never accuses anyone of anything. It just quietly notes the missing evidence, offers real help, and speaks to the next hundred people who'll read it. That reframing is the whole point: you can't delete a competitor's plant on your own, but you can make sure it doesn't stand unanswered. And it's worth knowing exactly [what future readers see when a developer replies](/blog/what-happens-when-a-developer-replies-to-your-review) — the reply, not the takedown request, is the part that sticks.

Doing this at any real volume by hand is the hard part. A suspicious cluster arrives while you're shipping a release, and the reviews sit unanswered for a week, which is exactly when a public reply matters most. This is the gap [ReplyArgus](/features) fills: it watches both stores in one inbox, flags new reviews the moment they land, and drafts a measured, on-brand reply grounded in your own past answers and store facts, in the reviewer's own language, so a coordinated drop never sits naked on your listing while you're busy. You approve every reply by default; nothing posts without you unless you explicitly scope a narrow auto-publish rule.

No — and neither should your users. The base rate of surviving fraud on a mature store is low, the law now punishes it, and the stores remove it continuously. The rational move isn't to distrust every review; it's to read for the pattern, weight detailed reviews over generic ones, and look at how the developer responds. An app whose team answers real reviews thoughtfully is showing you something no fake can fake, and that's the best defense for your own listing too. You can't control who plants a bad review, but you fully control whether every genuine one gets a real answer.

Start free — Argus watches both stores, catches the suspicious clusters, and drafts your reply grounded in your own past answers before anything reaches the listing. No card required. [Start free](/signup), or see what each tier automates on [pricing](/pricing).