How to spot and report fake reviews on Google & App Store
Table of Content:
- What are fake reviews?
- Consequences of fake reviews for businesses
- Consequences for those posting fake reviews
- 3 Types of inappropriate reviews
- How to report a concern about malicious reviews in app stores
- How to measure whether your reporting workflow works
- What to do with the reviews that stay
- FAQs on how to report fake reviews
- Read also
New one-star reviews land after a release. Some describe a login loop. Others promote a competing service. They arrive in the same review feed, but they call for different work: investigate the login issue, and examine the promotional posts against store policy.
Start with what the reviewer actually wrote. Compare the complaint with the release log and incoming support tickets. Where the text shows a policy issue, save the evidence and report it. When a customer has found a real defect, get the issue to its owner and reply with the next step.
The reporting steps below use the current App Store Connect and Play Console paths. You will also find two examples of concern descriptions and a way to follow what happened after submission in AppFollow.
Can a developer remove a fake app review?
Developers can report reviews that appear to break App Store or Google Play policies. The store reviews the concern and decides whether to remove the content. In App Store Connect, open Ratings and Reviews and select Report a Concern. In Play Console, open Reviews and use the flag icon.
A low star rating, a short complaint, or a harsh opinion does not automatically qualify for removal. Check for concrete policy issues such as spam, threats, or off-topic promotion. Keep genuine product complaints in your support workflow.
What are fake reviews?
Fake reviews are exactly what they sound like: reviews that don’t come from real, honest users. They’re written with an agenda—to unfairly boost an app’s rating or sabotage a competitor’s reputation. Think bots dropping 5-star praise that sounds like a sales pitch, or 1-star rants from someone who never actually downloaded your app.
Sometimes they’re bought in bulk (yep, that’s a thing), sometimes they’re posted by competitors playing dirty, and other times it’s just trolls being trolls. Either way, they’re misleading, manipulative, and totally against Google and Apple’s review policies.
And here’s the kicker—they don’t just hurt your rating. They mess with your credibility, user trust, and even your app’s visibility in the stores.
So yeah, spotting and reporting them isn’t just “nice to have”—it’s essential for protecting everything you’ve built.
Consequences of fake reviews for businesses
You could Google the impact of fake reviews and find plenty of stats — and hey, data is great. But if you really want to know what happens when your app gets hit with spammy 1-stars or bot reviews, you’ve gotta hear it from someone in the trenches.
That’s why I sat down with Lucija Knezic, Customer Success Manager at AppFollow — an expert who’s been helping app teams monitor and manage reviews across Google Play and the App Store for nearly a decade. She’s seen it all: the review bombs, the shady competitors, the overnight rating drops, and the long game it takes to recover.
Lower Ratings = Fewer Installs
Me: So Lucija, let’s get into it. What really happens when fake reviews hit an app?
Lucija: Fake negative reviews can be brutal. They pull down your average star rating fast — and that’s a huge deal. We’ve seen that if your rating dips below 4.0, your app becomes significantly less visible in the stores.
Me: Wait, seriously?
Lucija: Yep. Over 80% of app store revenue goes to apps rated 4.0 or higher. That’s not a vanity number — it’s make-or-break. And here's something even more critical: we've seen cases where developers asked at what rating Play Store removed an app — and while Google doesn’t reveal a magic number, if the app consistently receives poor-quality ratings or violates review guidelines, it can get removed entirely.
Fake Reviews Hurt Conversion Rates
Me: And I’m guessing it’s not just about search visibility?
Lucija: Exactly. Even if someone finds your app, fake or spammy reviews can ruin their first impression. When you’ve got a bunch of 1-star reviews that look like they were dropped by a Google review bot 1 star script — short, vague, and repetitive — it sets off red flags. It looks untrustworthy.
App Store Trust Score Can Drop
Me: Let’s talk app store algorithms. What’s happening behind the scenes?
Lucija: Fake reviews chip away at your trust score. Both Apple and Google use it to determine how trustworthy and stable an app is. If their systems detect unnatural spikes in negative reviews — especially ones that look like Google review spam — they may lower your app’s visibility or rankings.
Review Bombing = Reputation Damage
Me: Okay, now let’s get juicy. Any wild stories?
Lucija: Genshin Impact is a textbook case. They got hit with a review bombing wave after a gameplay update people didn’t like. But the real problem? Many of those reviews were clearly spam — same phrasing, unrelated complaints, even reviews in the wrong language.
You Waste Time Fixing the Wrong Things
Me: That’s actually a nightmare for product teams.
Lucija: Totally. Fake reviews don’t just mess with your rating — they throw off your entire feedback loop. I’ve seen teams delay critical launches because they were trying to fix complaints that came from bots.
When you base roadmaps on fake data, you waste time, money, and miss opportunities.
cta_free_trial_purple
Consequences for those posting fake reviews
While the focus is on businesses, it's worth mentioning the risks for people posting fake Google reviews:
- Accounts can get suspended or banned
- Legal trouble and fines are possible
- Businesses paying for fakes face serious penalties
Fake reviews hurt your brand, tank rankings, and anger real users. Spot them? Handle them ASAP. It's worth it. So, now that we know the Why of it, let’s get to the How of it.
How to identify malicious app reviews
Many come from real users pointing out actual problems—bugs, missing features, and poor UX. These complaints are valuable. Fix the issues, tell users about it, and they might upgrade their rating.
Then there's the garbage—fake reviews that pop up when your app gets attention or when competitors try to tank your rating. These aren't real feedback. Find them and get rid of them ASAP.
The key: respond fast to real problems, and clean up the fake junk.

