What should you do if a competitor is leaving fake reviews?
By the Ingenious AI team · Published 14 November 2026 · Reviewed 14 November 2026
Run the free review audit See pricing · See a sample provenance report
Short answer
Slow down and build the file. Import your reviews and isolate the suspect cluster: dates, wording, transaction links (usually absent), fingerprint status on Pro or Agency. Check your own house in the same pass — your response loses all force if your profile carries the same patterns. Flag the cluster internally with the reasoning logged, dispute through the platform's own process with the evidence pack attached, and reply publicly, if at all, in one calm factual sentence. Never buy counter-reviews, never accuse the competitor publicly on signal evidence alone, and never name them in your record as fact — your record states patterns; attribution is the platform's or a court's job.
What is suspected competitor reviews?
Suspected competitor reviews are negative reviews a business believes were fabricated by or for a rival rather than written by customers. The belief is common and sometimes true; the operational problem is that a business can fully document the cluster (timing, wording, absent provenance, pooled-fingerprint flags) while being unable, from its own data alone, to document authorship. Effective triage therefore separates the provable (the pattern) from the attributable (the author) and pursues each through its proper channel.
The cluster first, the suspect last
Work the rows before the theory. A fabricated attack cluster usually shows a combination no honest week produces: several low-star reviews in a tight window (watch for the burst flag), similar phrasing or AI-generation patterns across supposedly unrelated writers, no transaction links for any of them, handles with no other history with you, and — on the graph — fingerprints flagged at other businesses, sometimes including your other competitors, which is the closest thing to a signature this evidence offers. Write the combination down, element by element, in the moderation record. That document is what you send the platform; 'we are sure it is the shop across the road' is what you keep out of it, because an unevidenced attribution hands the conversation a new subject: you.
Keep the negative reviews. That instruction surprises people mid-crisis, but suppression is itself a violation under the FTC rule, and a profile scrubbed clean during an attack reads as manipulation to anyone who later examines it. ReviewProof has no silent-delete path: moderation decisions are kept, published or flagged internally, each one is logged in the chain of custody, and the evidence export counts the negatives you kept. The strongest response to a suspicious review is a boring, complete record — the row, the dates, the signals, the decision, all preserved while you dispute through the platform's own process.
Your own file is part of the dispute
Before filing, run the same tests on your positives. If your profile contains an unexplained burst of UNLINKED five-star reviews from a vendor's campaign, the platform reviewing both sides will find it, and your clean-hands position collapses mid-dispute. The self-audit is not etiquette; it is reconnaissance on your own exposure. Where the audit finds your own problems, the order of operations is: stop the practice, flag the rows, log the correction, then dispute the competitor cluster with the full file — including your corrections — in the pack. Platforms and investigators both calibrate credibility by what a complainant volunteers about themselves.
After the first audit, the habit that matters is cadence. Re-import on a regular rhythm — monthly suits most locations — so new reviews enter the provenance record while the underlying transactions are still easy to match. Each import logs provenance events, moderation starts from kept (no suppression), and the certificate for any review shows its chain: imported, transaction-linked or not, analysed with its signals, moderated with its decision. A record built gradually like this is worth far more in a dispute than one assembled in a panic the week the dispute arrives.
Mistakes that undo the work
Retaliation in kind is the unforgivable error: it converts you from complainant to co-violator, and the two clusters will be indistinguishable to the next examiner. Public naming of the competitor on pattern evidence alone invites a defamation fight you may lose even if you are right. And quietly deleting or 'resolving away' your own suspicious positives before filing is evidence-tampering against yourself — flag, log, disclose in the pack.
Triage starts from your own data, not from the public profile. Import the reviews, look at which rows carry which signals, and separate three questions that are often mashed together: is this review about a real transaction, was it solicited in a way the FTC rule prohibits, and what record do we hold if anyone asks? ReviewProof answers the first two from the imported rows — transaction link present or UNLINKED, gating or incentive language present or absent — and answers the third with the provenance chain. What it will not do is declare a review fake: signals are heuristics for human review, and acting as if they were verdicts creates a new problem while solving none.
Worked example: nine one-star reviews, one weekend, no customers
A fictional worked example, written to show the numbers and the decisions in practice.
A bakery returned from a closed weekend to nine new one-star reviews. Import and cluster work showed: all nine inside 38 hours, none transaction-linked (the bakery had been shut for two of those days, a contemporaneous fact in its own records), four sharing near-identical wording about an event that had not occurred, and three fingerprints flagged at other businesses on the graph. The bakery flagged all nine internally with that combination logged, replied once publicly ('We were closed on two of those dates and cannot match these to any visit; we have shared our records with the platform'), and filed the dispute with the evidence pack. The platform removed seven and the bakery's record kept all nine — flagged, reasoned, retained — because the file's job is to show its working even after the platform acts.
Your five-action checklist
- Import and isolate the suspect cluster before forming any theory of authorship
- Record the combination: timing, wording, links, fingerprint status
- Run the identical tests on your own positive reviews in the same pass
- Flag internally with reasoning; dispute through the platform with the evidence pack
- Reply publicly once, factually, without accusation — or not at all
Frequently asked questions
Can ReviewProof prove a competitor wrote the reviews?
No — and it does not claim to. It documents the cluster's pattern (timing, wording, absent links, pooled flags). Attribution is for the platform's investigation or a legal process.
Should I reply to suspected fake reviews?
At most once, briefly and factually, without accusation. Your dispute file does the real work; a public argument only entertains spectators.
What if some of the suspect reviews might be genuine?
Then the cluster reading must say so row by row. Mixed clusters exist; flagging a genuine angry customer as fake, carelessly, is its own reputational and evidential error.
Is buying positive reviews to offset an attack ever justified?
Never. It replaces an attributable attack on you with a provable violation by you — the one trade no position can afford.
Keep reading
Related guides from the ReviewProof library:
- What should you do in the first 48 hours of a one-star attack?
- How do you clean up a profile with bought reviews in its past?
- Why are employee reviews of your own business a violation risk?
- What does it mean when one reviewer appears at many businesses?
- What should you do when a customer threatens a bad review?
- Can having too few negative reviews look suspicious?
- How do you explain a seasonal spike in your reviews?
Start with the tool itself: open the free audit desk, see how ReviewProof works, compare Free, Pro and Agency plans, inspect the sample provenance report, or browse all ReviewProof guides.