Handling a review bomb

A review bomb is a coordinated or reactive wave of negative reviews arriving in a short window, usually from people who were never customers. It follows a news story, a social post, a political association, a viral complaint, or a dispute with a former employee.

It feels like an emergency because it is loud and fast. The response that works is slow and boring, which is the hardest part.

Is this actually a bomb or is it a real problem?

Answer this before you do anything else, because the two situations need opposite responses.

A bomb has fingerprints. Reviews arrive in a tight cluster, often within hours. Reviewers have no local history and frequently no history at all. The text references a story or a topic rather than a visit. Several reviews use similar language. Ratings are uniformly one star with no gradient.

A real problem looks different. Reviews arrive over days or weeks. Reviewers have normal profiles. Each one describes a specific experience, and the descriptions are inconsistent with each other in the way real complaints are.

If the reviews describe your actual service, you do not have a review bomb, you have a service failure with an audience. Treating that as an attack is the single most damaging mistake available, because customers can tell.

Sort them into three piles: never a customer, was a customer and is angry, unclear. Each pile gets different handling, and the sorting takes an hour.

What do I do in the first twenty four hours?

Document, report, and post once.

Document everything first. Screenshot every review with its timestamp and reviewer name before anything gets removed. Screenshot the source too, the post or article that triggered it. If you later need to make a case to a platform, this is the case.

Report the policy violations, not everything. Google is explicit that you can report any review, but only those that violate Google policies are eligible for removal, and that it does not get involved in conflict between businesses and customers. Your filing has to name a policy. Two grounds carry almost all of the weight in a bomb.

Off topic. Google's prohibited content policy does not allow content containing general, political, or social commentary or personal rants. A bomb triggered by a news story, a political association, or something the owner said publicly is off topic on its face, and this is the strongest filing available to you.

Conflict of interest. The policy names current or former employment, a contractual relationship, and other professional or personal affiliations including industry competitors and family relationships. A wave organised by a former employee or a competitor is removable on a named ground.

Mass reporting everything, including legitimate complaints, weakens your credibility with the review team and it is slow work for nothing. The escalation path runs flag from the profile, then the Reviews Management Tool, then an appeal covering ten reviews at a time. That appeal is described as one time and the word is literal. Spend it on your strongest ten.

Post one reply, on the most prominent review. Calm, short, factual, with no defensiveness and no reference to the controversy. You are writing for the person reading in three months, not for the reviewer. That person will judge you on your tone more than on the content.

Do not organize a counter wave. Asking staff, friends, or family to post positive reviews is a policy violation, it is obvious to anyone reading, and it can trigger filtering that removes your legitimate reviews along with the new ones. Google's Rating Manipulation policy specifically covers merchants directing staff to solicit reviews. The federal rule adds a second layer: 16 CFR Part 465 section 465.5 makes an insider review a violation without clear disclosure, and it reaches the business that failed to instruct reviewers to disclose. Your cousin's five star review is your exposure, not hers.

Do not threaten anyone. Section 465.7(a) of the same rule makes it unlawful to use an unfounded or groundless legal threat, intimidation, or a public false accusation to prevent or remove a review. Posting "these are all fake accounts from a competitor" under a review, when you cannot prove it, is the public accusation the section names.

Tell your team what to say. They will be asked. One sentence, agreed in advance, is enough.

If money was demanded, it is not a bomb, it is extortion. Google runs a dedicated reporting channel for negative review extortion scams and restaurants are the most frequent targets. Pay nobody, document the demand, and file it there.

Does a review bomb actually hurt my rankings?

Usually less than it hurts your rating, and the difference matters.

Your star rating drops immediately and visibly. That is the part everyone sees. The ranking effect is more complicated, because recency and volume of new reviews are signals in their own right, and a wave of new reviews is, mechanically, new reviews.

Whitespark's Darren Shaw makes the point directly: review recency increases rankings regardless of whether the new review is positive or negative. That is not comfort, exactly, but it does mean the ranking collapse people fear often does not arrive.

There is a second order risk worth knowing about, and it cuts against you. Google's policy names content exhibiting unusual volumes or patterns of review contributions as a violation, and its consumer alerts documentation says that when it detects suspicious activity it may display a public banner on the profile, impose review posting restrictions, or hide reviews. A bomb can therefore trigger a posting restriction on your own profile, which is the worst possible time to lose the ability to collect new reviews. It is another reason not to add a counter wave on top of the original pattern.

