GOOGLE REVIEW GUIDE · UK BUSINESSES
Google review bombing: responding to a coordinated attack
A local dispute or widely shared post can be followed by a wave of Google reviews. The priority is to record what happened and distinguish people describing real experiences from accounts responding to a call to action. We can assess the pattern and the individual reviews together.
A sudden wave is a pattern to explain—not a reason to dismiss every complaint in it.
Two very different reasons for the same spike
Illustrative scenarios, not client results.
Twenty bookings were cancelled.
A cluster of complaints may reflect twenty real experiences. Compare the dates and details with your operational records.
A public post asks strangers to leave one star.
Preserve that post and its timing. It may help explain the pattern, but still check the evidence for each affected review.
Build a timeline before the pattern changes
Record the first unusual review, the following submissions, and any public post or message that appears connected. Save links and screenshots with dates. A simple list makes it easier to distinguish a cluster over a few hours from ordinary feedback spread across several weeks.
Separate coordinated activity from extortion
If someone demands payment to remove the reviews, preserve that communication and use the dedicated extortion guidance. Without a demand, focus on the review evidence and any documented coordination. Do not encourage supporters to post experiences they have not had to offset the ratings.
Turn the wave into a timeline
- A dated list of review links, ratings, and screenshots.
- Your usual review pattern and the timing of the sudden change.
- Public posts or messages calling for reviews, where available.
- Relevant operational records showing whether a real incident could explain the complaints.
Keep original records. Share only what is relevant, and avoid putting private customer or staff information into a public reply.
Respond to the pattern without losing the individual cases
These steps explain the platform’s published process. Reporting is available without paying for our service.
- Group the affected review links into one incident record while documenting the concern for each.
- Report reviews with supported policy issues through Google’s tools; explain the wider pattern where the process allows supporting information.
- Track the outcomes and use eligible appeals where appropriate. If a direct demand arrives, retain it and follow the extortion route.
FICTIONAL EXAMPLE · NOT A CLIENT RESULT
The event behind the spike matters
Terrible attitude from the staff. I would not recommend booking here.
Several reviews appear after a post about a venue. Some may come from people who never attended; others may relate to a real cancelled event. Booking records and the public post can help explain which concerns require further assessment.
Bring the case to a specialist
Start with your Business Profile link, the affected dates and an outline of any related incident. We assess the evidence across the group, explain which concerns appear supported and identify genuine complaints that should be handled separately.
Already tried the standard reporting process? We can assess whether further options are available for your case.
Explore our Google review removal serviceOfficial guidance
Platform processes can change. These are the sources used for the policy and reporting explanations in this guide.