Marco had run his family's Italian restaurant in a college town for about eight years. Nothing fancy, a few dozen tables, a regular crowd of students, faculty, and locals who had been coming since the place opened. The Google listing sat at a steady 4.7 stars built up slowly, one real dinner at a time.
Then, over a Thursday and Friday, that changed. Between roughly midnight and the following evening, ten one-star reviews landed on the listing. Not two or three spread out over a normal week of mixed feedback. Ten, in under 48 hours.
What the fake reviews looked like
The pattern was consistent enough that it announced itself. Every review was vague: "terrible service," "would not recommend," "overpriced for what you get," with no mention of a dish, a server, a date, or anything a real diner tends to include when they are annoyed enough to leave one star. None of the accounts had a profile photo. None had reviewed any other business, ever. Several were created the same week the reviews were posted.
Marco never learned exactly who was behind it. There was no ransom demand, no message asking for money to make the reviews disappear, which ruled out the extortion pattern some businesses face. This was something else: a coordinated wave of fabricated negative reviews with no attached ask, just damage.
In under two days, the listing's average dropped from 4.7 to approximately 3.9. On a profile with a modest total review count, ten fake one-star ratings carry enormous weight. There were not hundreds of prior reviews to absorb the hit.
The cost showed up the following weekend
Google's local pack shows the star rating right next to the business name, before a searcher clicks through to a single review. A rating that has visibly dropped reads as a signal on its own, independent of whether anyone reads the reviews behind it.
The following weekend, online reservation requests came in an estimated 25% lower than a typical weekend for that time of year. No obvious external cause: no bad weather, no local event pulling business away, no menu change. Just a lower number of people clicking through to book, in the exact window when the rating had visibly dropped in search.
For a business running on a few dozen tables and weekend covers, a quarter of a weekend's reservation requests is not a rounding error. It is the difference between a full room and empty tables on the two nights that carry the week.
The DIY flagging attempt
Marco's first move was the one most owners try first: flagging each fake review individually through Google's own reporting tool. It costs nothing and takes a few minutes per review, so it is a reasonable place to start.
Weeks passed. Of the roughly ten flagged reviews, two came down. The other eight were marked "no violation found," with no further explanation and no path to appeal beyond resubmitting the same flag and waiting again. This is a common outcome. A single vague, one-star review from a new account does not always trip Google's automated policy check on its own, even when a person looking at the pattern across all ten reviews together can tell immediately something coordinated happened.
That gap, between what is obvious to a human looking at the whole picture and what an individual automated flag catches, is exactly where review-bombing cases tend to stall.
What changed once the reviews were submitted as a batch
After the DIY route stalled, Marco found Lizard Reviews and sent over all ten review links at once, along with a short note on timing (all posted within roughly a two-day window) and the observation that none of the accounts had any other review history.
Submitting the reviews together, with the pattern laid out rather than left for someone to notice ten separate times, made the case easier to evaluate as what it was: a coordinated attack rather than ten unrelated complaints. The batch was reviewed and accepted within a day. All ten reviews were confirmed removed within about a week, and the listing's rating recovered close to its pre-attack level as the fake ratings dropped out of the average.
"I spent three weeks flagging reviews one at a time and got two removed. I sent everything to Lizard Reviews on a Monday and by the following Monday the whole mess was gone. I wish I had done that first." "Marco," restaurant owner (composite quote, illustrative of client feedback patterns)
Dealing with a sudden wave of fake reviews?
Send us the links, all of them, in one message. We tell you within 24 hours which ones we'll take. You only pay after Google confirms the removal.
Why review bombing is a different problem than a single bad review
A single genuine one-star review is something almost every business eventually gets, and it barely moves an average built on a healthy volume of reviews. Review bombing is a different category of problem for three reasons.
- It's sudden. The damage lands in hours or days, not spread across months, so there is no time to dilute it with new positive reviews before it shows up in the local pack.
- It's coordinated. A cluster of similar, content-free reviews from new accounts in a tight time window is a pattern, and patterns are harder to argue against one review at a time than as a set.
- It hits small businesses hardest. A profile with 40 reviews and a profile with 4,000 reviews can receive the exact same ten-review attack. The smaller business sees its average collapse. The larger one barely registers it. Review bombing disproportionately punishes exactly the businesses least equipped to absorb it.
That third point is worth sitting with if you run a small or mid-sized local business. Rating volume is a buffer, and if you don't have much of one, a coordinated attack does more damage per fake review than it would on a bigger competitor down the street.
The practical lesson
If you notice a sudden cluster of one-star reviews, from accounts you don't recognize, all vague, all landing within a day or two of each other, don't spend three weeks flagging them one by one and waiting on "no violation found" replies. Document the pattern (links, posting dates, account age if visible) and submit everything together, whether that's to Google support with the pattern spelled out or to a removal service that handles bulk cases regularly. Speed matters more with review bombing than with an ordinary bad review, because the rating drop is visible in search the moment it happens, and every day it sits there is a day of searchers seeing a lower number than the business actually earned.
For a broader look at a related but distinct threat, where reviewers demand payment to remove negative reviews rather than posting them anonymously in a coordinated burst, see Google review extortion: what to do. And if you're comparing providers before deciding who handles a batch like this, our breakdown of the best Google review removal services in 2026 covers how to evaluate turnaround claims and pricing models.
Frequently asked questions
What is Google review bombing?
A coordinated burst of negative reviews, usually one-star and vague, posted within a short window by accounts with little or no other review history. It differs from an ordinary bad review because it is sudden, clustered in time, and aimed at moving the average rating quickly rather than reflecting one customer's actual experience.
Why does review bombing hurt small businesses more?
A business with a few dozen reviews has no buffer. Ten fake one-star reviews can drop the average by most of a point in under 48 hours, and that drop shows up immediately in Google's local pack. A business with hundreds or thousands of reviews absorbs the same attack with barely a visible dent.
Does individual flagging work against review bombing?
Sometimes, but slowly and inconsistently. Flagging is a one-review-at-a-time process, and Google's automated system frequently returns "no violation found" even on reviews that look obviously fake, because a single vague negative review doesn't always trip an automated policy check on its own. Submitting the whole batch together, with the pattern laid out, tends to move faster.