A review bomb is what happens when a coordinated group decides to target your business with a wave of negative reviews in a short space of time. The trigger is usually a public incident - a controversial decision, a viral social media post, a misunderstood news story, sometimes a campaign organised in a closed group somewhere you cannot see. Within twenty-four hours your rating can drop a full star and your phone stops ringing.
The instinct is to start flagging reviews one by one, replying to each, and trying to argue your way back to where you were. That is the slowest possible response and it almost always makes things worse. Effective review bomb response is structured, sequenced, and patient. This article walks through what actually works.
Recognising a review bomb
The first task is to confirm what you are looking at is actually a review bomb and not a real spike in legitimate complaints. The two require completely different responses. A review bomb has a recognisable shape: a sudden cluster of reviews from accounts with little prior history, similar language across multiple reviews, references to information the reviewers should not have first-hand experience of, and a timeline that maps onto a public event rather than onto your normal customer flow.
Real complaint spikes look different. The reviewers tend to have varied account histories, the language is messier and more individual, the timing matches the day-to-day pattern of your business, and the complaints reference specific staff members, products, or visits that actually happened.
Before you act
Do not respond to anything in the first hour. The single most damaging thing you can do during a review bomb is reply to one of the reviews while you are still angry. Your reply is read by every future customer, indexed by Google, and screenshot by anyone who wants to keep the campaign going. Take an hour. Document everything. Then make decisions.
Document before you flag
The platforms want evidence of coordination. They will not remove individual reviews just because there are a lot of them, but they will remove reviews when you can demonstrate they are part of a coordinated campaign rather than independent customer experiences. Documentation is the difference between a successful mass challenge and a slow grind through individual flags.
The documentation process
- 1
Take screenshots of every new review with timestamps. Capture the reviewer's profile, account age, and review history. Save them to a single folder with the date in the filename.
- 2
Build a simple spreadsheet listing each review by reviewer name, account age, number of prior reviews, time posted, and any phrases that repeat across multiple reviews.
- 3
Identify the trigger - the public event, social media post, or news story that the campaign is responding to. Save links and screenshots. This is the evidence of coordination.
- 4
Capture any external references to the campaign - posts on social media calling for a review attack, comments in forums, screenshots of group chats if anyone has shared them publicly.
- 5
Save everything before you start flagging. Once a review is removed, you may lose access to the evidence on the platform.
The mass-flag approach
Once you have documentation, the goal is to get the platform's attention as a coordinated incident rather than as a series of unrelated reviews. On Google, this means flagging the reviews individually but then escalating through the Business Profile support channel and explicitly framing the situation as a coordinated attack. On Trustpilot, it means using the dedicated incident reporting flow rather than the standard challenge process. On Facebook, it means using the page-level reporting tool.
The framing in every escalation is the same: this is not a spike in customer dissatisfaction; this is a coordinated campaign. Here is the trigger event. Here are the patterns across the reviews. Here is the evidence of coordination. Please review the cluster as a whole, not as individual reviews.
The reality
Platforms remove coordinated campaigns more readily than they remove individual reviews. A single fake review is hard to prove. A cluster of forty reviews posted within six hours, all referencing the same controversy, all from accounts with no prior activity in your category, is obviously coordinated and platforms will act on it - if you make the case clearly. Spend the time on framing the cluster, not on litigating each review separately.
Public response while the bomb is active
While you are working on removals, the bomb is still visible to potential customers. You need a public posture that does not feed the campaign and does not pretend nothing is happening. The best version of this is a single, calm, factual statement posted in one place - usually a pinned post on the business's main social channel - acknowledging that the business is aware of an unusual volume of reviews, that those reviews are being assessed against platform guidelines, and that the business will continue to operate normally.
Do not name the trigger event unless it is genuinely unavoidable. Do not respond to individual review bomb reviews with the same statement copy-pasted across the platform. Do not engage with the campaign on social media. The goal is to look composed, in control, and uninterested in the fight. Composure is contagious and so is panic.
The waiting period
Most review bombs have a short half-life. The campaign loses energy within a few days as the participants move on to the next thing. The reviews that remain are the ones the platforms decided to keep, and they need to be managed against the new baseline of your rating - which will be lower than it was before.
This is the moment most businesses make their second-biggest mistake. They start asking happy customers for reviews to "rebalance" the rating, all at once, in obvious panic. This produces a second cluster of suspicious activity that platforms read as gaming the system. The right move is the opposite - resume normal review capture at normal cadence and let time and volume do the work over weeks, not days.
Composure is contagious and so is panic. The goal is to look uninterested in the fight.
When the bomb is part of a larger story
Some review bombs are downstream of a media story. The reviews are not the problem - the story is the problem, and the reviews are a symptom. In these cases, removing the reviews does not change much. The story is still in search results, the comments are still on social media, and the reviews will start again the next time the story resurfaces.
The work in those cases is broader than reputation management on a single platform. It involves coordinating a public response, managing search results around the brand name, and sometimes engaging with the media directly. These are the cases that benefit from specialist help, because the moves on each front have to support the moves on the others.
When to get specialist help
Review bombs caused by genuine business problems need to be handled differently from review bombs caused by misunderstanding or by external campaigns. Knowing which is which is the first decision and it is hard to make from the inside.
If you are in the middle of a coordinated review attack and you are not sure what to do next, the first step is to stop responding and tell us what is happening. The first conversation costs nothing and we have handled this exact situation many times. We will tell you honestly whether the bomb is going to keep going, how to document it, how to escalate to the platforms in a way that produces removals, and how to position the business publicly while the campaign runs its course.