If the way you've been asking for reviews involves a staff scoreboard, a script that tells customers to "mention Sarah," or a tablet shoved across the counter before someone leaves, Google now has a name for that: a policy violation. Google tightened its review solicitation rules in 2026, closing off practices that used to sit in a gray area. Here is exactly what changed, the primary sources behind it, and a simple way to check whether your current process is still compliant.
What actually changed
Google's rating-manipulation policy, published on its own Business Profile support pages, now spells out three specific solicitation practices as violations rather than leaving them to interpretation. Google's language is direct: businesses may not have staff solicit a set number of reviews, may not have staff solicit reviews that include specific content (including content that identifies a staff member), and may not pressure or require a review while a customer is still on premises.
This sits alongside a broader enforcement push. Google's own 2025 Trust and Safety Report, published in April 2026, disclosed the scale of what its systems are now catching. Google blocked or removed 292 million policy-violating reviews in 2025 and removed over 13 million fake Business Profiles, while publishing more than a billion legitimate reviews. The solicitation rules didn't appear in a vacuum, they arrived as part of a system built to actually catch them.
The three things Google now explicitly bans
Strip out the legal phrasing and the update comes down to three specific asks that are now off-limits, each one a way businesses were quietly steering the content or volume of their reviews rather than just inviting honest feedback.
- Staff review quotas. Telling a team "we need 10 reviews this week" or tying a bonus to review counts is now a named violation, not just bad practice.
- Employee-name solicitation. Scripting staff to ask customers to mention a specific person by name in their review crosses the line, even if the visit was genuinely great.
- On-premises pressure. Asking for the review, or watching someone write it, before the customer has left your location is now explicitly prohibited.
Why Google is cracking down now
Two separate forces are pushing in the same direction, and it helps to know both are running at once. The first is Google's own detection stack. Google's April 2026 update added Gemini-powered screening for profile edits, paired with scam-detection systems that catch suspicious review patterns, like extortion attempts demanding payment to remove a fake one-star, before they publish, instead of relying only on after-the-fact reports from business owners.
The second is regulatory. The FTC's Consumer Review Rule, in force since 2024, bans fabricated reviews, undisclosed employee endorsements, and incentives tied to positive sentiment. In December 2025 the FTC sent its first warning letters under the rule to ten companies, and the maximum civil penalty per violation now sits at $53,088. The rule applies the same way to a single-location business as it does to a national chain, and each individual fake or coerced review can be treated as a separate violation.
“Two different enforcers, one message: a review has to reflect what actually happened, with nobody scripting who gets named, how many show up, or when the ask happens.”
There's a physical version of this violation that a lot of owners don't think of as "asking", the review kiosk or tablet sitting at the checkout counter. If a customer is filling it out while a staff member is standing there, or before they've paid and left, that's on-premises pressure even though nobody said a word. The same device used after the customer has walked out, say, a QR code on the receipt they take home, does not have that problem. The hardware isn't the issue. The moment is.
The 3-question self-audit
You don't need a lawyer to check your current process. Run whatever you're doing right now through three questions, and if the answer to any of them is yes, that practice needs to change.
- Are you assigning a number? A target review count for a person, a shift, or a location is a quota, regardless of how it's phrased.
- Are you assigning a name? If staff are told to get themselves, or a coworker, named in the review text, that's solicitation of specific content.
- Are you assigning a moment that's still on-site? If the ask happens before the customer has physically left, or while a staff member is standing there watching them type, that's on-premises pressure.
Answer no to all three and you're in the clear, even if you ask every single customer, every single time. Volume and consistency were never the problem. Scripting the outcome was.
Two quick examples of how this plays out. A dental office that texts every patient a review link the evening after their appointment, with no mention of who worked on them, is fine no matter how many patients they text. A restaurant that posts a whiteboard in the back reading "Team goal: 20 reviews mentioning your server this month" fails the audit twice over, once on the number and once on the name, even though the food really was good and the reviews would have been genuine.
What's still completely fine
None of this makes asking for reviews risky. The core activity, inviting customers to leave honest feedback, is still exactly what Google wants. What changed is the method, not the goal.
- Send the same review request to every customer by text or email after the visit
- Provide a direct one-tap link to your Google review page
- Thank customers for reviews after the fact, regardless of star rating
- Let an employee's name appear if the customer brings it up on their own
- Ask again, once, if a customer never got around to it the first time
- Set a review count target for staff, a shift, or a location
- Script staff to request that a specific employee gets named
- Ask for or watch a review being written while the customer is still on-site
- Offer a discount, refund, or gift in exchange for a review
- Route the request differently based on how the visit seemed to go
For the mechanics of asking well within these lines, timing, message wording, and getting your direct review link right, see our full guide on how to ask for Google reviews.
This isn't the same as review gating
It's worth separating this update from a related but different violation. Review gating is filtering customers by how happy they seemed before deciding who gets asked, sending glowing customers to Google and quiet ones to a private form. This update is about how you ask everyone, regardless of sentiment: no quotas, no scripted names, no on-premises pressure. A business can violate one, both, or neither. Our review gating explainer covers that side in full, including the FTC exposure specific to it.
If you've been doing one of the banned things
Don't panic, and don't start mass-deleting old reviews or contacting past customers about it. The fix is entirely forward-looking. Rewrite the checkout script, remove any review count from staff scorecards or bonus structures, and move the ask to after the customer has left. Reviews you already have that came from a genuine visit aren't retroactively invalid just because the process around them wasn't perfect.
The harder part for most owners was never the asking, it's staying on top of what comes back. Our Google review management workflow covers the monitoring and reply side end to end.
Once the requests are compliant, the other half of the job is answering what comes in without it eating your week. Resparo drafts replies in your own voice automatically and holds anything sensitive for a one-tap check, so a clean, rule-following ask process doesn't just sit there generating reviews nobody answers. Plans start at $29.99 a month, and you can try a single reply for free with the reply generator first.