Playbook

How to handle fake restaurant reviews

The honest truth: your options are more limited than you'd like. But there's still a playbook.

First, confirm it's actually fake

Before going down the dispute path, make sure. A review that's clearly wrong about your restaurant, names the wrong dish, or references an experience that couldn't have happened — that's suspicious. A review that's just harsh but plausible isn't necessarily fake, even if it stings.

Signs a review may be fraudulent: the reviewer profile is brand new with no other reviews, the review mentions no specific details, the language doesn't match how a real customer would describe a meal, or you see multiple similar reviews appear at once.

What you can actually do

Flag it for removal via the platform

Google, Yelp, and TripAdvisor all have dispute processes. On Google, flag the review via Google Business Profile and select the reason (hate speech, spam, conflict of interest, etc.). Yelp has a similar reporting path. Removal isn't guaranteed and typically takes 1–2 weeks to get a response. Google removes a small percentage of flagged reviews — the threshold is high.

Respond publicly — calmly

Whether or not the review gets removed, respond to it. State factually that you don't have a record of this customer's visit and invite them to contact you directly. This tells other readers what's happening without making you look defensive or accusatory. Keep it short and level-headed.

Build volume to dilute the impact

One fake 1-star review on a restaurant with 12 total reviews is significant. The same review on a restaurant with 400 reviews is a rounding error. The best long-term defense against fake reviews is a high volume of genuine ones. See the playbook on getting more Google reviews.

Document everything

Screenshot the review with timestamps. Check your POS and reservation systems for records of the date mentioned. If you escalate to the platform or pursue any kind of legal action, your case is much stronger with documentation.

What doesn't work

  • ✕ Fighting fire with fire — paying for positive reviews to offset the fake ones. This violates platform policies and creates new problems.
  • ✕ Threatening the reviewer publicly in your response. It looks bad to everyone reading it and rarely leads anywhere useful.
  • ✕ Expecting fast removal. The dispute process is slow, decisions are often opaque, and platforms tend to err on the side of keeping reviews up.
  • ✕ Trying to get a lawyer involved for a single review. The cost-benefit rarely makes sense unless you're dealing with a coordinated attack.

Competitor review attacks

Coordinated fake negative review campaigns from competitors happen, though they're less common than restaurant owners fear. If you see a sudden cluster of low-rated reviews from new accounts appearing in a short window — especially mentioning specific competitors or containing similar phrasing — that's a different situation.

Document the pattern, report each review individually with as much detail as possible, and contact Google (or Yelp, etc.) support directly via their business support channels. A coordinated attack is a stronger case for removal than a single disputed review.

The honest bottom line

Fake reviews are frustrating, and the platforms don't make it easy to fight them. Your best long-term move is building a review base large enough that no individual fake review can meaningfully move your average. The operational work of generating genuine reviews is more reliable than the dispute process.

Catch suspicious review patterns early

FeedbackFountain shows you your review activity across all platforms in one place — so you can spot a sudden drop or suspicious cluster before it compounds.

Apply for Early Access →
← All playbooks | Next: Using AI for review responses →