How to Prove a Competitor Is Behind Fake Reviews

Almost every business that gets hit with fake reviews suspects a competitor. Very few can prove it, and the gap between those two states is where removal cases are won or lost. Google does not act on suspicion. It acts on a documented conflict of interest. This guide covers the research method that gets you from one to the other.

Why does suspicion not work?

Google evaluates the claim you file, and "we think our competitor did this" contains nothing to evaluate. A conflict of interest report has to demonstrate a link between the reviewer and a business that benefits from your rating dropping. Without that link, the report reads as a business unhappy about a bad review.

The frustrating part is that businesses are usually right about who is responsible. The instinct is well founded. It is just not admissible, and filing on the instinct alone burns the report and teaches you nothing.

What should I look at first?

Look at what else the reviewer's account has reviewed. This single step resolves more cases than everything else combined, because a competitor-driven account almost always leaves a trail: glowing reviews for one business in your category, negative reviews for its rivals, clustered in one metro area.

Click the reviewer name on the review. Their public contribution history opens. Record all of it, in writing, with screenshots. You are looking for the shape of the account, not a confession.

How do I cross-reference the account?

Search the reviewer's display name alongside the competitor's business name, then check public professional profiles and social accounts. People who post attack reviews rarely build separate identities for it, so the same name often appears on a staff page, a professional profile, or a tagged photo.

Work through these in order. Search the exact display name in quotes plus the competitor name. Search the display name plus your city. Check whether the profile photo appears elsewhere. Look at whether the account has left reviews for businesses that are obviously connected to one another, such as three locations of the same small chain.

Keep this within public sources. Everything useful here is visible to anyone, and staying on public record is both sufficient and the only defensible approach. Do not create fake accounts to contact the reviewer, do not attempt to access anything private, and do not hire anyone who offers to.

How do I document timing patterns?

Build a spreadsheet listing every suspect review with its exact posting time, the reviewer name, their total review count, and their apparent account age. Coordination is a quantitative claim, and it is invisible until someone tabulates it.

What emerges is often striking. Six accounts, all created within the same month, all posting between 8:15pm and 9:00pm on a Tuesday, all reviewing your business and one competitor and nothing else. Written as a paragraph that is an accusation. Written as a table with timestamps it is a pattern, and a pattern is what the fake engagement policy is built to address.

Note account age carefully. Google does not publish creation dates, but the earliest visible review on an account is a reasonable proxy, and a cluster of accounts whose entire visible history begins the same week is meaningful.

What about my own records?

Your booking, transaction, and customer records are the evidence a competitor cannot fabricate around. If a reviewer describes a specific service on a specific date and your system shows no such appointment, that is documentary proof the review does not reflect a genuine experience.

Pull the records before you file. Search the reviewer's name, any name mentioned in the review text, and the date range described. Print or export the negative result. In regulated fields this needs care: a dental or medical practice cannot disclose patient details publicly, but it can confirm internally that no such record exists and reference that fact in a filing without exposing anyone. This is one reason dental practices and medical offices benefit from having filings handled by someone who works within those constraints routinely.

Is suspecting a competitor enough to remove a review?

No, and this is worth restating because it is the most common reason these reports fail. Google acts on documented conflicts of interest, not on assertions. A filing needs the reviewer's history, the affiliation evidence, the timing table, and the records showing no customer relationship.

Assembled together, those four elements make a strong case, and conflict of interest is one of the more reliably actioned categories once it is properly evidenced. That is the shape of the work in a Google review removal filing, and the same standard applies when the attack spreads to Yelp or when a competing employer is behind it on Glassdoor.

Should I confront the competitor?

No. Confrontation destroys the evidence trail. Accounts get deleted, reviews get edited, and public profiles get locked down within hours of a competitor realizing you are documenting them. Everything you have not already captured is gone.

It also converts a platform matter into a business dispute, and occasionally into a legal exposure of your own if the accusation turns out to be wrong. Document first. File second. If the financial harm is large enough to justify counsel, a lawyer can send a demand letter later with your evidence package already assembled, and that letter lands very differently when it arrives with documentation attached.

What if the evidence is not there?

Sometimes it genuinely is not, and knowing that early is valuable. An account with a long, varied, geographically plausible review history that left you one bad review is most likely a real customer you do not remember, and no amount of research will change that.

When the evidence does not materialize, the honest conclusion is that this is a review to respond to rather than remove. That is a better outcome than months spent filing reports that cannot succeed, and it redirects the effort toward the thing that actually moves a rating: a steady flow of genuine recent reviews.

There is a middle case worth naming as well. Sometimes the account looks purpose-built and the review is plainly false, but nothing ties it to any particular competitor. That case is still winnable, just under a different policy. Fake engagement does not require you to name who benefited, only to show that the review does not reflect a real experience, so a filing built on account history and your own records can succeed on its own terms. Businesses often abandon a viable case because they could not prove the part that was never required.

What does the finished evidence package look like?

A complete conflict of interest package has four parts: the reviewer's full contribution history, any public affiliation linking them to a competing business, a timing table covering every related review, and your own records showing no customer relationship existed. Each part is weak alone and persuasive together.

Assemble it as documents rather than description. Screenshots with visible dates, an exported spreadsheet, and a one-page summary that states which policy is breached and points to the specific evidence for each element. That is the form a filing needs to take, and it is the difference between a report that gets read and one that gets closed.