Review Funnel Plugins and the FTC Fake-Review Rule
For years the standard advice for collecting reviews was to ask customers how they felt first, send the happy ones to a public review page, and route the unhappy ones to a private feedback form. Plugins were built specifically to do this. It was called a review funnel, it worked, and in the United States it is now the kind of practice the Federal Trade Commission’s rule on fake and deceptive reviews targets.
The rule is not obscure and the exposure is not trivial. This article explains in plain terms what is prohibited, why gating crosses the line, what you may still legitimately do to ask for reviews, and which plugin defaults need changing.
Verified August 2026. This is general information, not legal advice, and it describes United States rules. If your business is affected, consult a qualified adviser about your specific situation.
What the rule prohibits, in plain English
The core idea is straightforward: consumers should see a representative picture of what customers actually think, not a curated one.
Fake reviews. Writing reviews of your own business, having staff or family write them, or buying them. This was already deceptive and the rule makes the consequences explicit.
Suppressing negative reviews. Using intimidation, false legal threats or unfounded takedown claims to remove criticism, and displaying a review section that has been filtered so it no longer represents the reviews you received.
Buying positive reviews with conditions attached. Offering compensation contingent on the review being favourable. Incentives for a review of any sentiment are treated differently from incentives for a good one.
Undisclosed insider reviews. Reviews written by employees, officers or their relatives without disclosing the relationship, and soliciting those reviews without telling people to disclose.
The thread running through all of it is representativeness. Anything that systematically shapes which reviews exist or which are visible, in order to present a better picture than reality, is the target.
Why gating is the problem
Review gating is the specific tactic: ask a screening question, and branch based on the answer. Satisfied customers get a link to a public review platform; dissatisfied ones get a private form that reaches you and nobody else.
It was popular because it works spectacularly. A business gating its requests accumulates an almost entirely positive public profile, not because its customers are unusually happy, but because only the happy ones were ever shown the door to the public page.
That is precisely the harm the rule addresses. The resulting public rating is not a filtered display of reviews you received; it is a filtered set of reviews that were ever allowed to exist. From a consumer’s perspective the effect is identical to deleting the negative ones, and the fact that it happens before publication rather than after does not change what the visitor is misled about.
Worth noting separately: the major review platforms have prohibited gating in their own policies for years, independently of any regulator. A business doing this has been at risk of losing its profile for some time. The rule adds a second and more serious source of exposure.
The 6 options compared
1. Site Reviews
Collects first-party reviews with no funnel logic of any kind, which makes it the least troublesome default in this comparison.
A customer submits a review, it goes into your moderation queue, you approve it. There is no branching by sentiment because there is no sentiment screening; everyone reaches the same form. That is exactly the shape a compliant flow should have. Moderation itself is not the problem: holding reviews for approval to catch spam, abuse or identifiable personal information is legitimate, and every platform does it. What matters is what you do with a genuine negative review once it arrives. Approve it, reply to it publicly, and resist the temptation to leave it unapproved indefinitely, which is where a legitimate moderation queue quietly turns into suppression.
- Sentiment gating: None
- Default flow: Compliant
- Best for: First-party collection without funnel risk
- Watch out for: Do not use moderation to bury criticism
2. Starfish Reviews
A dedicated review funnel product, which places it at the centre of this question and makes its configuration the thing to examine.
Funnel tools exist to route customers along different paths after a request, and that machinery can be configured compliantly or not depending on what drives the branching. If the branch is by sentiment, with only positive respondents shown the public review link, that is the gating pattern the rule targets. If every customer is offered the same public review options, and a separate private feedback channel is additionally available to anyone who prefers it, the flow is defensible. The distinction is whether the customer chooses their path or the software chooses it based on how they rated you. Review your existing configuration against that test specifically, because the default in many funnel setups predates the rule.
- Sentiment gating: Configurable; check yours
- Default flow: Depends entirely on setup
- Best for: Multi-platform requests, configured carefully
- Watch out for: Pre-rule configurations still in place
3. Trustindex
Primarily a display tool, which keeps it clear of most of this. $65, $125 and $349 a year, unlimited widget views.
Showing reviews that already exist on a public platform involves no collection funnel and therefore no gating. The compliance question shifts to the display itself: filtering your widget to show only five-star reviews while your public profile averages three is a misleading presentation, even though every individual review is genuine. Set the display to show a representative selection, including recent reviews regardless of rating, and link to the full profile so a visitor can see everything. Where its collection features are used, apply the same test as anywhere else. As a display tool configured honestly, it is straightforward.
- Sentiment gating: Not applicable for display
- Default flow: Compliant as a display tool
- Best for: Showing existing platform reviews
- Watch out for: Filtering the display to hide low ratings
4. Customer Reviews for WooCommerce
Automated post-purchase review requests for stores, where the compliance questions are about timing and incentives rather than routing.
Sending every customer the same request after delivery is exactly right: no screening, no branching, everybody asked. Where stores get into difficulty is with coupons offered in exchange for reviews. An incentive conditioned on leaving a favourable review is prohibited. An incentive offered to every reviewer regardless of what they write is generally acceptable, provided the incentive itself is disclosed. The wording matters more than the intention, so check the template text rather than assuming: a message reading “leave us a five-star review for 10% off” is a problem, and “leave a review, positive or negative, for 10% off” is a different proposition entirely.
- Sentiment gating: None by default
- Default flow: Compliant if incentives are unconditional
- Best for: Store review requests at scale
- Watch out for: Coupon wording tied to positive reviews
5. WP Social Ninja
An aggregator combining reviews from several platforms with social feeds and other proof elements.
Aggregation raises a specific version of the display question: when you pull reviews from four platforms and show a combined rating, that number must reflect the underlying reviews rather than a selection of them. Check whether the plugin has filters that exclude reviews below a threshold, because such settings exist in several products in this category and applying them turns an honest aggregate into a misleading one. Used to show everything from every connected platform, aggregation is genuinely useful for a business whose reviews are scattered. Used to assemble a flattering composite, it is the display-side version of gating.
- Sentiment gating: Check display filters
- Default flow: Depends on filter settings
- Best for: Businesses with reviews across platforms
- Watch out for: Minimum-rating display filters
6. Ask everybody, the same way
The approach that removes the problem rather than managing it, and which performs better than most businesses expect.
Send every customer the same request, with the same links, at the same point after the work is done. No screening question, no branching. The fear is that this floods you with criticism; in practice most businesses find that asking everyone produces a higher volume of reviews and an average close to their real quality, which is what a prospective customer wants to see anyway. A profile of exclusively perfect scores reads as implausible, and buyers have learned to discount it. Add a public reply to every negative review, which is the single most effective response available and is visible to every future reader. This is both the compliant approach and, on the evidence, the commercially better one.
- Sentiment gating: None, by construction
- Default flow: Compliant
- Best for: Every business
- Watch out for: You will receive criticism; reply to it
Comparison table
| Option | Type | Sentiment branching | Main risk | Fix |
|---|---|---|---|---|
| Site Reviews | Collection | None | Unapproved criticism | Approve and reply |
| Starfish Reviews | Funnel | Configurable | Legacy gating setup | Same links for everyone |
| Trustindex | Display | Not applicable | Filtered display | Show a representative set |
| Customer Reviews for WooCommerce | Requests | None | Conditional incentives | Reword the offer |
| WP Social Ninja | Aggregation | Via filters | Misleading aggregate | Disable rating filters |
| Ask everybody | Process | None | More criticism | Reply publicly |
What you may still do
The rule does not stop you asking for reviews or managing them sensibly. It stops you shaping which ones exist. Everything below remains available.
- Ask every customer, and ask persistently. A reminder a few days after the first request is fine. Volume is your best defence against an unrepresentative average, and there is no limit on asking.
- Choose your timing. Asking shortly after a successful delivery rather than during a support dispute is ordinary good practice, not gating, provided you apply the same timing to everyone.
- Offer a private feedback channel alongside, not instead. A contact link presented to everyone, next to the public review options, is genuinely useful. It becomes gating only when it replaces the public option for people who rated you poorly.
- Moderate for spam, abuse and personal information. Holding a review to check it is legitimate is normal. Leaving a genuine negative review permanently unapproved is not.
- Reply to criticism publicly. This is your strongest tool and it is entirely unrestricted. A measured reply to a poor review reassures future readers more than the review discourages them.
- Incentivise reviews unconditionally, with disclosure. A reward for reviewing, regardless of what the review says, is treated differently from a reward for saying something positive. Disclose the incentive.
On insider reviews, the rule is simple in principle and often ignored in practice: employees, officers and their close relatives must disclose the relationship, and you must not solicit those reviews without telling people to disclose. If you have ever asked staff to help get things started, that is worth revisiting.
Frequently asked questions
Is review gating actually illegal now?
Routing only satisfied customers to a public review page is the kind of practice the FTC rule targets in the United States, and major platforms have banned it independently for years.
Can I still moderate reviews on my site?
Yes, for spam, abuse and personal information. Approving a genuine negative review and replying to it is the correct handling; leaving it unapproved indefinitely is not.
Can I offer a discount for a review?
Only if it is offered for any review regardless of sentiment, and disclosed. Conditioning the reward on a positive review is prohibited, and wording matters more than intention.
Can I ask staff to leave reviews?
Only with clear disclosure of the relationship, and you must not solicit them without instructing people to disclose. Undisclosed insider reviews are directly covered.
Is a private feedback form allowed?
Yes, offered to everyone alongside the public options. It becomes gating when it is shown instead of the public option to people who rated you poorly.
What about businesses outside the United States?
This rule is a US one, but consumer protection law elsewhere addresses misleading reviews too, and the platforms ban gating globally. The safe approach travels well.
The verdict
If you run a review funnel that branches on sentiment, change it this week. Same request, same links, every customer. That single change removes the exposure and takes ten minutes.
For collection without funnel risk: Site Reviews, which has no sentiment branching to misconfigure, with moderation used for spam rather than for criticism.
Check your display settings too. A widget filtered to show only five-star reviews while your profile averages three is the display-side version of the same problem, and several plugins offer exactly that filter.
Then ask everybody and reply to the criticism. Businesses that do this end up with more reviews and an average close to their real quality, which is what buyers actually want to see. A wall of perfect scores reads as implausible, and prospective customers stopped believing it some time ago.