Characteristics of fake reviews
Here’s where it gets tricky. They're sneakier than you'd think, often hiding in plain sight among your higher ratings. Here's your comprehensive detection guide:
- Short or emotional reviews: Short or emotional reviews can be genuine. If several reviews repeat the same wording, compare their timing with product releases and support activity, then record the evidence you can verify.
- Suspicious timing: watch for sudden review clusters, especially when the wording repeats.
- Language quirks: Language alone tells you very little. Look for repeated text, promotional content, or a coordinated pattern before deciding that a review merits a report.
- Mismatched content: reviews praising non-existent features or complaining about irrelevant issues.
- Copy-paste jobs: multiple reviews with suspiciously similar wording.
- Off-topic nonsense: reviews that ramble about unrelated topics.
Most devious of all? Fake 4-5 star reviews. While they seem positive, they're actually undermining your app's credibility. A flood of obviously fake positive reviews can damage user trust just as much as negative ones. This can make your legitimate positive reviews look questionable too. You can't be sleeping on these brand reputation management strategies. Trust me on this one.
Report reviews when you can point to a specific store-policy violation. Every fake review that stays up—whether it's a one-star bomb or a suspiciously glowing five-star review—chips away at your app's reputation. The faster you clean house, the better your chances of maintaining authentic user trust.

cta_get_started_purple
Use the review as evidence, not as proof of motive. A cluster can suggest coordination; it does not identify the person behind it. Match the content to the store rule, and keep real product failures in the support queue.
| What you found | Report? | Evidence worth recording | If it stays |
|---|---|---|---|
| “App crashes on version 5.3” | Not just for being negative | Version, crash logs, support tickets | Fix, reply, retest |
| Five near-identical reviews in one hour | Review for potential manipulation | Review text, timestamps, storefronts, URLs | Continue incident investigation |
| Review advertising a competing service | Likely policy concern | Review text + promotional link | Report through store |
| Harassment or threats | Likely policy concern | Exact prohibited language | Report rather than engage |
| “Bad app” / one-star with no detail | Weak evidence alone | Other surrounding signals | Do not label fake automatically |
| Specific billing complaint, inaccurate from your perspective | Not automatically removable | Payment flow, support history | Publicly help; keep private data out |
3 Types of inappropriate reviews
1. Spam reviews
Tell-tale signs of spam reviews include:
- Copy-pasted reviews (identical text used for other apps)
- Ads for another service
- Offers of money for reviews
- Reviews containing links to websites, phone numbers, or email addresses
- Repeated strings of meaningless text across several reviews

2. Aggressive and offensive reviews
Offensive reviews often contain:
- Hate speech
- Uncensored words
- Bullying or harassment
- Sexual content
- Violence or promotion of violence
- Discrimination against others

3. Off-topic and fake reviews
Tell-tale signs of fake reviews include:
- Complaints about pricing or ads for an unrelated product
- Solicitation, political, or social commentary
- Several identical reviews
- Reviews with evidence of payment or incentives

