ReviewProof ⚖

How do you clean up a profile with bought reviews in its past?

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

You do not clean a bought profile by deleting the bought rows; you clean it by stopping the supply, documenting what exists, and outbuilding it with provable reviews. Concretely: cancel every reputation vendor arrangement today; import the full file as found; identify bought clusters by their pattern (bursts, duplicate or AI wording, UNLINKED, flagged fingerprints) and flag them internally with the conclusion and its basis logged; file platform disputes for the clusters with the evidence pack; then run clean solicitation — one ask, everyone, nothing offered — so the linked profile grows over the purchased layer. The record of the cleanup, kept, is the asset.

What is a bought-review cleanup?

A bought-review cleanup is the remediation of a profile containing reviews purchased from a vendor, a freelancer or a past agency. Its governing insight is that the contamination is documentary as much as statistical: the clusters sit inside your history with dates and patterns, and any future examiner will find them whether or not you did. The cleanup therefore aims at a state you can show — supply stopped, clusters identified and flagged by you first, corrections dated — rather than at a state you can merely claim.

Confession beats cosmetics, every time

The temptation is cosmetic: prune the obvious clusters from your spreadsheet, present a cleaner file, move on. It fails arithmetically (the platform's copy, the vendor's other clients' files and the pooled graph all retain the pattern), it fails evidentially (an edited file with unexplainable gaps is worse than a dirty file with an honest log), and it fails the FTC test, because removing reviews selectively from your record is suppression being used to hide fabrication — the two violations holding hands. The alternative is genuinely available: businesses recover from this. They recover by being the party who found it, named it, stopped it and documented all three, in that order, before anyone asked.

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.

The rebuild is a volume and patience problem

After the stop and the flags, what remains is arithmetic: a profile with 80 bought rows among 200 needs its linked, clean volume to grow until the purchased layer is a documented historical episode rather than the profile's centre of gravity. That takes the time it takes — there is no compliant accelerant, and anyone selling one is selling the next cleanup. What you can accelerate is capture quality: transaction-triggered asks at full coverage, references linked at import, the widget publishing the clean layer immediately so your own site's claim is honest from week one even while platforms still show the mixed history. Internally, track the clean linked share as the recovery metric and report it like one: dated, rising, unspectacular, real.

In practice the routine takes minutes. Export or copy the reviews for the location, import them into ReviewProof by CSV or paste, and read the report top-down: total rows, flagged count, risk score, then the per-signal breakdown. Open the flagged rows themselves — the report traces each signal to its row precisely so you can do this. Decide moderation openly (kept, published, or flagged internally; there is no delete), check which reviews carry a transaction link, and publish or refresh the verified widget so the public claim matches the audited record. On Pro, export the evidence pack while the file is fresh.

Mistakes that undo the work

Deleting bought rows from your own record is the central error — suppression to conceal fabrication. Quietly letting the vendor continue 'but only a few a month' restarts contamination during your own cleanup. And announcing a 'fresh start' publicly while the clusters remain unflagged in your file inverts the credibility order: flag first, document, then, if you speak at all, speak about the system you now run.

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.

Worked example: a retailer recovers in the open

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

A gifts retailer inherited a bought layer when it purchased a competitor's shop and list: of 431 imported reviews, cluster analysis identified roughly 90 bought rows across three vendor bursts (duplicate long texts, AI phrases, zero transaction links, two fingerprints flagged across the pool). The new owner cancelled the still-running vendor contract the week of the audit (the vendor had kept 'maintaining' the profile), flagged the three clusters with the acquisition and the findings logged, disputed them with the pack — the platform removed about half — and published the widget from linked reviews only. Eighteen months of clean solicitation later, linked reviews outnumber the bought layer four to one and the recovery itself, documented end to end, is the first thing the owner shows a new wholesale partner who asks about the shop's ratings.

Your five-action checklist

  1. Cancel every review-vendor arrangement and keep the cancellation record
  2. Import the full profile as found — no pre-editing, however tempting
  3. Identify bought clusters by pattern and flag them internally with the basis logged
  4. Dispute the clusters through the platform with the evidence pack
  5. Rebuild on clean solicitation; track clean linked share as the recovery metric

Frequently asked questions

Can bought reviews be removed?

By the platform, through its dispute process, with evidence — sometimes. From your own record, never silently: they remain, flagged by you, as part of the documented history.

What if a previous owner or manager bought them?

The record should say exactly that, with dates. Inherited contamination, found and remediated by the current owner, is a defensible position — undocumented, it is just contamination.

How long does recovery take?

As long as your genuine review volume takes to outweigh the layer. There is no compliant shortcut; the monthly trend of clean linked share is the honest measure.

Should we tell customers about the cleanup?

There is rarely a reason to announce it. Run the clean system, publish the verified widget, and answer any direct question with the documented record.

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.