How to Ask Customers for Reviews Without Breaking FTC or Google's Rules

Asking every customer for a review is legal and, done right, is the single best defense against a fake-review problem later. What's no longer allowed, under the FTC's Consumer Review Rule and Google's 2026 Rating Manipulation Policy, is choosing which customers get asked, or tying the ask to an incentive that depends on what they write. The line isn't "can you ask": it's whether you asked everyone the same way.

#What does the FTC's Consumer Review Rule ban?

Two things relevant to review requests: incentives conditioned on sentiment, and solicitation that's filtered by predicted sentiment. A business can offer a small thank-you for leaving any review; it cannot offer that thank-you only if the review is positive, and it cannot survey customers first and only invite the happy ones to post publicly.

The rule, finalized in August 2024 and in force since October 21, 2024, doesn't ban asking for reviews at all. Plenty of businesses read early coverage of it that way and stopped requesting reviews entirely, which cost them legitimate volume for no legal reason. What it bans is the review being manufactured or its sentiment pre-selected. A uniform request sent to a full customer list, with no reward attached to the outcome, was never the target.

#What did Google's 2026 policy change add?

Google's Rating Manipulation Policy, updated April 17, 2026, closed a gap the FTC rule didn't reach: what businesses ask their own staff to do. Two new prohibitions apply specifically to employees. A business can't assign staff a quota of reviews to bring in, and can't direct staff to request reviews that name them individually ("ask them to mention Maria at the front desk"). Both practices showed up often enough in review patterns that Google made them explicit violations rather than leaving them to fall under "spam" generally.

That second rule matters because it's exactly the pattern our own scoring model flags as a review drive: a spike of reviews, from otherwise real customers, that mention staff by name or repeat near-identical phrasing because a script or quota is behind them. As of September 2026, 15 of the 595 places in our dataset with a completed analysis, about 1 in 40, carry that verdict. It's a smaller share than outright fake reviews, but it's the pattern most directly caused by well-meaning review-request programs that went too far.

Neither rule cares how the request was delivered. Email, a printed receipt QR code, a text message, a tablet at checkout: the medium is irrelevant. What both rules look at is whether the population of customers asked, and any reward attached to asking, depended on predicted or actual sentiment.

#The compliant playbook

None of this requires giving up on review requests. It requires making the ask blind to the answer:

• Send the request to every customer from the same trigger event (checkout, appointment completion, order delivery), never a subset chosen after the fact.
• Never precede the request with a private satisfaction filter that decides who gets the public review link.
• If you offer a thank-you (a discount code, a raffle entry), make it available for leaving a review at all, not for a positive one.
• Keep any staff review-request effort to "ask the customer to leave honest feedback" — no quotas, no scripts asking for a named mention.
• Space requests out with your normal transaction volume. A request email that goes to 200 people on the same afternoon, all mentioning the same employee, reads to a platform, and to us, exactly like a review drive.

#Does timing or platform change any of this?

Yes, in one direction: the rules above are a floor, and individual platforms can be stricter. Google's own terms discourage incentivizing reviews at all, even with a reward available to everyone regardless of sentiment, so a business collecting Google reviews specifically should treat any reward as a risk rather than lean on the "not conditioned" exception. Timing matters less for legality and more for how genuine the resulting reviews look: a request sent within a day or two of the transaction, while the experience is fresh, produces more specific, more varied reviews than a delayed or batched send, and specific, varied reviews are exactly what doesn't get flagged by a burst or duplicate-text check.

Google is stricter than the FTC on incentives specifically: even a reward that isn't conditioned on sentiment can trip Google's own rules against incentivized reviews on its platform, while the FTC rule focuses on the conditioning. When the two disagree, follow the stricter one for that platform.

#A request template that stays inside both rules

"Thanks for visiting us. If you have a minute, we'd appreciate an honest review, good, bad, or in between. [Link]. It helps other customers and helps us fix what isn't working."

That's the whole template. It doesn't ask for five stars, doesn't name an employee, doesn't attach a reward, and goes to everyone who completes the same trigger event. Anything more elaborate than that is usually where the rule gets bent, not where the review gets better.

For a business trying to fix an existing pattern rather than build a new one, our guide to review gating covers what a compliant wind-down looks like, and the review-drive signal explainer walks through exactly how the pattern above gets flagged when staff-named requests get sent in a batch. If you want to check where your own listing stands before changing anything, run it through our free analyzer, which reads the same signals a platform would.

#Frequently asked questions

#Is it illegal to ask customers to leave a review?

No. Asking every customer, without conditioning the request on what they'll say, is legal under the FTC's Consumer Review Rule and allowed by Google. What's restricted is selecting who gets asked or rewarding only positive outcomes.

#Can I offer a discount in exchange for a review?

Only if the discount applies regardless of the review's content or rating. Offering it exclusively for a positive review is a banned "conditioned incentive" under the FTC rule, and Google separately discourages incentivized reviews on its own platform.

#Can I ask my staff to request reviews from customers?

Yes, but Google's April 2026 policy bans giving staff a review quota or asking them to request reviews that name them personally. A general "please leave us honest feedback" ask from staff is fine; a scripted, self-naming request is not.

#What's the difference between review gating and a normal request process?

Review gating pre-filters who gets asked based on predicted sentiment, usually through a private survey. A normal process asks everyone from the same trigger point, with no filter standing between the customer and the public review link.

#Will asking for reviews get my Google Business Profile flagged?

Not if the request goes to every customer without incentive conditioning or staff quotas. What gets flagged is the pattern that results from cutting corners on this: bursts of reviews, all mentioning the same employee, arriving in a short window.