Make sure to properly report fake reviews that match these patterns. The right reporting can clean up your app’s Ratings & Reviews section.
Here is a more detailed list of Apple’s Guidelines.
Here is a more detailed list of Google’s Guidelines.
cta_free_trial_yellow
How to report a concern about malicious reviews in app stores
While some reviews won’t even make it through app stores’ policies, the majority will still appear in your app’s Ratings & Reviews section. Once you’ve identified inappropriate, spammy, or malicious app reviews, there are a few ways to report them — either within the store itself or by using third-party tools.
How to report a fake or inappropriate review on the App Store
- Sign in to App Store Connect, open Apps, and choose your app.
- Select Ratings and Reviews in the sidebar, then choose the relevant platform.
- Find the review and click Report a Concern.
- Select the concern that fits the content. Add a concise description explaining the policy issue and the evidence you can verify.
- Click Submit. Apple decides whether the review breaches its terms. The reviewer is not notified that you filed a concern.
A useful description is specific: “Six reviews posted between 09:10 and 09:45 UTC contain the same promotional URL and near-identical wording.” Avoid claiming you know the accounts are bots or belong to a competitor unless you have independently verified evidence. Apple does not publish a guaranteed removal timeline.
Apple’s App Store Connect guide to ratings and reviews
Example A — repeated promotional spam
“This review includes a link promoting an unrelated service rather than feedback about our app. We also identified five reviews with substantially the same promotional text between [UTC time] and [UTC time]. We are reporting the content as potentially promotional/off-topic under the App Store review rules. Please review the linked entries.”
Example B — abusive content
“This review contains a direct threat toward our support staff: [quote the minimum necessary excerpt]. We are reporting the abusive content for moderation. We have retained the review date and URL for reference.”
Do not send: “Our competitor bought these bots. Delete all these one-stars immediately.” That alleges an actor and an outcome you cannot establish from the review text.
cta_get_started_yellow
How to report fake reviews on Google Play
- Open Play Console and select your app.
- Go to Monitor and improve → Ratings and reviews → Reviews.
- Locate the review that appears to breach Google's Comment Posting Policy.
- Select the flag icon, then Report.
- Monitor the decision in Play Console. Google says a specialist normally reviews a report within a few business days. If it finds a policy violation, the review is removed. If your report is rejected, you cannot report that same review again through Play Console.
Google's daily submission limit applies to the developer account. If you reach it, wait 24 hours. For off-topic complaints, separate the actual review text from your suspicions about the author; the former is what moderators can assess.
Google Play Console Help on reporting inappropriate reviews
Dealing with fake reviews quickly is crucial for your app's reputation.
Looking for fake Google Maps or Google Business Profile reviews instead? Those are handled through Google Business Profile's review reporting process, not Play Console. The steps above apply to reviews of Android apps and games listed on Google Play.
Track Report a Concern submissions in AppFollow
When your team reports reviews across two stores, the useful number is how many concerns reached the platform and what happened to them. A flagged review sitting in a queue still appears on the store page.
Open AppFollow’s Reviews Feed. The Reviews to report preset helps surface offensive or spam-looking content for inspection. Read the review, check the store policy, and use Report to submit a concern. With the appropriate store connection, the same workflow covers App Store and Google Play reviews.
cta_demo_request_yellow
For repeated patterns, you can configure Report a Concern through Auto-reply automation. Test the rule on a small sample first: a shared word or a one-star rating can also appear in genuine complaints. AppFollow can submit up to 15 concerns per source per day; additional concerns remain Pending for the next day.

As your app gets bigger, update the rules. Use past reviews that clearly violated store policy to refine your conditions.