Watch it properly rather than refreshing one search. A single position check tells you almost nothing during a volatile period, and grid rank tracking shows what one ranking number hides.

The thing that does real long term damage is stopping. Businesses that get bombed often freeze their review requests out of fear, and then the wave becomes the newest thing on the profile for months. Your recent review count matters more than your total, and after a bomb the recent count is entirely negative unless you keep asking.

What does recovery actually cost in reviews?

Do the arithmetic before you decide reporting is not worth the afternoon. Replace the inputs with your own.

Before: 180 reviews at a 4.7 average. The stars sum to 846.

The wave: 40 one star reviews land. The profile now holds 220 reviews summing to 886, and the displayed average is 4.0. Seven tenths of a star, in a weekend.

Recovery by dilution alone. To get back to 4.5 you need new five star reviews. Solve it: 886 plus five per review, over 220 plus the count, has to clear 4.5. That is 208 new five star reviews. At a healthy cadence of six a month, you are looking at roughly 35 months.

Now recovery with half the wave removed. Say twenty of the forty are clearly off topic or conflict of interest and Google removes them. The profile holds 200 reviews summing to 866, and the average is 4.3. Reaching 4.5 now takes 68 new reviews, or about 11 months at the same cadence.

Twenty removals were worth 140 reviews and two years.

That is the number that should decide how you spend your first forty eight hours. The report is not the long shot and the dilution is not the whole plan. Filing two well grounded policy arguments on your strongest twenty is worth more than any asking campaign you can run, and asking is still what you do for the rest of the year.

How do I recover over the following months?

Keep asking, and ask more than usual.

The mechanism is dilution and it works, it is just slower than the arithmetic above makes people comfortable with. A hundred fresh reviews from real customers push the wave down the page and pull the average back. There is no faster path, and no vendor can sell you one that is both legitimate and quick.

Set the target from your market rather than from your anxiety. Benchmarking your review cadence against competitors gives you a number that means something, and after a bomb you want to be clearly above it.

Ramp rather than blast. The same policy that named the bomb's arrival pattern applies to yours, and a sudden cluster of five star reviews from a business that was just bombed is the least subtle pattern on the internet.

Check where the pressure actually landed. A bomb on one platform does not necessarily matter, and which review platforms matter depends on your industry more than on where the noise is loudest.

Keep the rest of the operation visible while this plays out. For a restaurant, the pages that do the most work in an ordinary week are ordinary pages, and a menu page structured so Google can read it keeps earning while the review situation resolves.

And revisit the reported reviews after a few weeks. Platform removals are inconsistent and slow, and a second report on a clear violation sometimes lands when the first did not.

Where does this playbook break down?

Three places, and the first one is common.

When the bomb is small and the profile is thin. Six one star reviews on a profile with twenty two is not a public relations event, it is an arithmetic event, and the average will not recover this quarter no matter what you post. Report what qualifies, then treat it as a volume problem for the next year.

When the trigger is still live. Dilution assumes the wave has stopped. If the news cycle, the lawsuit or the social post is ongoing, new reviews arrive faster than you can collect real ones, and the only move that matters is resolving the underlying story. Marketing advice does not reach that.

When the reviews are half true. The most difficult bomb is the one where a real incident happened and then a thousand strangers who were never there piled on. You cannot report the pile on as fabricated when the underlying event was real and public. What you can do is answer the real complaint honestly, once, in public, and report only the off topic commentary.

What to do this week

Screenshot everything today, including the trigger. Put it in one folder with dates.

Sort the reviews into the three piles. Report only the clear violations, naming off topic or conflict of interest.

Run the two line arithmetic above with your own numbers so you know what removals are worth before you decide how hard to argue for them.

Write one reply and post it on the most visible review. Have someone else read it before you post it.

Then turn your asking cadence up and keep it up for ninety days. That is the whole recovery plan and it is unglamorous on purpose.

Want a second read before you respond?

Email me at eric@seod.com with the date the reviews started, roughly how many arrived, and two or three of the review texts. I will tell you whether the pattern reads as coordinated or as a real service problem, which ones are worth reporting and under which policy, and I will write the one reply I would post.

The sorting is the part that is hard to do while it is happening to you. I am happy to be the outside eye, and I answer these the same day when I can.

Otherwise keep reading the reviews and reputation library.