How to report a fake Google review

Someone left a review from a person who was never your customer. Maybe it's a competitor. Maybe it's a stranger angry about something your brand said. Maybe it's forty of them in one afternoon. This is what Google actually does about that, what it needs from you, and why the evidence that works is almost never the evidence people bring.

Short version: Google does not remove reviews for being false. It removes reviews that break a policy. Those sound like the same thing and they are not, and the gap between them is where most reports die.

"Fake" means something narrower than you think

When a business owner says a review is fake, they usually mean this did not happen. When Google says a review is fake, it means something more specific — one of these:

• Fake engagement. Posted by someone who was never a customer, or bought, traded, or incentivized.
• Conflict of interest. A competitor, a current or former employee, or anyone with a stake in hurting or helping the business.
• Impersonation. Someone posing as a person or company they are not.
• Off-topic. Not about an experience with your business — commentary on your politics, a news story, or an unrelated company.

That last one matters more than most owners realize. When a brand gets caught in a public controversy and the reviews arrive from people reacting to the news, those reviews are off-topic under Google's own policy. They are not opinions about your service. They are reactions to something else, posted in the wrong place.

Naming the specific policy is the single biggest thing you control. A report that says "this is false" is a complaint. A report that says "this is off-topic under the prohibited content policy — the reviewer describes a news story, not a visit" is a case.

The proof problem nobody warns you about

Here is the awkward part. Google does not verify purchases. It has no receipt, no booking, no record that ties a reviewer to your business.

So when you report a review as fake engagement, you are asserting a negative — this person was never here — and you cannot prove it. Neither can Google. That asymmetry is why so many individually reported fake reviews stay up. It isn't that Google sides with the reviewer. It's that there is nothing to adjudicate.

This is the hinge of the whole thing: a single suspicious review is hard to act on, and a pattern is not. One stranger with a grudge looks identical to one unhappy customer. Forty accounts posting within six hours does not.

Which is why, if you are going to spend effort anywhere, spend it on documenting the pattern.

When it isn't one review — it's forty

Coordinated review attacks have a shape, and the shape is the evidence:

• Volume that breaks your own history. A business that averages two reviews a week suddenly takes thirty in a night.
• Compressed timing. Hours, not weeks.
• Uniform rating. Almost all one star, where your normal mix is not.
• Thin reviewer profiles. Accounts with no other reviews, or a burst of reviews for unrelated businesses on the same day.
• Language that repeats. The same phrasing, or the same grievance, across accounts that supposedly never met.

Any one of those is weak. Together they describe something that cannot happen naturally, and that is a much stronger report than "this review is untrue."

Google does detect and remove coordinated attacks — sometimes in bulk, without anyone reporting. But detection is not guaranteed and it is not fast, and a brand watching its rating fall in real time is not in a position to wait and hope.

What to actually send

Report through your Google Business Profile, one review at a time, and for each one name the policy it breaks. Then, if this is an attack rather than an isolated review, escalate with the pattern:

1. Your normal rate. "This profile has averaged 0.2 reviews per week for eleven years. Its busiest day on record was five, all five stars."
2. The window. The exact date and time the cluster started and stopped.
3. The list. Every review in the cluster with its author, its timestamp, and a link to the reviewer's profile so a human can check it.
4. What the reviews have in common. Rating, phrasing, the grievance.

The reason this works better than adjectives is that a reviewer can argue about whether your service was good. Nobody can argue about whether thirty reviews arrived in ninety minutes.

What does not work

Reporting the same review repeatedly. Google does not count votes, and a cluster of coordinated reports is the exact pattern its anti-abuse systems are built to catch. You can end up looking like the attacker.

Asking customers to report it for you. Same problem, bigger.

Paying a removal service. There is no paid channel. Anyone selling guaranteed removal is selling you the outcome of a process they do not control — covered in more detail in how to get a Google review removed.

Responding angrily in public. The reply is for future customers reading later, not for the reviewer. Calm and factual reads as credible; defensive reads as guilty, even when you are right.

The timing problem

Everything above depends on one thing: knowing what your profile looked like before the attack, and exactly when it changed.

If you notice on Thursday that your rating dropped, you are reconstructing the week from memory. You cannot say when the cluster started, how many arrived, or what your baseline was — and those three facts are the entire case.

If you have a dated record, you can say all of it in one paragraph.

That is the same problem as the one in why your Google reviews disappear, pointed the other direction. There, you need proof that a review existed before it vanished. Here, you need proof that a cluster of reviews did not exist before a specific hour. Both are questions about the past, and the past is only available if someone was writing it down.

ReviewVault takes a dated snapshot of your reviews every day, so your normal rate and the moment it broke are both on record — with each review's author and profile link attached. It does not get reviews removed; nobody can promise that. What it does is make sure that when you report, you arrive with a timeline instead of an adjective.

What to take from this

Google will not remove a review for being false. It will remove one that breaks a policy — so find the policy and name it.

One suspicious review is genuinely hard to act on, because nobody can prove a negative. A coordinated attack is not hard to act on, because the pattern is visible and unnatural.

And the pattern is only visible if the history exists. That part has to be in place before the attack, not after.