ReviewProof ⚖

What is review gating, and how do you stop doing it?

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

Review gating is soliciting reviews selectively: happy customers are sent to a public review page while unhappy customers are routed to a private form, a manager, or a phone call first. It is prohibited because the public profile then misrepresents the real spread of experiences. In ReviewProof, gating shows up as gating-language signals in your imported rows — and, just as tellingly, in a profile whose negative reviews have quietly gone missing.

What is review gating?

Review gating is the practice of pre-screening customers by sentiment before inviting a public review — for example asking 'did you love it?' and sending only the yeses to Google while the noes go to an internal inbox. The FTC fake-review rule (16 CFR Part 465) treats suppressing and misrepresenting the review picture as a violation, and gating is suppression performed at the front door, before the review is ever written.

Gating usually starts as customer service

Almost nobody sets out to gate. A manager wants unhappy customers reached quickly, so the feedback flow asks about the experience first — a reasonable service instinct. The violation appears in the routing: if the satisfied branch ends at a public review link and the dissatisfied branch ends at a private form, the public record is being filtered by design. Staff scripts carry the same risk in words: 'if you loved it, leave us a review; if anything was wrong, talk to us first' is gating in a single sentence, and variants of it are exactly what the gating-language patterns scan for.

Two design choices keep the detection honest. First, nothing is scored until you import it: there is no scraping of your public profiles and no third-party score blended in. Second, the weights reflect what the FTC fake-review rule (16 CFR Part 465) actually prohibits — how a review was solicited weighs heaviest (gating and incentive markers at 1.0 each), while wording patterns weigh less (duplicates 0.8, AI-generation patterns 0.6). A burst of same-day reviews adds a flat 15 points because timing is visible in the dates you supply. You can reproduce every number in the report from your own file, which is exactly the point.

The fix is one ask, sent to everyone

A compliant ask has three properties: it goes to all customers on the same terms, it links to the same public place regardless of sentiment, and it offers nothing for a positive outcome. Private feedback channels can still exist — service recovery is legitimate — but they must sit beside the public ask, not in front of it as a filter. After fixing the wording, audit backwards: import the reviews you already hold and read the gating count. A count above zero is not a confession to publish; it is a list of rows to understand, keep, and learn from while the new, clean ask replaces the old pattern.

ReviewProof's import is forgiving about format and strict about meaning. Column names are matched flexibly — body, review or text for the review itself; rating or stars; reviewer, author or name; a verified flag and a transaction reference when you hold them. Rows are capped per import by plan (500 on Free, 5,000 on Pro, 50,000 on Agency), which is generous for a single location's history. What the importer will not do is upgrade a review's status: a row that arrives without a transaction link is analysed fully and still labelled UNLINKED, because the label is the product.

Mistakes that undo the work

Replacing one filter with a subtler one — a star-rating widget that only reveals the public link at four stars and up — is still gating. So is asking for reviews only at the moment of obvious delight, such as at a celebration table, while never asking after routine or difficult visits. And deleting the old gated reviews makes the record worse, not better: keep them, flagged, as part of the history you have now corrected.

ReviewProof computes every signal from the rows you import, never from a reputation guess about your business. The risk score is 100 × (gating × 1.0 + incentive × 1.0 + duplicate × 0.8 + AI-signal × 0.6) ÷ (2.6 × number of reviews), plus 15 points when a burst is detected, capped at 100. Each flagged review in the report names the imported row that triggered the signal, so a human can open that row, read it in context, and decide. The product labels these patterns signals for human review, not verdicts — and that restraint is deliberate, because a heuristic that overclaims would be its own kind of false evidence.

Worked example: a salon chain that rewired one sentence

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

A two-location salon group imported 168 reviews and found 11 rows carrying gating language, all quoting, in near-identical words, the sentence on its old feedback card. Its imported profile also held only 3 reviews of two stars or fewer out of 168 — a shape consistent with unhappy customers being routed away. The group replaced the card with a single ask sent to every client, kept all 168 rows in the audit (the flagged 11 flagged internally, with the decision logged), and re-imported monthly. Six months later the negative share had risen to a believable level — and the rating the widget displayed was one it could prove.

Your five-action checklist

  1. Read every review-request script, card and email your team uses, word for word
  2. Remove any branch that routes by sentiment before the public ask
  3. Send one identical public ask to every customer, with nothing offered for positivity
  4. Import your existing reviews and read the gating-language count
  5. Re-audit monthly until the gating count stays at zero on new imports

Frequently asked questions

Is asking happy customers for reviews gating?

Asking is fine; filtering is the problem. If the invitation, timing or channel differs by how happy the customer seems, the public profile is being gated.

Can we still offer a private feedback form?

Yes — beside the public ask, not in front of it. Every customer must be able to reach the public review route on the same terms.

How does ReviewProof detect gating?

Patterns in the review text itself — phrases about leaving a good review, showing the review first, or contacting the business before posting — are counted as gating-language signals on the imported rows.

What if past reviews were gated before we knew?

Keep them, flag them internally, fix the ask, and let the record show the correction. Deleting the evidence is the one response that makes it worse.

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.