CallRadius
Compliance

The FTC Fake-Review Rule and LSAs: Compliant Review Generation in 2026

April 13, 2026 · CallRadius LSA Institute · 6 min read

For a long time, a common piece of "review strategy" advice was to filter before you ask — survey customers first, then only invite the happy ones to leave a public review and quietly steer the unhappy ones elsewhere. It boosted average ratings, and it felt clever. As of the FTC's fake-review rule, it is also a genuine legal risk. For Local Services Ads (LSA) advertisers — whose reviews now flow through Google Business Profile and directly influence performance — understanding this rule is not optional.

This is a plain-language look at what changed, why the old "review-gating" playbook is now dangerous, and how to build a review process that is both compliant and, as it happens, better for your business.

A note: this article is general information, not legal advice. For your specific situation, consult a qualified attorney.

What the rule targets

The FTC's rule on fake and deceptive reviews (16 CFR Part 465, effective October 2024) takes aim at practices that distort the honest picture a review section is supposed to give consumers. It addresses things like fabricated reviews, reviews from people with undisclosed material connections to the business, and other forms of review manipulation. The animating idea is straightforward: reviews should reflect genuine customer experience, not a curated highlight reel engineered to mislead.

Why review-gating is the problem

"Review-gating" is the practice of soliciting reviews selectively based on how you expect the customer to feel — asking for a public review only from customers you believe are happy, while diverting dissatisfied ones to a private channel. The result is a review profile that systematically overstates satisfaction, because the negative experiences were filtered out of public view by design.

That is precisely the kind of distortion the FTC's approach frowns on. When you cherry-pick who gets to review you in order to inflate your rating, you are shaping the public record to be more flattering than reality — and that manipulation, not the individual reviews themselves, is where the exposure lies. The compliant standard is the opposite of gating: ask all your customers for reviews, and let the honest distribution speak.

The double bind for LSA advertisers

This is especially pointed for LSA businesses, because reviews are not just reputation — they are performance. Review velocity is widely understood to be a ranking and performance factor, and since around July 2025 all LSA reviews are managed through Google Business Profile. So advertisers feel real pressure to keep ratings high and reviews flowing. The temptation to gate is strong precisely because the stakes are high. But giving in to that temptation now carries regulatory risk on top of the platform-integrity risk of getting caught manipulating reviews.

The compliant playbook: ask everyone

The good news is that the compliant approach is also the more durable one. A review process built to ask every customer — not just the ones you predict will rave — produces a profile that is trustworthy, defensible, and resilient. Here is what that looks like in practice.

Risky (gating)Compliant (ask all)
Survey first, invite only the happyInvite every completed customer to review
Divert unhappy customers away from public reviewAddress concerns directly, but never block the review path
Curate the public recordLet the genuine distribution stand

Why compliant is also better

It is easy to read all this as a constraint. It is closer to a gift. A review profile built by asking everyone is more believable — consumers are skeptical of a wall of flawless five stars, and a realistic mix with thoughtful responses often converts better than suspicious perfection. It is also more sustainable: you are not one audit or one platform sweep away from having your reputation strategy collapse. And it produces honest signal about your actual service, which is information you can use to get better.

The takeaway

The era of quietly curating your review profile is ending, pushed out by both regulation and platform integrity. For LSA advertisers, that raises the stakes on getting review generation right — because reviews drive performance and now live inside Google Business Profile. The winning move is not a clever workaround. It is a disciplined, universal review process: ask every customer, make it effortless, respond to everyone, and let an honest reputation compound. It is compliant, it is durable, and it earns more trust than gaming the system ever did.

Frequently asked questions

How do I generate LSA reviews without breaking the FTC rule?

Ask every customer who completes a job for an honest review through the same Google Business Profile link, make it easy, and respond to what comes in. The FTC's fake-review rule (16 CFR Part 465, effective October 2024) targets manipulation such as gating, not the honest, universal ask.

Does the FTC fake-review rule apply to Local Services Ads advertisers?

The rule applies broadly to businesses soliciting reviews. It is especially relevant to LSA advertisers because review velocity is a performance factor and, since around July 2025, LSA reviews are managed through Google Business Profile, so the pressure to inflate ratings is high.

Is a perfect five-star rating better for winning leads?

Not necessarily. A realistic mix with thoughtful responses is often more believable to consumers than a wall of flawless five stars, and it is more durable because it is not built on practices that could collapse under an audit. This is general information, not legal advice.

How CallRadius helps. CallRadius runs a compliant review engine that invites every customer to review and drafts timely replies through Google Business Profile — building honest velocity without the gating that now carries real risk. See it live at callradius.io.
CallRadius — autonomous AI for Google Local Services Ads · Total AI Marketing LLC, Scottsdale, AZ · Patent-pending closed-loop optimization (U.S. Provisional 64/063,539).