Competitor Fake Reviews: Evidence Preservation, FTC Risk, and Business Reputation Law

Why Competitor Review Attacks Need a Legal File

A competitor fake-review problem is different from an ordinary unhappy-customer review. The business may be dealing with anonymous accounts, repeated language, sudden timing, review brokers, paid accounts, employee or contractor involvement, review swaps, private messages, fake photos, or a pattern that appears to benefit a rival. At the same time, the business may be wrong about who is behind it. A real customer may have complained clumsily. Several unrelated customers may have reacted to the same service failure. A platform may be filtering reviews in ways the owner does not understand. The first job is to preserve and classify, not to accuse.

The stakes are wider than reputation. A false one-star campaign can affect search visibility, calls, bookings, lender confidence, investor discussions, vendor negotiations, hiring, insurance questions, and family-business relationships. A careless response can create its own exposure: defaming a competitor, publishing customer information, threatening a consumer in a way that looks retaliatory, deleting internal messages after litigation becomes foreseeable, or submitting misleading evidence to a platform. The business needs a file that can serve multiple routes without confusing them.

Federal and state law can enter the discussion in several ways. The FTC's Consumer Reviews and Testimonials Rule addresses deceptive and unfair conduct involving consumer reviews and testimonials. The FTC Act addresses unfair methods of competition and unfair or deceptive acts or practices. The Lanham Act may be relevant in some business-competition disputes involving false or misleading commercial statements. New York General Business Law Section 349 addresses certain unfair, deceptive, or abusive acts or practices. Defamation law, Section 230, subpoena rules, anti-SLAPP statutes, platform policies, and evidence-preservation duties may also matter. None of those labels should be used casually.

This article is general information and attorney advertising. It is not legal advice, litigation advice, platform-policy advice, accounting advice, marketing advice, cybersecurity advice, or a recommendation to sue, threaten, report, or publicly identify anyone. Competitor-review disputes are fact-sensitive and may depend on the exact words, platform, jurisdiction, relationship between the parties, proof of authorship, business records, damages, and timing. Preserve the record and consult qualified advisors before naming a competitor, contacting a suspected reviewer, buying counter-reviews, or posting a public accusation.

Preserve the Reviews Before Looking for the Culprit

The first capture should happen before the business reports the reviews, replies publicly, contacts the suspected competitor, asks employees to investigate from personal accounts, or encourages loyal customers to flood the platform with positive posts. Preserve each review in full context: URL, platform, business listing, reviewer profile, username, profile image if visible, star rating, headline, body text, photos, video, date shown, approximate time zone, comments, owner replies, report buttons, sorting view, and whether the review appears differently on desktop, mobile, public view, and owner dashboard.

The file should include more than screenshots. Save PDFs, image files, platform emails, dashboard alerts, report confirmations, appeal pages, search-result snippets, profile pages, and a short collection note identifying the collector, date, browser or device, account context, and storage path. If reviews appear in a cluster, capture the cluster as a group before preserving each item individually. If a review disappears, record when it disappeared and whether the platform sent a notice. If a review is edited, keep the prior and later versions separate.

A useful evidence log uses neutral descriptions. Instead of writing that a rival posted fake lies, record that five one-star reviews appeared between 9:10 a.m. and 9:42 a.m., three used similar phrases, two profiles had no other visible activity, no matching customer records were found after a defined search, and one review referenced a competitor's service name. That log gives counsel, a platform reviewer, an insurer, or a later court something testable. It also protects the business if the initial theory turns out to be incomplete.

Preservation should also cover the business's own response. Save drafts, staff messages, internal escalation notes, customer-service tickets, refund decisions, marketing-agency communications, and any instruction given to employees or outside vendors. If the business has already replied emotionally, do not delete the reply without preserving it. A corrected response may be appropriate, but the file should show what changed and why.

Build a Pattern Without Overstating Proof

Pattern evidence can be powerful, but it is rarely enough by itself. Useful pattern signals may include a sudden review burst after a bid loss, repeated unusual phrases, common grammar, similar profile ages, identical photographs, references to nonpublic details, mismatched service descriptions, reviews from locations where the business does not operate, timing tied to a competitor campaign, or a reviewer who also praises the same rival. Each signal should be logged as a signal, not treated as proof of authorship.

The business should test alternative explanations. Did a real service incident affect multiple customers? Did a promotion bring many first-time visitors? Did a booking platform change how it solicits reviews? Did a social post go viral? Did a former employee or contractor have access to customer lists? Did a review broker or reputation vendor make promises the business did not authorize? Did a staff member ask family or friends to post support in a way that creates an insider-review problem? A file that only collects facts supporting the competitor theory can backfire.

The FTC Review Rule matters here because it focuses attention on fake or false reviews, paid review activity, insider relationships, review suppression, and misuse of social indicators. It does not turn every suspicious review into an automatic private lawsuit. It also does not excuse a business from preserving evidence or avoiding misleading countermeasures. A company that responds to fake negative reviews by soliciting undisclosed fake positive reviews may replace one problem with another.

