There is no official fake review checker. What Google actually publishes

Google does not publish a fake review checker. No score, flag or setting in a Business Profile tells you whether a review is genuine, and no field in the API carries one. Nothing Google hands a business owner answers the question.

What exists is a policy naming the behaviour, a report form that produces a decision, and a short list of fields in the API. None of those is a detector, and the difference matters: acting on a guess is how a business ends up publicly accusing a real customer.

What the API actually tells you about a reviewer

Each review from the v4 Business Profile API carries a Reviewer object, documented as “Represents the author of the review.” It has three fields.

Field	What Google’s reference says about it
displayName	“The name of the reviewer. Only populated with the reviewer’s real name if isAnonymous is false.”
profilePhotoUrl	“The profile photo link of the reviewer. Only populated if isAnonymous is false.”
isAnonymous	“Indicates whether the reviewer has opted to remain anonymous.”

That is the entire author record. No account age, no contribution count, no review history, no location, no authenticity signal, and no reviewer identifier, so two reviews cannot be tied to one account through the API. The review’s own identifier is documented as “The encrypted unique identifier.”

The rest is as plain. comment is “The body of the review as plain text with markups.” and createTime is “The timestamp for when the review was written.” Text, a rating, a name that may not be a name, a timestamp. That is what an automated judgement built on this API has to work from.

FAKE_ENGAGEMENT is a policy name, not a verdict on a review

Search for a checker and you can end up at the string FAKE_ENGAGEMENT, which looks like Google marking a review as fake. It is not. It is one value in the PolicyViolation enum, and the field it arrives in is documented as “Optional. Output only. The policy violation that resulted in rejection. Only populated if reviewReplyState is REJECTED.”

Rejection of your reply, not of the review. Google will tell you through the API that something you wrote breached the fake engagement policy, never that a review did. The other rejection reasons are in what Google publishes when a reply is rejected.

The value reads, in full:

Content that violates our policy on fake engagement isn’t allowed. Fake engagement includes incentivized content, content intended to manipulate a place’s rating, and other content that doesn’t represent a genuine experience.

What Google publishes about the behaviour itself

The policy behind the name is the Fake Engagement section of Google’s prohibited and restricted content page, which opens:

Contributions to Google Maps should reflect a genuine experience at a place or business. Fake engagement is not allowed and will be removed.

Four bullets follow. Two are about content, which you can assess to a degree:

• “Content that is not based on a real experience or does not accurately represent the location or product in question.”
• “Reviews or ratings that have been paid for, directly or in kind.”

Two are about accounts and devices, which you cannot assess at all:

• “Content that has been posted from multiple accounts by or at the request of one person.”
• “Content that has been posted using an emulator or other device tampering service, modified operating system, or other method to mimic genuine engagement, manipulate sensor data or results, or otherwise thwart or confuse normal operations.”

Read the last bullet as the answer to the original question: emulators, tampered operating systems and sensor data are signals held inside Google and available to nobody outside it. The adjacent Rating Manipulation section names the same class of evidence: “Content exhibiting unusual volumes or patterns of review contributions that are indicative of efforts to manipulate a place’s rating”. Volumes and patterns across Maps, not across your profile.

The bullet you can sometimes evidence yourself is “Content that is based on a conflict of interest.” Google’s examples include current or former employment, contractual relationships, industry competitors and familial relationships.

What a third-party checker is doing

We are not naming one. We have tested none of them, and we will not repeat a detection claim on the strength of a vendor’s description of its own product.

What can be said is what the inputs are, because they are fixed. A tool inspecting a review from outside Google has the text, the star rating, the displayed author name, the date, and whatever that author’s public Maps contributions page shows. From those it can produce a confident-looking label, “This review is likely fake”, which is an inference from public information rather than a lookup.

The same limit applies to pattern-spotting by hand. A burst of one-star reviews in an afternoon from accounts with no other activity is worth reporting as a pattern. It is not proof: a local news story or a viral post produces the same shape. Treat it as a reason to report, never as a finding you act on publicly.

The report is the route to a decision you can look up

Google’s own detection does not wait for you to file anything. The reporting page says “To remove reviews identified as spam, Google uses automated spam detection.”, and concedes the error case in the same section: “Occasionally, the system may also mistakenly remove legitimate reviews. If this happens, contact support for assistance.” Reviews are therefore removed with no report behind them, and legitimate ones are sometimes caught.

What a report gets you is not Google’s signals for the first time, it is a decision with a state you can look up, and none of the three statuses it can carry says which policy was considered. The wait Google publishes, those statuses with Google’s definition of each, and the single appeal after a refusal are set out in how to report a fake Google review.

The same page draws the boundary a report has to clear. “Google doesn’t get involved in conflict between businesses and customers.” A review you believe is dishonest about what happened is a conflict. A review that breaches one of the bullets above is a policy violation, and only the second gets acted on, which is why removal is the narrow case.

The one signal you have and Google does not

Your own records. Google cannot see your bookings, invoices, door log or kitchen tickets. A specific absence in them is material you can put in a report. How much it counts for is not something we can tell you: we found nothing on the five pages cited below that ranks one kind of evidence against another, or that says what a report needs to carry.

Be precise about what an absence proves, starting with the chance that your own records are the incomplete thing. A booking can sit under another name, a walk-in may never have been written down, and an hour of a system being down leaves the same gap as a visit that never happened. A displayed name with no matching transaction is weak for a second reason as well, because the field description says the display name is only the reviewer’s real name when isAnonymous is false. A review describing a service you never offered, a site you never operated, or a date you were closed does not rest on your records being complete, and Google can check it without any account data.

None of it belongs in a public reply. Reply for the next reader, say plainly that you have no record of the visit, offer a way to get in touch, and stop. The method is in how to respond to a negative review.

The figures Google does publish, and the ones it does not

Google does publish one class of number, annually and platform-wide. In the highlights from its 2025 Trust & Safety Report, Google says its “advanced systems and expert analysts blocked or removed over 292 million policy-violating reviews, while publishing more than 1 billion helpful reviews.” The year before, the same blog reported that Google “blocked or removed more than 240 million policy-violating reviews from 2024, the vast majority of which were removed before they were seen.”

Read those for what they are: counts of enforcement across the whole of Maps, published after the year they cover. They are not a detector, they say nothing about any individual review, and no equivalent figure reaches your profile or the API. What we found nowhere is a detection rate, a removal rate, or an estimate of what share of the reviews standing on Maps today are fake. Percentages of that kind circulate in this category and in the copy of review tools. We could not trace them to anything Google publishes, so we are not repeating them, including the ones that would make this page look better informed.

The honest answer is short. No checker can tell you whether a review is fake, because the evidence that decides it is not public. Read the four bullets, find the one your review actually breaches, evidence it from your own records, and report it once.