What does the FTC fake-review rule actually ban?
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
The FTC fake-review rule (16 CFR Part 465), in force since October 2024, bans: fake or false consumer reviews including AI-generated ones; buying a particular sentiment, positive or negative; insider reviews presented without disclosure; review suppression, including gating and deleting negatives; and misrepresenting a review site or profile as independent when it is not. For a business, the practical translation is one sentence: be able to show, review by review, where yours came from and what you did with them.
What is the FTC fake-review rule?
The FTC fake-review rule is the US Federal Trade Commission's rule at 16 CFR Part 465, effective October 2024, which makes specific review practices unfair or deceptive acts under the FTC Act. It does not require a business to hold any particular software or certificate; it prohibits conduct — fabrication, bought sentiment, suppression, undisclosed insiders, false independence — and enforcement examines the business's records to establish whether that conduct happened.
The bans, translated into daily practice
Walk the list as an operator. Fabrication: anyone writing reviews for experiences that never happened, human or AI, is banned — so the subcontractor who 'handles ratings' is a liability, not a vendor. Bought sentiment: value conditioned on praise is banned, so the discount-for-five-stars card goes in the bin. Insiders: staff and relatives reviewing without disclosing the connection is banned, so the team's own glowing reviews come out of the strategy entirely. Suppression: threatening, gating or quietly removing negatives is banned, so moderation becomes a logged, defensible act. Independence: a 'review site' you control must not pose as neutral. Each ban maps to a habit, and each habit maps to a record.
The FTC fake-review rule, 16 CFR Part 465, has been in force since October 2024. It bans fake and AI-generated reviews, buying positive or negative sentiment, insider reviews without disclosure, review suppression, and misrepresenting review sites as independent. ReviewProof was built as the evidence layer for that rule: imported reviews carry a provenance chain — import, transaction link, analysis, moderation decisions — and the Pro evidence export includes the moderation log with negative reviews kept, which is how a business shows suppression did not happen. Proof, in this design, is a record anyone can inspect, not a badge a business awards itself.
Why provenance is the natural defence
Notice what an investigator asks for under every ban: the underlying record. Who wrote this, after which transaction, solicited how, moderated by whom, with what else in the file? A business running ReviewProof answers from one place: the imported rows, the signal analysis traced to those rows, the transaction links or their honest absence, the moderation log including negatives kept, and — on Pro — an evidence export that assembles it. No tool makes a business compliant; conduct does that. But when conduct is questioned, the business with the chain of custody spends the meeting showing documents while the business without one spends it explaining memories.
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
Believing the rule is only about fake positive reviews misses half of it: suppression and bought negative reviews aimed at competitors are banned with the same force. Believing a disclosure cures everything is another error — disclosure does not license buying sentiment. And believing you are too small to matter confuses enforcement odds with legality; platforms apply the same principles at every scale, instantly, through their own filters.
Enforcement and platform action both turn on records, not intentions. A business that can produce the underlying row, its source, its date, its transaction link or the honest absence of one, and every moderation decision taken about it, is in a different position from a business holding only a star average. That is why ReviewProof never silently deletes: imported reviews default to kept, moderation is limited to kept, published or flagged internally, and every decision is written into the chain of custody. The evidence pack (a Pro and Agency feature) assembles that chain so it can be handed over as one document.
Worked example: a retailer reads the rule and changes four habits
A fictional worked example, written to show the numbers and the decisions in practice.
The owner of a small electronics retailer imported 264 reviews and read her own profile against the rule. The audit showed 17 incentive rows from a gift-card promotion (bought sentiment — ended that week), 6 reviews from staff accounts written at launch (insiders — flagged internally, connections noted in the record), and a negative share of 1.5% that pointed at the old feedback-card gating (suppression risk — one identical ask replaced it). Nothing was deleted; everything was logged. Her summary to her partner fit on an index card: 'We found it ourselves, we stopped it, here is the record.' That is the rule's practical purpose — and the strongest position it leaves available.
Your five-action checklist
- Map each ban in the rule to one habit in your business, in writing
- Import your reviews and read the gating, incentive and negative-share picture
- End any incentive, gating flow or insider reviewing the audit reveals
- Set moderation to logged decisions only — kept, published, flagged internally
- Keep the evidence pack current so any question is answered with documents
Frequently asked questions
When did the FTC fake-review rule take effect?
October 2024. It sits at 16 CFR Part 465 and treats the practices it lists as unfair or deceptive acts under the FTC Act.
Does the rule ban AI-generated reviews?
It bans fake reviews, expressly including AI-generated ones that misrepresent experience. A genuine customer review is untouched; fabricated text is banned whoever or whatever wrote it.
Are incentives for reviews always banned?
Value conditioned on a review expressing a particular sentiment is banned. The safe operating rule is simple: nothing of value connected to writing, posting or praising a review.
Does ReviewProof make a business compliant?
No tool does — conduct does. ReviewProof provides the audit, the provenance record and the evidence export that let you find problems, prove corrections and answer questions with documents.
Keep reading
Related guides from the ReviewProof library:
- Why does keeping negative reviews protect your business?
- What should an evidence pack for a review dispute contain?
- What is a chain of custody for a customer review?
- What is a review provenance certificate?
- What does transaction-backed review provenance mean?
- How do you audit your own reviews, step by step?
- How should you moderate reviews without suppressing them?
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.