An evidence guide for suspected fake reviews
Fake Google Reviews: Evidence, Signals and Next Steps
“Fake” is a serious conclusion, and an unfamiliar name alone does not establish it. A strong assessment looks at the review’s content, context, and connection to Google’s policies rather than guessing at the reviewer’s identity. This guide helps a Cyprus business build a fair, usable record before deciding whether to report.
01
What makes a review potentially inauthentic
Google’s policy on fake engagement addresses content that does not represent a genuine experience or that is posted to manipulate a place’s reputation. Signals can include coordinated wording across several accounts, incentives for a particular rating, reviews from a competitor or employee, repeated promotional material, or activity unrelated to the place.
One unusual detail is not a verdict. A new account, a name you do not recognise, a short comment, or an angry tone may occur in a genuine experience. Assess several signals together, and avoid labelling a person a fraud in a public reply when the facts are not established.
02
A missing customer record is not proof
Search the records that reasonably relate to the date and service, including alternate spellings, group bookings, walk-ins, delivery orders, and third-party reservations where appropriate. Ask relevant staff for context without sharing more personal information than necessary. Keep the result as an internal note, not as a public accusation.
The absence of a matching record can support a question for Google, but it does not prove the review is fake. Records can be incomplete, a customer may use a different name, or the review may concern a conversation rather than a purchase. Phrase the report as an evidence-based concern and separate what you know from what you infer.
03
Build evidence that can be checked
Keep the review URL, screenshots with the date captured, the exact text, and a short chronology. If several reviews appear connected, record the common wording, timing, account patterns, or incentives without trying to identify private individuals. Preserve original files and do not alter images, create accounts, or ask others to report content they have not seen.
If the review contains personal information, threats, or targeted harassment, note those separate policy concerns rather than forcing everything into “fake.” Each issue may have a different reporting category. A concise table of facts and source links is usually clearer than a long emotional narrative.
04
Report the policy issue, not the business dispute
Use your Business Profile or Google’s review-reporting flow, choose the closest reason, and describe the observable signals. Google removes policy-violating content, not merely content that is negative or inconvenient. A report should ask for policy review and should not demand a guaranteed result.
Track the report in Google’s Reviews Management Tool where available. If Google rejects an eligible report, the tool may provide a one-time appeal. Add relevant evidence once, respond accurately, and avoid duplicate submissions that add noise. Google decides whether its policy threshold is met.
05
Keep the public response measured
While a report is pending, a short response can acknowledge the concern without confirming or denying private customer details. Invite the writer to contact the business through an appropriate channel, and do not offer incentives for a changed rating. A calm reply protects the conversation without turning uncertainty into a public allegation.
This approach applies across Nicosia, Limassol, Larnaca, Paphos, and the Famagusta district; a location does not change the evidence standard. For a structured review of the material, email papadopoulou@remove.cy. We can discuss the policy question, without promising removal, a timeline, a price, or legal representation.
Want a second look?
Send the facts, not the frustration.
Email the public link and a concise description to papadopoulou@remove.cy. The conversation is policy-focused and is not a guarantee or legal service.
Email the team