ReviewProof ⚖

What does it mean when one reviewer appears at many businesses?

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

It means one of two opposite things, and the surrounding evidence decides which. A genuine local reviewer — a food writer, an enthusiastic newcomer reviewing every business they try — appears at many businesses with transaction-linked, specific, varied reviews: their presence in the pooled graph adds a small 5 points precisely because presence is weak evidence. A farm handle appears with the opposite combination: flagged at other businesses (15 points), UNLINKED in your file, generic or AI-phrased wording, dates clustered with similar appearances elsewhere. Never judge the handle; judge the combination in the rows in front of you.

What is a repeat reviewer across businesses?

A repeat reviewer across businesses is a reviewer fingerprint observed in more than one merchant's imported file by the pooled graph. Because the pool shares only the salted fingerprint, counts and flag state — never identity, text or merchant data — the observation available to you is deliberately thin: this pseudonymous reviewer exists elsewhere, in this volume, with this flag state. The thinness is a privacy design, and it forces the correct discipline: the flag raises a question your own rows must answer.

The genuine traveller, in profile

Real prolific reviewers have textures farms struggle to imitate at scale: ratings that vary because experiences did; specific local detail (a named dish, a street, a staff member's first name used correctly); reviews spread across plausible dates including unfashionable ones; and transaction backing where businesses captured it. In your own file their row reads like a customer's row, because it is one. Businesses sometimes misread presence-elsewhere as suspicion and flag these rows — an error with a cost, because flagging genuine signal-bearing customers teaches your team that the graph cries wolf, and the month it matters they will ignore it.

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.

The stable handle, in profile

Farm handles are economical creatures: one account reviews a dental clinic, a car wash, a roofer and a bakery in the same week, in the same glowing register, with phrases that recur across supposedly unrelated writers because they recur across the farm's script or generator. In your file the row is UNLINKED (the farm cannot buy your transactions), and in the pool it accumulates flags as business after business reaches the same conclusion from its own rows. Your contribution to that accumulation is a duty of the system: when the combination in front of you justifies it, flag honestly, with the combination logged — you are writing the evidence that makes the next business's 15-point flag possible.

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

Publishing or implying a reviewer's cross-business activity in a public reply ('you seem to review a lot of businesses') discloses method, accuses without evidence the reader can check, and may be plain wrong about a genuine customer. Bulk-flagging every present-elsewhere row poisons your own flags' meaning in the pool. And deleting such rows from your record hides the very pattern the pool needs.

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: two handles, two opposite readings

A fictional worked example, written to show the numbers and the decisions in practice.

A home-services firm's graph check listed Handle A: present at 23 businesses, never flagged, one review of the firm — transaction-linked to a real boiler service, four stars, mentions the engineer's name and a rescheduled appointment. Judgement: a genuine local reviewer; kept, no action, noted as context. Handle B: flagged at 5 businesses, one review of the firm the same week as a small burst — UNLINKED, five stars, wording matching an AI-phrase pattern and echoing another row already flagged. Judgement: flagged internally with the full combination logged, the firm's flag joining the pool's. Same list, same afternoon, opposite outcomes — the combination, never the mere presence, drove each.

Your five-action checklist

  1. Judge repeat-reviewer rows on the full combination in your file
  2. Weight flags (15) far above mere presence (5) — presence is normal for genuine reviewers
  3. Check links, wording, rating spread and date plausibility before any decision
  4. Flag farm-pattern rows with the combination logged; contribute to the pool
  5. Never reference graph data in public replies or marketing

Frequently asked questions

How much does presence at other businesses add to risk?

5 points when merely present, 15 when flagged at another business — a deliberate threefold gap between a common, innocent pattern and a meaningful one.

Can I find out who the reviewer is or where else they reviewed?

No. The pool shares only the fingerprint, counts and flag state — never identities, texts or merchants. That boundary is permanent by design.

Should I serve or refuse a customer whose fingerprint is flagged?

The graph is a review-integrity tool, not a customer-screening tool. Judge the review row; the customer relationship is a separate matter.

Do genuine reviewers get harmed by the pool?

Only if businesses misjudge presence as suspicion. The scoring gap and the human-judgement rule exist to protect exactly them.

Keep reading

Related guides from the ReviewProof library:

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.