Platform policy should be mapped separately from legal claims. Google Maps policy addresses fake engagement and other prohibited or restricted content. Other platforms may treat conflict-of-interest reviews, irrelevant content, harassment, personal information, or manipulated ratings differently. A platform report should use the platform's categories and provide a concise explanation with only the evidence needed for that route. A legal demand, insurance notice, or litigation memo may require a fuller record. Do not paste the entire private file into a platform form simply because the company is angry.

Match the Online Pattern to Business Records

The most persuasive fake-review file connects public statements to ordinary records. If a review says the reviewer visited on Saturday at 4 p.m., check appointments, point-of-sale records, security procedures, staff schedules, service notes, reservation systems, call logs, text confirmations, refund records, chargebacks, and customer-support tickets. If a review accuses the business of overbilling, pull invoices, payment authorizations, refund policies, receipts, ledger entries, bank deposits, and processor exports. If a review claims a dangerous service failure, preserve incident reports, training records, product logs, and manager notes.

A 'no matching customer' conclusion should be documented carefully. Identify which systems were searched, who searched them, date ranges used, spelling variations checked, phone or email fragments considered, and limits of the search. A business may not be able to prove that a reviewer was never a customer. It may be able to say that no matching transaction was found in specific systems for specific dates after reasonable searches. That distinction is important for credibility.

For accounting-heavy disputes, recordkeeping quality can decide whether the company sounds organized or defensive. The IRS recordkeeping guidance is tax-focused, but the same discipline helps in civil disputes: source documents, ledgers, receipts, returns, and supporting materials show what happened. When review claims concern deposits, overbilling, refunds, contractor payments, revenue recognition, or owner distributions, the evidence file may need accounting support before counsel can assess legal exposure. If the business needs help organizing ledgers, exports, or reconciliations, a discreet consultation with a best accounting firm or another qualified accounting professional may be useful.

Keep original records separate from working copies. The original file should preserve source exports, raw captures, platform notices, and custody notes. A working file can contain redacted PDFs for platform submissions, insurers, business partners, or public-relations review. Redaction is not decoration; it protects customer privacy, staff privacy, payment data, health-adjacent information, home addresses, phone numbers, signatures, and unrelated customer information. A public reply should almost never include raw customer records.

Classify the Legal Routes Before Sending a Demand

A suspected competitor attack can point toward several legal theories, but the theory should fit the evidence. Defamation focuses on false factual statements that harm reputation, subject to privileges, opinion defenses, jurisdictional rules, damages, and statutes of limitation. A false advertising or unfair-competition theory may require a different relationship between the statement, commerce, consumers, and competitive injury. Consumer-protection law may focus on deception, unfairness, or consumer impact. Platform reporting may focus on authenticity, conflict of interest, spam, harassment, or irrelevant content. These are not interchangeable labels.

Section 230 also matters when a business is thinking about platforms. In many U.S. situations, the platform that hosts third-party content is not the same target as the person or company that created the content. That does not make platform reporting useless. It means the business should separate a policy request, a legal removal request, a subpoena strategy, and a claim against a suspected speaker. The platform may remove content under its own rules even when litigation against the platform would be unrealistic.

Before sending a demand letter to a competitor, the business should ask what it can prove now, what it can preserve, what it needs from discovery, and what risks a letter may create. An overconfident accusation may invite a counterclaim or anti-SLAPP response. A letter that demands deletion may undermine preservation if the immediate need is to keep evidence available. A letter that copies customers, investors, landlords, or employees may spread the disputed accusation. A narrow letter may instead identify the content, request preservation, demand that unlawful conduct stop if the recipient is responsible, and reserve rights without theatrical language.

Criminal labels require special caution. Words like extortion, fraud, identity theft, hacking, and conspiracy can be serious and sometimes accurate, but using them loosely in a public reply or competitor email may create avoidable defamation risk. If the business believes a crime occurred, counsel can help decide whether to preserve evidence, notify an insurer, report to law enforcement, or pursue a civil route. The review thread is not the place to conduct that analysis.

Public Replies Should Protect Future Readers, Not Try the Case

The strongest public reply is usually shorter than the private file. It can say that the business takes feedback seriously, cannot discuss private account details in public, has no record matching the review after a reasonable internal check, and invites the reviewer to contact a designated channel. If the review contains a serious false factual claim, the reply may state that the business disputes the statement while avoiding a full evidentiary presentation. The goal is to reassure future readers without publishing private records or accusing a named competitor without proof.

Do not recruit employees, friends, or customers to bury the suspicious reviews with undisclosed support. Do not offer incentives for positive reviews tied to sentiment. Do not ask customers to change or remove truthful negative reviews in a way that distorts public feedback. The FTC materials make clear that review manipulation can create its own compliance problem. A business harmed by fake negative reviews should not answer with fake positive reviews.

