A Competitor Is Leaving Fake Reviews on My App: The Response Playbook

A tight cluster of vague one-stars that all sound the same, landed within a day or two, from accounts with no other reviews and no real detail about the app: that's the signature of a coordinated attack, not a bad week. If your rating dropped overnight and the complaints are generic ("worst app," "scam," "don't download") with nothing you can actually reproduce, you're probably looking at planted reviews. The playbook is the same whether the source is a competitor, a disgruntled ex-employee, or a bought review farm: confirm the pattern, report each review to the store that hosts it, reply in public without accusing anyone, and keep your rating fed with real reviews while the reports work their way through.

The hard truth up front: you can't delete a competitor's fake reviews yourself, and neither Apple nor Google will act on a hunch. What you *can* do is document the pattern, file clean reports through the right channel, and control the one thing that's fully yours: how you respond in public, and how fast fresh reviews land on top of the fakes. Do those well and a coordinated hit becomes a bump, not a crater.

Real anger looks different from manufactured anger. A user who hit an actual bug tells you *what broke* — the screen, the version, their device, the step that failed. A planted review is allergic to specifics, because the person writing it never used the app. Before you do anything else, open the recent reviews and look for the tells.

None of these is proof on its own. Two or three together, landing in the same short window, is a pattern worth acting on. Screenshot everything now — dates, reviewer names, the exact text — before anything gets edited or pulled. Your report is only as strong as the evidence you captured while it was fresh. For the wider picture on how much of this actually happens and how the stores fight it, [are App Store reviews fake?](/blog/are-app-store-reviews-fake) walks through the detection systems on both sides.

Each store has its own channel, and the mechanics differ. Report the individual reviews that violate policy, keep it factual, and point at the *pattern*, not the person. Here's the path on each side.

Here's the counterintuitive part: replying to a review you're *certain* is fake still helps you, because the reply isn't for that reviewer. It's for the next hundred people who read the review before deciding whether to install. A calm, specific, non-defensive response to a nasty one-star signals a real team that stands behind the product, and it quietly reframes the accusation as unreliable. You never say 'this is fake.' You answer as if it were real and let the contrast speak. The same [playbook for negative reviews](/blog/how-to-respond-to-negative-app-reviews) applies here, just with an extra dose of composure.

The move is to invite the specifics the fake review conspicuously lacks. Ask what broke, offer a real channel, stay warm. If it's a genuine user hiding behind vague anger, you've opened a door. If it's planted, your measured reply makes the review look thin next to it.

That reply is under 350 characters, so it fits Google Play's hard cap with room to spare. Apple publishes no official character limit; community testing suggests a few thousand, but keeping replies tight travels safely across both stores (more on those differences in [App Store vs Google Play review replies](/blog/app-store-vs-google-play-review-replies)). It never says 'you're a fake.' It asks for the exact detail a real complaint would already have, offers a concrete remedy, and reads as confident rather than wounded. Do that consistently and your review section starts working *for* you even under attack.

The most reliable defense against a slug of fake one-stars is a steady flow of genuine reviews landing on top of them. This is where the math is on your side. Google Play weights recent ratings more heavily than old ones (a change announced at Google I/O 2019), so a wave of fresh, real five-stars dilutes an attack faster than you'd expect. On Apple the average is cumulative, but new positive reviews still sit at the top of your listing where buyers actually look. Either way, volume and freshness are the antidote. A quiet review stream is what lets a small attack leave a big dent.

Prompt happy users for reviews at real moments of delight (a completed task, a milestone, a win inside the app), never on cold app-open. And keep answering the legitimate reviews, because responses generate fresh ratings: a study of over four million reviews by Hassan et al. found users were roughly six times more likely to raise their rating after a developer replied (4.4% versus 0.7% with no reply), and Google reported at I/O 2019 that developers who respond see an average lift of 0.7 stars. Every unhappy user you win back mints a new, higher rating — exactly the fresh positive volume that pushes an attack down the page. Keeping that stream flowing is the whole argument for treating [review velocity](/blog/review-velocity) as a metric you manage, not an accident.

This isn't only a store-policy problem. In the United States, the FTC's Rule on the Use of Consumer Reviews and Testimonials took effect on October 21, 2024, and it explicitly bans creating, buying, or selling fake reviews — including reviews written by anyone without genuine experience with the product, and reviews that misrepresent the reviewer. The rule carries civil penalties of up to $51,744 per violation (FTC, 2024). A competitor paying a farm to bury your app in invented one-stars is squarely the conduct it targets.

Be realistic about what that gets you, though. The FTC pursues businesses at scale, not individual review takedowns, and it has no button to clean up your listing. If you have hard evidence of an organized, paid campaign — invoices, a paper trail, a documented pattern — it's worth reporting to the FTC and worth a conversation with counsel. For the day-to-day fight, the store report and your public replies are still the fast levers. The FTC rule is the reason the ground has shifted under the people doing this, not a same-day remedy for you.

An attack you notice a week late has already done its damage and buried the timing evidence you needed to report it. The teams that shrug these off are the ones who saw the spike on day one: they reported while the cluster was obvious, started replying immediately, and turned the review taps on before the average moved much. The difference between a scare and a real rating hit is almost always how fast you noticed.

That's the case for real-time alerting on every new review across both stores. [ReplyArgus](/features) watches your App Store and Google Play reviews in one inbox and can ping you in Slack, Discord, Telegram, or email the moment new reviews land, so an unusual burst of one-stars surfaces in minutes rather than on your next manual check. It drafts an on-brand, non-accusatory reply for each one, grounded in your past approved replies and already sized to each store's limits, so you can answer a whole coordinated wave calmly in one sitting instead of typing a hundred replies at midnight. When the attack is planted, a fast, measured, everywhere-at-once response is your best look, and it's the hardest thing to keep up by hand right when you're rattled.

A fake-review campaign feels personal, and that's exactly why the winning response is unemotional: confirm the pattern, screenshot it, report each review through the right channel, reply in public without accusing a soul, and drown the fakes in real, recent, well-answered reviews. The attacker controls a burst; you control the response and the recovery. [Start free with ReplyArgus](/signup), no card required, and Argus watches both stores, pings you the moment a suspicious spike lands, and drafts a calm, on-brand reply to every review in the reviewer's own language, so a coordinated hit meets a fast, steady answer instead of a scramble.