Check the Reviews Feed or Agent Performance for the outcome. Submitted means the concern reached the store. Satisfied means the store removed the review. For Google Play, Declined indicates a rejected report. AppFollow manages submission and tracking; Apple and Google handle moderation.
AppFollow’s Report a Concern documentation
Not sure what rules to set up? Try our manual review reporting for both stores first. Set up tags and quick views for reviews with specific ratings and keywords to access them faster and save a ton of time and money.
How to report reviews to both the App Store and Google Play
If your apps are on both the App Store and Google Play, you might want to report reviews for both from one place. AppFollow lets you submit concerns for both stores from the Reviews Feed.
To set this up, you’ll need to:
- Open the Reviews Feed and choose your app.
- Use the Reviews to report preset to find reviews to check against store policy.
- Select the review and click Report. For App Store reviews, add a reason and description before submitting.
You will need to connect your profile with both consoles to be able to report reviews from AppFollow.
In a published 2020 case study, Viber submitted about 1,100 Report a Concern requests over six months. AppFollow reported that 60% were satisfied by the stores. This is Viber’s historical result, not a benchmark or promised removal rate for another app.
cta_get_started_purple
How to measure whether your reporting workflow works
Start with the status breakdown. One busy week can produce plenty of reports and very few completed decisions; the submitted count alone tells you little.
- Queue health: count Pending and Error concerns separately from Submitted. A growing Pending queue may reflect AppFollow’s daily submission cap of 15 concerns per source, rather than a store rejection.
- Observed removal share: report Satisfied alongside the size and age of the submitted cohort, broken down by store. For Google Play, where Declined is available, you may also show Satisfied ÷ (Satisfied + Declined) for completed known decisions. Keep pending and still-Submitted cases visible: excluding them can make the figure look too optimistic. Do not compute the same denominator for Apple.
- Observed processing time: if you have reliable timestamps, measure from submission to the date you first recorded Satisfied or Declined. AppFollow checks statuses periodically, so this is not the exact time Apple or Google made its decision.
- Quality check: periodically open a sample of reviews selected by your reporting rules. If you keep catching complaints about real bugs, tighten the rule and route those complaints to support.
Use the actual status labels: Pending, Error, Submitted, Satisfied, Declined (Google Play only), Deleted, and Republished. Deleted can reflect a review updated by its author and must not be counted as an accepted report.
| AppFollow status | What it means | How to interpret it |
|---|---|---|
| Pending | Queued in AppFollow | The store has yet to receive the concern. |
| Error | The concern could not be processed | Check the submission or connection. |
| Submitted | Sent to the store | A store decision may still be pending. |
| Declined | The store rejected the report (Google Play only) | Exclude from the count of satisfied concerns. |
| Satisfied | The store removed the review after the concern | Count as a confirmed removal after reporting. |
| Deleted | The report was deleted because the author updated the review | Track separately from Satisfied. |
| Republished | A review from the same author appeared again after a satisfied concern | Track separately from new concerns. |
What if Apple or Google rejects your report?
Google Play does not allow the same review to be reported again after a rejection. AppFollow also prevents resubmitting a declined concern through its workflow. Record the decision and return to the review itself: does it describe an issue your team can investigate?
If it does, reply with the next step you can actually provide. Avoid promising a fix unless its status is confirmed. Example for a verified release: “Thanks for reporting the sign-in problem. We released an update for this issue in version [number]. If you’re still unable to sign in, please contact support through [verified channel] so we can check your case.”
For a remaining off-topic review, retain the original text, the policy reason, and the moderation result. Check official escalation options only when the platform documents a valid route. Keep your product-response queue moving while the moderation record is closed.
What to do with the reviews that stay
A review spike needs two queues. Send evidence of policy violations through the store’s reporting process. Send bug reports, billing complaints, and confusing UX to the teams that can fix them. Keep the review and its outcome attached to the issue, so it does not disappear into a spreadsheet.
AppFollow helps the support team find reviews worth checking, submit concerns, and track their status across stores. The moderation decision still belongs to Apple or Google.
AppFollow’s Report a Concern documentation
cta_get_started_purple
FAQs on how to report fake reviews
How can I report fake reviews on Google Play?
In Play Console, choose your app and open Monitor and improve → Ratings and reviews → Reviews. Select the flag next to the review, then select Report. For a review of a business on Maps or Search, use the Google Business Profile reporting process.
How long does it take to remove fake reviews?
Google says a specialist normally reviews reports within a few business days. Apple does not publish a guaranteed timeline. The store decides whether the review violates its policy and qualifies for removal.
Can fake reviews hurt my app's rating?
Yes. Fake reviews, whether overly negative or suspiciously positive, can skew your app’s ratings. This affects how users perceive your app and can reduce downloads. Identifying and reporting them quickly helps maintain your app's credibility.
Can AppFollow help with reporting fake reviews?
Yes. AppFollow can surface reviews to check, submit concerns through a connected store account, and track the outcome. You can automate submission with rules. Apple and Google decide whether to remove a review.
How many reviews can I report in a day?
Google Play applies a daily limit to your developer account. If you reach it, wait 24 hours. AppFollow submits up to 15 concerns per source per day and keeps additional concerns Pending for the next day.
How do I set up automatic reporting?
In AppFollow, configure Report a Concern through Auto-reply automation. Connect the appropriate store account, set conditions that match a specific policy violation, and test the rule on a small sample before expanding it.
Read also
- Top 7 AI Tools That Read Customer Reviews for Actionable Feedback
- Best Amazon Review Management Software: 10 Tools [Price & Features]
- The best online reputation management software: Top 10 tools review
- AI Reputation Management: How to Secure Your Brand’s Reputation with Ease
- Your Comprehensive Guide to App Reviews and Ratings in 2025
- Guide to App Store Analytics: Find the Data, Follow the Clues, Grow
- Stop letting competitors dominate your niche—implement these online reputation tips
- App store review management