Can you ask customers to mention your name in a Google review?

Here's the honest answer most owners are looking for. Yes, you can ask a happy customer for a Google review. No, you should not tell them to mention a specific person by name.

The difference is who chose the words. A customer who writes "Dave was fantastic" because Dave actually helped them is leaving a real review. A customer who writes "Dave was fantastic" because your text told them to is repeating a script. Google's policy is built to tell those two things apart.

If your ask works whether or not the customer remembers a name, you're on clean ground. If your ask only works when the customer inserts the name you handed them, that's the part to fix.

Most coverage of this change blurs three separate events into one vague "April 2026 update." Here they are precisely, because the details decide what you actually have to change.

February 20, 2026: Google revised its review policy text to tighten the rule against pressuring customers to review while still on the premises. April 16, 2026: Google publicly announced new Maps enforcement, including Gemini-powered scam detection, and published its 2025 numbers, over 292 million policy-violating reviews blocked or removed and posting restrictions placed on more than 782,000 accounts. April 17, 2026: with no announcement at all, two new lines appeared in the rating-manipulation section, spotted by product expert Amy Toman.

Those two lines are the ones that matter here, and they are worth quoting verbatim. The policy now prohibits merchants requesting that staff solicit reviews that include specific content, "including content that identifies a staff member." Its sibling bullet prohibits merchants requesting that staff solicit "a certain number of reviews," which ended review quotas in the same edit.

This was a direct response to a common tactic. Service businesses had spent a decade coaching customers to drop a technician's name into the review, usually to feed internal contests or per-tech bonus programs. Google now names that practice, in writing, as rating manipulation.

From Google's side, a wave of reviews naming the same employee looks engineered, because it often is. Real customers don't coordinate. They mention what stuck with them, in their own words, at their own pace.

When fifteen reviews in a row credit "Mike Thompson" by full name, that pattern reads as a campaign, not a coincidence. Google does not publish its detection signals, but the field evidence points the same direction: a practitioner report from Wizard of Ads in May 2026 observed reviews using a technician's full first and last name being filtered as coached-review signals. Treat that as one practitioner's read of enforcement rather than stated policy, and notice that it is exactly what the policy text would predict.

One question has no answer yet, and honesty beats guessing: whether Google will retroactively remove older reviews that already name staff. No statement exists either way. The defensible move is to stop soliciting name mentions now and let the archive be what it is.

And the risk doesn't land on whatever tool or agency suggested the tactic. It lands on your Business Profile. That's the listing your next customer reads before they call.

This is the part that gets lost in the panic. Google did not ban employee names in reviews. People can still write "Sarah at the front desk made this easy" or "ask for Luis, he knew exactly what was wrong." That's a genuine, specific, helpful review, and it's completely allowed.

The rule is about the request, not the result. You can't engineer the name in. You can absolutely earn it.

So the goal isn't to scrub names out of your reviews. It's to stop putting names into your customers' mouths. Let the people who genuinely impressed someone get credited the natural way.

Owners ask this one a lot, and it's fair. Sometimes the customer really does want to thank the specific person who saved their weekend. Nothing about the policy stops them.

The line is whether you steered it. If you handed them a card that says "mention Dave for a discount," you scripted it. If Dave did great work and the customer brings up Dave on their own, that's just a good review doing what good reviews do.

The safe move is to make the person memorable through the work, not through the ask. Have your tech introduce themselves. Do the kind of job people want to talk about. Then ask for the review without dictating a single word of it.

There's a version of this that gets you specific, detailed reviews without touching scripted content. Instead of telling the customer what to write, help them remember what happened.

A good review request points them at the experience, not at a sentence. What stood out about the visit? Was the timing good? Did the work hold up? Those prompts pull real detail without putting any words in anyone's mouth. The review still belongs to the customer.

That's the whole idea behind how small Talk works. It asks the customer a few quick questions about their experience and drafts a review from their real answers. They can edit anything. One tap copies it, the next opens your Google review box, so they just paste and post. It never tells them to insert a name to satisfy a contest. The specificity comes from the customer's experience.

Here's the test to run on your own process. If you removed every instruction you give customers, would the reviews still read the same way? If yes, you're asking cleanly. If the reviews fall apart without your script, the script was the problem.

Real reviews are a little uneven. Different words, different details, different names, or no names at all. That unevenness is what makes them believable, and it's what keeps your profile out of trouble.