You wake up to seven 1-star reviews. They all hit your profile within a 90-minute window. The reviewers are all new accounts, all with zero photos and zero other reviews. Two of them complain about a service you don’t even offer. A competitor opened down the street four weeks ago.
This is a coordinated attack, and Google has a specific path for handling it. The good news: these are easier to get removed than ordinary fake reviews because the patterns are visible. The bad news: the path requires patience and documentation. Skipping steps slows you down.
First: what counts as "coordinated"
Google looks for three signals in a coordinated attack:
- Timing cluster. Multiple reviews posted within a short window (usually a few hours to a couple of days).
- Account profile. New accounts, no other reviews, no photos, generic display names.
- Content pattern. Similar phrasing, similar complaints, or services your business doesn’t offer.
If you’re seeing at least two of these on three or more reviews, treat it as coordinated. Single suspicious reviews are handled differently, see the fake review removal guide.
The step-by-step playbook
Step 1: Reply publicly to each review
Counterintuitive, but this is the first move. You’re not writing to the reviewer. You’re writing to the next 500 people who’ll read the profile and need to know this was an attack, not a real customer experience.
Keep replies calm and pattern-focused:
“Thanks for the review. We don’t have a record of this booking and the service you describe isn’t one we offer. We’ve also received six other reviews this week with similar inconsistencies, all from new accounts. We’ve reported these to Google for investigation.”
No emotion. No accusations of who’s behind it. Just facts a reasonable reader can verify.
Step 2: Report each review individually
Open the Review Management Tool (workflow link). For each review:
- Click the three-dot menu on the review.
- Select Spam / Fake engagement / Misleading content.
- Submit.
Do all of them in one session. Don’t space them out over days, the timing cluster on your reports helps Google’s system see the pattern.
Step 3: Request manual investigation
After the initial reports, go to support.google.com/business/gethelp. Select your business. Enter "Fake text review removal request" and fill out the form.
Include in the message:
- Your profile link
- A list of every reported review with the date it was posted
- The Case IDs from Step 2
- A short paragraph explaining the pattern (timing, account ages, similar phrasing)
- Screenshots of the reviewer profiles showing no other reviews / no photos
The keyword to include in the message is "coordinated review attack", that’s the internal classification Google’s spam team uses.
Step 4: Escalate to the GBP Community
If three business days pass with no progress, post in the GBP Community with:
- Your profile link
- All Case IDs
- A summary of what you’ve already tried
A Product Expert can flag the thread for the internal spam team. This is the path that closes most coordinated attacks. The volunteers can’t remove reviews themselves but they can move your case to a human at Google.
What if the attacker is identifiable?
Sometimes you know exactly who’s behind it, a former employee, a competitor with a known grudge, an ex-business-partner. Don’t accuse them in your public reply. Document what you know separately:
- Save any DMs, texts, or emails where they’ve threatened reviews
- Note dates of disputes that preceded the attack
- Screenshot their public social posts mentioning your business
This documentation goes in your manual investigation request message, not your public reply. Google’s spam team uses it as supporting evidence; the public reply should stay neutral.
If you have hard proof of extortion ("pay me $X and I’ll take these down"), file separately at the merchant extortion form. That route moves faster.
Things that make this worse
- Filing the same report repeatedly. One round of reports, then wait. Repeated filings flag your account in a way that slows review.
- Naming names in public replies. Even if you’re right, naming the competitor in your reply can result in your reply being removed for policy violation.
- Asking customers to post counter-reviews. Google’s spam filter notices the pattern. You’ll trigger your own coordinated-attack flag and lose legitimate reviews.
- Going public on Twitter before the case is open. It feels good but rarely helps and sometimes gets the Product Experts to back off your case.
When the attack stops getting removed
About 70% of coordinated attacks get fully removed within two weeks of a well-documented manual investigation request. The other 30% involve attacks sophisticated enough to game Google’s detection, older accounts, varied phrasing, reviews spread over weeks.
If you’re in that 30%, the path forward is the same one that beats every reputation attack long-term:
- Get fresh real reviews flowing. Real customer reviews dilute the fake ones and signal to Google that your profile is active and legitimate.
- Maintain the public reply documentation. Every fake review with a calm, factual reply tells future readers and Google what happened.
- Be patient with Google’s spam detection. It improves over time. Reviews that look legitimate today may get auto-removed in three months when new pattern detection rolls out.
The companies that survive review attacks aren’t the ones who win every removal request. They’re the ones who keep getting real reviews while the attack plays out.
This post is one piece of a bigger playbook. The full guide covers all 16 common Google Business Profile crises in one place: The GBP cheat sheet.
Hit with a coordinated attack and stuck? Send us your profile link, we’ll take a look.
