How to Remove Fake App Reviews From Your Listing

You can't remove a fake app review yourself: you report it, and Apple or Google decides whether it comes down. There's no delete button on a customer review the way there is on your own developer reply. Your only lever is the store's moderation channel: flag the review as a policy violation, hand over the evidence, and wait for someone to rule on it. That's the whole mechanism, on both stores.

So the honest answer has two parts. Report it cleanly, then assume the report might fail and protect your rating by replying in public while real reviews keep flowing. Removal is a slow, uncertain lever; your reply is a fast, certain one.

Because it isn't yours to delete. On both stores, a customer review is content the store hosts on the reviewer's behalf, not content you own. You can edit or delete your own [developer reply](/blog/how-to-delete-a-developer-reply-on-google-play) any time, but the review it hangs under stays put unless the store's team pulls it. Developers get a report control, a way to say "this breaks your rules," and that's it.

The fix feels like it should be in your hands. By design, it isn't: if developers could delete reviews they disliked, the rating system would be worthless. A review that genuinely violates a written policy can come down. But "I'm sure this is fake" and "this provably breaks a policy" aren't the same thing, and only the second gets action. For how common planted reviews really are, [are App Store reviews fake?](/blog/are-app-store-reviews-fake) covers the detection systems on each side.

Stores remove reviews that break a specific content rule, not reviews that are simply harsh, unfair, or wrong. That distinction decides whether your report works. Before you file, sort what you're looking at into "violates a policy" versus "a bad review I don't like."

What will *not* come down: an honest one-star from someone who hated your onboarding, a review about a bug you've since fixed, or a blunt customer. That's legitimate feedback even when it stings, and reporting it as "fake" burns your credibility for the day you have a real case. One piece of leverage against a paid campaign: in the U.S., fake reviews became illegal under the FTC's Rule on the Use of Consumer Reviews and Testimonials (effective October 21, 2024, penalties up to $51,744 per violation; FTC, 2024). If a rival is behind the wave, the [competitor fake-review playbook](/blog/a-competitor-is-leaving-fake-reviews) covers the confirm-and-report path.

Apple shows little about the reviewer (a nickname, no history), so your case leans on content and timing. The reviewer isn't notified when you report a concern, so there's no retaliation loop.

Google shows the reviewer's name and public history, so you have more to point at: a brand-new profile with one lone one-star is a real signal. Removals here are tied strictly to Google's Comment Posting Policy; a review that doesn't break it stays, full stop.

Here's the move most developers skip: reply to the fake review, in public, even though you're certain it's fake. The reply isn't for the person who wrote it. It's for the next hundred shoppers reading that one-star before they install. A calm, non-defensive answer signals a real team behind the product and reframes a vague accusation as unreliable. You never type "this is fake." You answer as if it were genuine, ask for the exact specifics a planted review lacks, and let the contrast do the work. The same [negative-review playbook](/blog/how-to-respond-to-negative-app-reviews) applies, with extra composure.

That reply lands under 350 characters, so it clears Google Play's hard cap. Apple publishes no official character limit (community testing suggests a few thousand), but keeping replies tight travels safely across both stores. And every legitimate reply nudges genuine users to re-rate: Hassan et al., studying over four million reviews, found users were roughly six times more likely to raise their rating after a developer replied (4.4% versus 0.7%), and Google reported at I/O 2019 an average lift of 0.7 stars for developers who respond.

Volume is the other half. Google Play weights recent ratings more heavily than old ones (Google I/O 2019), so a steady flow of fresh, genuine five-stars dilutes a planted wave faster than you'd guess. The developers who barely feel a fake attack are the ones who caught the spike on day one and kept the real reviews coming while the report sat in a queue.

That speed is the hard part by hand. A spike doesn't announce itself; you find it on your next manual check, often a week late, after the timing evidence has aged. [ReplyArgus](/features) watches your App Store and Google Play reviews in one inbox and pings you in Slack, Discord, Telegram, or email the moment reviews land, so a burst of one-stars surfaces in minutes. It also drafts an on-brand, non-accusatory reply for every review, grounded in your past approved replies, in the reviewer's own language, sized to each store's limits, so you answer a whole wave in one sitting. From Claude or Cursor, you can triage and reply through the [MCP connector](/agentic-tools) too.

A fake review feels like something to erase, but erasing isn't yours to do. Report it cleanly, capture the evidence, aim at a real policy line, then stop waiting on a takedown and control what you can: a composed public reply and a stream of genuine, recent reviews that pushes the fakes down the page. [Start free with ReplyArgus](/signup), no card required, and Argus watches both stores, flags a suspicious spike the moment it lands, and drafts a calm reply to every review in the reviewer's own language.