Handling Fake / Negative Reviews

Lesson 3: Handling Fake & Negative Reviews

Learning objectives

By the end of this lesson you'll understand the difference between a genuine negative review and a policy-violating one, how to flag a review for removal through the right channel, what Google will and won't remove, and what to do in the weeks a removal request is pending.

The distinction everything else depends on

Get this wrong and every other decision in this lesson goes wrong with it. A genuine negative review is a real customer describing a real experience — even if it's harsh, even if it's unfair, even if the business is convinced the customer misunderstood what happened. Google does not remove genuine negative reviews, no matter how the business feels about them. The correct response, covered in the previous lesson on responding to reviews, is a professional public reply — never a removal request.

A policy-violating review is something else entirely: content that breaches Google's own review policies rather than content the business simply dislikes. Fake reviews from accounts with no evidence of a real visit, spam, reviews from a direct competitor, reviews with no connection to a genuine customer experience, or reviews from someone with a conflict of interest (a current employee, a former business partner mid-dispute) all fall into this category, and Google will remove these when the evidence supports it.

The practical test: if the review is factually wrong about a service that genuinely happened, it's still genuine — customers misremember details constantly, and being wrong about a detail doesn't make a review fake. If the review describes an interaction that provably never happened at all, it's a candidate for removal.

What Google will and won't touch

Google removes spam and clearly non-genuine content, off-topic content that doesn't describe a customer experience at all, restricted content like phone numbers or URLs embedded in the review text, illegal content such as defamatory statements of false fact or impersonation, and reviews with a demonstrated conflict of interest.

Google will not remove a review just because it's harsh, just because the reviewer is factually mistaken about a minor detail, just because the business disagrees with the characterisation, or just because a genuinely bad experience happened and the business would rather it weren't public. This second list is longer in practice than most business owners expect going in — a large share of "this review is unfair" removal requests fail because the review, however unwelcome, is genuine.

How the removal process actually works

There are three practical routes. In-profile flagging is fastest: find the review on Google Maps, click the three-dot menu next to it, select "Flag as inappropriate," and choose the specific policy category. GBP Support via chat at business.google.com works better for cases needing more explanation — describe the review, provide its URL, name the violation category, attach any evidence available. The Business Redressal Form is built specifically for coordinated attacks — several fake reviews landing in a short window from new or suspicious accounts — where describing the pattern across multiple reviews at once is more effective than flagging each individually.

None of these routes guarantee removal. Google's review team makes the call based on the evidence submitted, and a request with no supporting evidence beyond "this isn't true" rarely succeeds.

A worked example: what evidence actually moves the needle

A multi-specialty clinic in Andheri, Mumbai, part of the healthcare category, received a one-star review naming a doctor who had never worked there and describing a procedure the clinic doesn't perform. The clinic's team checked its patient records for the reviewer's name and phone number across the past two years — no match. It checked the reviewer's Google profile and found the account had posted eleven other one-star reviews for unrelated businesses across the same city in the same week, all with near-identical phrasing. That combination — no patient record match, a named doctor who doesn't exist at the practice, and a pattern of near-identical text across unrelated businesses — is far stronger evidence than "we don't think this is real." The review was removed within nine days of a Business Redressal Form submission citing all three points.

Contrast that with a case where evidence usually fails: a business assumes a review is fake purely because the star rating seems disproportionate to the complaint described, with no corroborating pattern. Reviewers are entitled to rate however strongly they feel, proportionate or not — that alone isn't evidence of fakery, and a removal request built only on "this seems too harsh" almost never succeeds.

What to do while a request sits pending

Removal decisions can take anywhere from a few days to several weeks, and there's no reliable way to expedite one beyond submitting strong evidence the first time. In the meantime, respond to the review as you would to any negative review — calmly, professionally, without conceding the specific facts you're disputing: "[Name], we've checked our records and can't find a visit matching what's described here. We'd like to understand what happened — please contact us directly at [contact] so we can look into it." This does two things: it signals to every other reader that the business takes feedback seriously regardless of the review's authenticity, and it prevents the disputed review from sitting as the only visible response to a customer's concern.

The other lever worth pulling is accelerating genuine review generation during the same period, using the engine built in the first lesson of this track. A single disputed one-star review carries proportionally less visible weight against a profile that's actively accumulating new five-star reviews than against one where it's the most recent activity on the page. The same logic applies to Google reviews specifically versus reviews sitting on other reputation platforms — a dispute on one platform doesn't need to stall review generation elsewhere.

Legal options, and why they're rarely the right first move

For reviews containing specific, false statements of fact that cause genuine reputational harm — not just a harsh opinion, an actual false factual claim — and where Google has declined a removal request, an advocate-issued legal notice to Google's India entity citing the specific defamatory content can sometimes prompt a fresh review of the case. Indian courts can and do issue content-removal orders that Google complies with, but this route is slow, costly, and disproportionate for the overwhelming majority of individual review disputes. It's appropriate for sustained, organised attacks that have already exhausted Google's standard process — not a first response to one disputed review.

What practitioners get wrong

The most common mistake is treating every negative review as a candidate for removal rather than a response. Businesses that flag reviews reflexively, without strong evidence, build a pattern of failed requests and waste the effort that should go into responding well. The second is going silent while a removal request is pending, leaving the disputed review unanswered for weeks — readers see an unanswered negative review the same way regardless of whether a removal request is quietly in progress behind the scenes. The third is confusing volume with pattern: three unrelated one-star reviews in a month from different, seemingly genuine accounts isn't evidence of an attack — it might just be three unhappy customers. See reviews and AI search visibility for how sustained negative patterns, genuine or not, can factor into broader visibility beyond just the local pack.

FAQ

Can a business ask Google to remove a review just for being unfair? No. "Unfair" isn't a removal category on its own. The review needs to violate a specific policy — spam, fake, off-topic, conflict of interest, illegal content — for Google to act on it, regardless of how disproportionate the rating feels to the business.

Does flagging a review too often hurt a business's standing with Google? There's no published penalty for submitting flags, but submitting weak or unsupported flags repeatedly wastes the credibility of future, genuinely strong requests. Reserve flagging for reviews with real evidence behind the claim.

How does a suspected fake review interact with GBP suspension risk? They're separate issues. A fake review targeting your profile doesn't itself put your listing at suspension risk — that's a distinct set of triggers covered in handling suspensions and appeals. Don't let a fake-review dispute distract from monitoring suspension risk separately.

Should staff or the owner personally leave a review on their own business, even a positive one? No. That's a conflict of interest under Google's own policy and is itself removable, on top of being a reputational risk if discovered. Reviews need to come from genuine, unaffiliated customers — see review generation for how to build that pipeline properly.

Next lesson: Local content and landing pages →