Walk into enough home service offices and you’ll eventually find the whiteboard. Technician names down the left side, review counts across the top, a prize at the end of the month for whoever got the most customers to mention them by name. It works. Customers play along. The reviews come in. And as of April 2026, running that program is a Google policy violation.
Key Takeaways
- Soliciting reviews that name a specific employee is now explicitly banned — Google added the language to its Rating Manipulation policy on April 17, 2026.
- Review quotas are banned in the same update — directing staff to collect a set number of reviews in a given period is now a named violation.
- Your existing reviews are almost certainly fine — reviews that happen to name a technician are not being retroactively swept. The violation is the solicitation practice, not the review itself.
- Enforcement is automated and runs before publication — there is no complaint queue to wait on, and consequences escalate to profile warnings.
- Move the attribution to your side of the wall — track which employee earned which review internally, rather than asking the customer to say the name out loud.
What actually changed
Google made two moves in April, a day apart, and they get conflated constantly.
On April 16, the changes were defensive: scam detection that runs before a review publishes, Gemini-powered moderation of review edits, and proactive email alerts to business owners when something looks wrong on their profile. Those are protections. If you have ever been review-bombed by a competitor or watched a five-star review quietly get edited into a one-star months later, that update was built for you.
On April 17, Google added two explicit prohibitions to the Rating Manipulation policy. The first bans “directing staff to request reviews that include specific content, including content that names a staff member.” The second bans directing staff to solicit a specific number of reviews in a given period.
Both practices were widespread. Neither was previously spelled out in the policy. Now both are named violations, and the enforcement is not a human reading complaints — it is automated pattern detection watching review volume, shared devices, IP clustering, and content similarity, mostly before anything goes live.
The part most people are getting wrong
Read three articles about this update and you will probably come away believing that Google is now deleting any review that mentions an employee’s name. That is not what happened, and the distinction matters a great deal if you are about to panic about four years of accumulated reviews.
Reviews naming employees are not being retroactively removed. A customer who spontaneously writes “Marcus and his crew were incredible” has done nothing wrong, and neither have you. Genuine, specific, unprompted praise is exactly what Google wants on a profile.
What is now prohibited is the instruction. The tech-of-the-month board. The script that says “when you ask for the review, remind them to use your name.” The sales meeting where everyone is told to bring in eight reviews before the thirtieth. Those are the violations, because from Google’s side they are indistinguishable from rating manipulation — a business shaping review content to serve an internal incentive rather than letting customers describe their own experience.
So the honest version is narrower and more useful than the panicked one: your review history is safe, and your review program may not be.
Why companies built these programs in the first place
Nobody set up a name-dropping incentive because they wanted to manipulate Google. They did it because they had a real problem and no better tool.
The problem is attribution. Your technicians, your sales reps, and your CSRs are the ones actually building the relationships that generate referrals, reviews, and repeat business. Most companies have no way to see who is doing that work, let alone reward it. Asking the customer to say the name out loud was a workaround — a way to get credit to flow back to the right person using the only channel available.
Snoball CEO Landon Taylor has been making this argument for a while, and the April update turned it from a best practice into a requirement.
“Rewarding technicians for getting their name dropped in a review just turned into a liability. The new way is a corporate-sponsored program with a closed loop, and end-to-end attribution that ties each outcome back to the employee who generated it. No name-dropping required.”
— Landon Taylor, CEO, Snoball
What to do instead
The fix is to stop routing attribution through the customer and start handling it internally. Concretely:
Audit your ask. Pull whatever script, text template, or door-hanger your team uses to request reviews. If it contains any version of “mention me by name,” rewrite it this week. Ask for the review. Do not ask for the content.
Kill the quota, keep the habit. “Everyone brings in eight reviews this month” is now a violation. “Every completed job gets a review request” is not. The difference is that one sets a target on outcomes you do not control and the other sets a standard on behavior you do.
Give credit a path that does not run through the review. If a technician’s customer leaves a review, that should be traceable back to the technician in your own system — through the referral link they shared, the QR code on their card, or the job record. The employee still gets recognized. Google never has to see the name.
Recognize the whole chain, not just reviews. The review is one outcome. The referral, the repeat job, and the revenue attached to both are the others. A team that only gets credit for reviews will optimize for reviews, which is how you end up with a compliance problem in the first place.
This week, the highest-value thing you can do is read your own review request script out loud. If any part of it tells the customer what to say, you have a fix that takes ten minutes and removes a risk you probably did not know you had. Everything else — the attribution, the recognition, the leaderboard — can move to your side of the wall, where it belonged anyway.
For more on the mechanics of collecting reviews without steering the content, see our guides on getting more Google reviews and review request templates. If you are rebuilding employee recognition around this, our breakdown of team leaderboards and trackable QR codes covers the attribution side.
Note: This article draws on a LinkedIn post by Landon Taylor, CEO of Snoball. Policy details verified against Google’s Business Profile review policy as of August 2026. Google’s policies change; confirm current requirements before making compliance decisions.
Get the reviews without the compliance risk
Snoball runs the referral and review engine for you — real conversations with your customers, asked at the right moment, with every outcome tied back to the person on your team who earned it.
Schedule a Demo