A review appears from someone who has never eaten at your restaurant. Perhaps it describes a dish you have never served, or a member of staff who does not work for you. Perhaps it is a competitor. You press the flag button, wait a week, and hear nothing at all.
This happens to almost everyone who tries, and the reason is usually the same. The report was built on the argument that the review is untrue, and that is the one argument Google is not able to consider.
Google does not decide who is telling the truth
This is the part worth internalising before you file anything. Google has no record of who sat at your tables on a Tuesday. It cannot verify a meal, a booking, or a conversation with a server. It is not a court, and it will not weigh your account against a stranger's.
What it can do is check a review against its own prohibited content policies. Those are rules about the kind of content a review is, not about whether its contents happened. So the question that gets a review removed is never "is this true?" It is "which specific policy does this break?"
Stop arguing that the review is a lie. Start naming the rule it breaks.
The grounds that actually work for restaurants
It came from a competitor
Google's conflict-of-interest policy prohibits reviews left by competitors to damage a rival. This is one of the strongest grounds available, and it is often provable: open the reviewer's profile and look at their other reviews. A profile that has left five-star reviews for three restaurants within two kilometres of you and a one-star for yours is describing itself.
It is an extortion attempt
If someone has demanded a refund, a free meal, or money in exchange for taking a review down, that is a policy violation outright and Google treats it seriously. Screenshot the messages before you reply to anything. A written demand attached to a report is about as clear as evidence gets.
It is about a different business
Far more common than owners expect, particularly if your name is close to another venue's, or you have moved premises, or a delivery aggregator listed you at the wrong address. A review complaining about parking at a branch you do not have is off-topic by definition and comes down relatively easily.
It is not about a customer experience at all
Rants about your perceived politics, your staff's nationality, a news story, or a personal dispute with the owner are off-topic. So is a one-star with no text left by an account with no history — that pattern falls under fake engagement rather than opinion.
It contains a personal attack
Criticism of a business is permitted, and should be. Content that targets an individual member of staff with harassment, slurs, or claims about their private life is a different matter and falls under Google's restricted and offensive content rules.
A harsh but genuine account of a bad night. An exaggerated one. One that is unfair, or that judges your restaurant against the wrong expectations. One where the diner blames you for a delivery rider. These stay up, and on balance that is the system working — a platform that deleted every review an owner disputed would be worth nothing to the people reading it.
How to report one properly
- Flag it from your Business Profile first. Find the review, use the three-dot menu, and report it. Pick the category that matches the policy you identified — not the closest-sounding one. This route is automated and it is where most reports quietly die, but it is the required first step.
- Wait, without re-flagging. Repeat flags on the same review do not add weight and can look like abuse of the tool. Give it a few days.
- Escalate to Google Business Profile support. If it is rejected and you still believe a policy is broken, contact support through the Business Profile help channels and ask for a human review. Name the policy, quote the phrase in the review that breaks it, and attach your evidence.
- Bring records, not indignation. Booking or POS records for the date claimed, screenshots of any demand for payment, the reviewer's profile showing reviews of nearby competitors. A short, factual, evidenced report is treated very differently from an angry one.
What to do while it sits there
Assume it stays. Most do, and an owner whose plan depends on removal has no plan.
Reply to it, once, in public, and keep it shorter than you want to. Something close to: you have no record of a visit matching this description, you take the concern seriously, and you would like the chance to look into it if they get in touch directly. Then stop. You are not writing to the reviewer, who is not persuadable. You are writing to the hundred people who will read the exchange over the next year, and they are quite good at telling a fair owner from a defensive one.
There is a longer treatment of that in our guide on replying to bad reviews, and the structure there works just as well when the review is invented.
The only durable defence
One fake one-star among twelve reviews is a wound. Among three hundred, it is a rounding error that no diner will ever scroll far enough to find.
This is the uncomfortable but useful truth: you have very little control over whether a bad review appears, and a great deal of control over how much it matters when it does. A restaurant collecting reviews steadily every week is not immune to sabotage, it is merely resistant to it. We worked through the arithmetic of exactly how resistant in a separate guide on review volume.
What you must not do is respond by buying positive reviews to bury it. Purchased reviews are the single most reliable way to get a Business Profile suspended, and losing the profile costs you every real review you ever earned, which is a far worse day than the one you are currently having.
If the deeper problem is that too few honest diners leave anything at all, that is a fixable one — RatingEcho invites every diner to leave a Google review after they scan the table QR, whatever they rated privately, so the ratio moves in your favour without anyone bending a policy.