Why it matters for analysis

A fake Google review distorts more than the rating. Clusters of fake negative or positive reviews can make a topic look like it is rising or falling when nothing changed. Before acting on a sudden shift, check whether the reviews behind it look genuine.

What Google already does

Google says its systems check each review as it is posted and keep checking afterwards, looking at the content, the account's history and unusual activity on the place, such as a burst of reviews or an unusually high number of one- or five-star reviews in a short period. Much fake content is removed before anyone sees it.

Signs in your data

  • Bursts: many reviews for one store in a day or two, unlike its normal flow.
  • Similar wording across reviews, or across your stores and competitors'.
  • Vague content with no specific detail.
  • Details that do not match: products you do not sell, a layout that does not exist.
  • Reviewer histories that look unusual, such as many reviews of distant businesses on the same day.
  • Off-topic content: political rants or unrelated complaints.

How to check

  1. Compare the cluster's timing and wording.
  2. Check your records for matching visits or orders.
  3. Look at the reviewers' public profiles.
  4. See whether competitors received similar reviews at the same time.

Free review snapshot

Want this done for your own reviews?

No commitment. We use your details only to send your snapshot and follow up. Privacy policy

What to do

  • Report reviews that break Google's policy through the Reviews Management Tool.
  • Reply calmly in public.
  • Flag suspected fakes in your analysis so they do not drive decisions until checked.
  • Keep genuine negative reviews in your data, however unwelcome.
Reporting

How to report and remove fake Google reviews.

How to report and remove fake google reviews

An example

A store's staff complaints tripled in two days. Every new review was one star, under twenty words, from accounts that had reviewed several of the brand's competitors the same week. The cluster was flagged, reported and excluded from that month's staff analysis; the store's real staff trend was unchanged.

Common mistakes

  • Assuming every bad review is fake.
  • Deleting genuine reviews from your dataset.
  • Acting on a spike without checking it.
  • Posting fake positive reviews in response.

Common questions

Can we prove a review is fake?

Rarely with certainty; build a case from several signs.

Do fake positive reviews matter?

Yes; they distort your data and break Google's policy if solicited.

What if competitors are behind it?

Report through Google and keep evidence; Google's policy prohibits content posted to undermine a competitor.

Should we exclude suspected fakes from reports?

Flag them and show results with and without them until checked.

Checklist

  • Bursts and clusters checked.
  • Wording compared.
  • Records searched.
  • Policy violations reported.
  • Suspected fakes flagged in analysis.

In short

Look for bursts, similar wording, vague or mismatched details and unusual reviewer histories; check before acting, report policy violations, and keep genuine negative reviews in your data.

A simple process

When a topic or store spikes, check the reviews behind it before reporting it. If they look suspicious, mark them, report the ones that break policy, and show the month's figures with and without them until Google's decisions come back. Record the outcome so you learn which patterns tend to be removed.

Doing this with Falcon

Falcon builds the theme list from your own reviews, then labels every review against it with a multilingual model, scoring sentiment for each mention and keeping the exact quote behind each label. Texts too short to judge are marked unclear rather than guessed, and low-confidence labels are flagged for a person to check. Negative share by topic, location and month then shows what is rising where, with small samples flagged.