No. According to several write-ups of Google's April 2026 policy change, a business should not ask customers to mention a specific employee in a Google review, and should not set staff review quotas. A customer who names someone unprompted is fine. The business asking for the name is the problem.
One caveat up front: every source we could reach is a third-party marketing blog, not Google's own help page. Read the current Google Maps user-generated content policy yourself before you rewrite your process around any summary, including this one.
What the change reportedly says
Trade coverage describes two new lines in the "rating manipulation" section of Google's Maps policy, first spotted in mid-April 2026. As reported, the rule bars merchants from having staff solicit reviews that include specific content, including content that identifies a staff member, and bars review quotas for employees. A second write-up frames the same shift as advice to avoid naming employees in reviews.
The reasoning is not hard to guess. A review that reads "ask for Priya, she's wonderful" looks coordinated, and Google's whole approach to review integrity is spotting coordination.
What is still fine
Sources agree on a few points:
- Open-ended requests. Asking customers to share honest feedback in their own words is still acceptable.
- Unprompted mentions. If a customer writes that Marcus fixed their brake problem in twenty minutes, that is their review, and it stays.
- Thanking your team. Replying publicly to a review that names someone, or praising staff internally, is not solicitation.
What's less clear is staff bonuses. One write-up says the guidelines don't expressly forbid rewarding review counts, while others advise caution, especially with anything tied to name mentions. Treat that as unsettled, and keep any reward away from the wording of reviews.
What to change in your ask
Audit the scripts, cards and texts your team uses today. Look for anything that tells the customer what to write.
- Cut the name prompt. "If I helped you today, mention me" is exactly the line to retire. So is a printed card reading "Tell them who served you."
- Drop the quota. "Everyone needs five reviews this week" turns an ask into a target. Track reviews as a team signal, not a personal number staff must hit.
- Use the same ask for everyone. A general request, identical for every customer, keeps you clear of the older rule on review gating too.
- Keep it free of rewards for the review itself. Incentives for reviews have been prohibited for years; our post on offering incentives covers where that line sits.
Our guide to training staff to ask for reviews works from a script that stays on the right side of all four.
Crediting staff without asking customers to write anything
Teams still want to know who earned the praise, and a business is allowed to know. The cleaner way is to capture it before the review exists, not inside it.
If each person has their own QR code, the scan itself tells you who served the customer. The customer never types a name, never gets told to, and the review text is entirely theirs. The attribution lives in your records, not in the public review. That is how Starboard's staff leaderboard works: the rating is tied to the code that was scanned, so you can see which team member's customers rated them highly without influencing a word of what gets posted. We wrote more about the idea in every rating carries a name.
Whether any given setup passes Google's review is Google's call, and policy wording can shift again. The safe habit is simple: the customer decides what to write, and you decide only what you measure.
A quick audit you can do today
Pull your last month of review requests, whether that's a counter script, a receipt line or an email template. Highlight any sentence that names a person, asks for specific wording, or mentions how many reviews someone must collect. Rewrite those lines to a plain, open request, then retrain the team on the new version in a five-minute huddle.
The bigger shift is mental. For years the standard advice was to coach customers toward reviews that sound specific and personal. Under this rule, specificity is something that happens to a review, not something you engineer into it. Your job moves upstream: be easy to find, ask everyone the same way, and let people say what they actually think.