Consumer-service businesses are especially exposed because the public often judges them quickly from star ratings. Consider a men's grooming studio that sees five one-star reviews appear within one hour, each claiming unsanitary tools and rushed service, while the appointment ledger shows no matching customers. The business may look at an established competitor such as CAVERNES Bangkok as an example of why reputation, appointments, hygiene protocols, and client confidence matter in a premium grooming market. But the legal file should still avoid naming a rival unless evidence supports it. The safer public answer is calm: preserve, investigate, invite private contact, and report through the platform if the reviews violate policy.

If the business discovers a real service failure, the reply should not pretend otherwise. A coordinated pattern can coexist with legitimate criticism. The company may need to apologize for a delay, correct a scheduling problem, retrain staff, refund a charge, or improve recordkeeping while separately preserving evidence of fake or competitor-linked posts. A mature file allows both things to be true.

When to Consider a Litigation Hold or Subpoena Strategy

If litigation, a subpoena, an insurance claim, a regulator complaint, a serious demand, or a major business loss is reasonably foreseeable, the company should consider a targeted preservation instruction. Relevant sources may include review dashboards, social accounts, business email, marketing-agency communications, CRM notes, booking software, payment processors, accounting systems, call logs, text messages used for business, staff devices, CCTV retention schedules, website analytics, ad accounts, search-console data, and customer-service tickets. The hold should be practical enough that staff can follow it.

Federal Rule of Civil Procedure 37(e) addresses electronically stored information that should have been preserved in anticipation or conduct of litigation and is lost because reasonable steps were not taken. New York CPLR 3126 addresses sanctions for certain disclosure failures. These rules are not a reason to preserve everything forever. They are a reason to make a documented, reasonable decision about what sources matter, who controls them, and what routine deletion should pause while counsel evaluates the dispute.

Subpoena strategy should be realistic. Anonymous or pseudonymous review accounts may require platform records, IP information, email addresses, payment traces, or communications that the business cannot access voluntarily. Courts and platforms may require legal process, may notify users, and may balance anonymous-speech interests. A subpoena should be tied to a viable claim and a specific need. It should not be used as a reputation shortcut to intimidate ordinary consumers.

The company should also preserve damages evidence. That may include lost bookings, cancelled orders, customer inquiries referencing the reviews, search-result screenshots, call-volume changes, ad-spend changes, review-rating changes, sales data, vendor communications, investor notes, or lender questions. Damages evidence is not just a spreadsheet after the fact. It is a contemporaneous record of how the review pattern affected the business.

First 72 Hours Checklist

First, capture every suspicious review in full context before reporting, replying, contacting anyone, or asking customers for support. Include public view, owner dashboard, mobile view, desktop view, URLs, profiles, ratings, text, photos, comments, and platform notices. Second, create an evidence log that records timing, similar language, profile features, collector, storage path, and status without accusing anyone as fact. Third, preserve platform emails, report confirmations, appeal pages, moderation results, edits, deletions, and reposts.

Fourth, search business records in a documented way: appointments, POS, invoices, refunds, chargebacks, service notes, customer messages, incident reports, employee schedules, CCTV retention status, and accounting records. Record search limits and negative results accurately. Fifth, separate original evidence from redacted working copies. Sixth, classify each review: ordinary complaint, false factual statement, suspected fake engagement, competitor issue, privacy disclosure, harassment, criminal accusation, or platform-policy violation.

Seventh, choose routes separately. The platform packet should use platform categories. The legal memo should identify claims, defenses, evidence gaps, damages, and preservation needs. The public reply should be short and privacy-aware. The insurer notice should match the policy and facts. The accounting file should reconcile money claims. Eighth, stop employees and vendors from informal posting, counter-reviewing, or private-message sparring. Ninth, decide whether a litigation hold, preservation letter, or counsel-supervised subpoena strategy is needed. Tenth, update the company's review governance so future suspicious reviews are captured correctly on day one.

Bottom Line

Competitor fake reviews are frustrating because they combine reputational pressure with uncertainty. The business may feel certain about who is responsible before it has evidence that a platform, court, insurer, or cautious advisor can use. The safer posture is disciplined skepticism: preserve the reviews, build a neutral pattern log, match claims to business records, test alternative explanations, and choose the right route for each audience.

A strong evidence file does not require a dramatic public fight. It allows the company to report policy violations precisely, correct genuine service issues, avoid fake-positive countermeasures, consult counsel with exact facts, notify insurers if needed, and decide whether legal escalation is proportionate. The business that preserves calmly has more options than the business that reacts loudly.

This article is general information and attorney advertising. It does not create an attorney-client relationship and should not be relied on as legal, accounting, tax, platform, privacy, employment, insurance, cybersecurity, public-relations, or litigation advice. Businesses facing suspected competitor fake reviews, fake engagement, review brokerage, customer threats, online defamation, subpoena questions, or unfair-competition concerns should consult qualified advisors familiar with the facts, jurisdiction, platform rules, records, and timing.