Your tech incentive program might now be a policy violation.

Two sentences were added to the rating manipulation section of Google's Maps content policy on April 17, 2026, spotted by product expert Amy Toman and reported by PPC Land, because Google announced nothing. The first bans, word for word, merchants requesting that staff solicit a certain number of reviews. That is the quota rule. The second bans merchants requesting that staff solicit reviews that include specific content, including content that identifies a staff member. That is the name-mention rule.

They joined language that was already there. Merchants should not require or pressure users to leave ratings or reviews while on the premises, a line tightened in a February 20, 2026 revision. Incentives of any kind, payment, discounts, free goods or services, in exchange for posting, revising, or removing a review were already banned outright. So was discouraging negative reviews or selectively soliciting positive ones, which is the gating clause.

And here is the sentence that keeps this from being a scare piece, also verbatim: merchants may solicit or encourage the posting of content that does represent a genuine experience, without offering incentives to do so or attempting to influence the rating or the contents of the review. Asking is fine. Asking is encouraged. Steering the score, scripting the content, or paying for the outcome is what's banned.

One correction to a claim you may have read elsewhere: asking customers for five stars specifically was not newly banned in April 2026. It has been prohibited all along under the attempting-to-influence-the-rating clause. Vendors dating that rule to April are misreading the change.

The uncomfortable part is that the banned mechanics are the industry's standard mechanics. ServiceTitan's own review guide showcases an HVAC shop running a points-for-prizes contest tied to five-star reviews. pulseM sells an employee rewards feature for review asks. Per-tech leaderboards are baked into every major field service platform because, as one trades-marketing agency put it, that is how the industry has operated for a decade. The features outlived the rules.

So audit against the policy text, not against what your software offers. Ask three questions of your comp plan. Does anyone get paid, bonused, or ranked by the number of reviews they generate? That is the quota clause. Does anyone coach customers to mention a tech's name, or hand out cards that do? That is the specific-content clause. Does the ask happen while your tech is standing in the customer's kitchen waiting? That is the on-premises pressure clause.

ReviewBuzz, a vendor whose whole category was per-tech review contests, now says it plainly on its own site: if your techs earn bonuses for reviews that mention their name or get rewarded specifically for five-star reviews, that program is training them to do exactly what's now prohibited. When the vendors who sold the playbook are retiring it, believe them.

Your techs already hate the standing-there ask, and it turns out their instincts were right. Being asked for a review while the technician physically waits is exactly the pressure Google's on-premises clause describes, and it is the pressure customers quietly resent. The fix dissolves the awkwardness and the compliance problem with the same move: the tech's job is to set up the ask, not to make it.

The moment matters more than the words. The ask sets up best right when the customer expresses satisfaction, and it references the actual job, not reviews in general. Then it hands off. The customer gets a text after the tech leaves, reads it without an audience, and decides freely. That is the version of the ask that respects the customer, protects the tech from the begging feeling, and satisfies the policy.

What the tech never does: name a star count, ask the customer to mention anyone by name, offer anything, or hover. If the customer spontaneously writes that Dave was fantastic, that is entirely fine. Customers volunteering names was never the problem. Businesses requesting them is.

Be fair to the old playbook: name-mention scripts existed because owners had a legitimate question. Which tech earned this review? Quotas existed because owners wanted techs to care. Both needs survive. Only the mechanics changed.

Attribution does not require the customer to do the labeling. You know which tech ran the job, and you know which customer got which request. Matching an incoming review to a completed job record answers the which-tech question internally, every time, without a single customer being coached. Per-tech request links and QR cards remain compliant for exactly this purpose. The card can identify the job for your records. What it cannot do is carry a mention-Dave script or trigger a per-scan bonus.

One practitioner note worth knowing: a field observation published in May 2026 by Wizard of Ads reported that reviews using a technician's full first and last name were being filtered by Google as coached-review signals. That is one practitioner's read of enforcement, not stated policy, but it points the same direction as the policy text. The name-mention era is over, and the reviews it produced may age badly.

Whether Google will retroactively remove older reviews that name staff is explicitly unanswered. No statement exists either way. Anyone telling you confidently that old reviews are safe, or doomed, is guessing. Our honest read: stop soliciting name mentions now, keep serving customers well, and let the archive be what it is.

Google's policy is not the only constraint, and conflating the two rulebooks is the most common error in the coverage. The FTC's Consumer Review Rule, effective October 21, 2024, bans compensation conditioned on a review expressing a particular sentiment, requires clear disclosure when employees or their relatives write reviews, and carries civil penalties of up to $53,088 per violation.

Notice the difference. The FTC permits incentives for honest reviews if they are not conditioned on sentiment and are properly handled. Google bans review incentives entirely. For a business that lives on its Google profile, the stricter rule is the operative one, so the practical answer is simple: no review incentives, full stop.

The FTC layer matters most for a failure mode quotas create. A tech under review pressure who cannot get customers to post starts thinking about posting reviews himself, or recruiting family. Employee reviews of your own business violate Google's conflict of interest policy, and undisclosed insider reviews are exactly what the FTC rule's insider provisions target, at $53,088 a violation. A quota does not just risk your profile. It manufactures the incentive for your own staff to create federal liability.

Strip the banned mechanics out and what remains is a better program. Train every tech on the two-line handoff script until it is muscle memory. Pay bonuses on what techs actually control: callback rate, first-time fix, CSAT scores. Celebrate reviews socially, read the good ones at the Monday meeting, and let the tech whose work gets described in a customer's own words take the lap. Recognition was always the part of the leaderboard that worked.

Then make the ask itself effortless, because a program built on techs remembering to ask fails on busy days. The request should fire when the job closes, in the owner's voice, to the customer's phone, every time. That is the consistency Google's policy actually rewards: every customer gets the same honest ask, no cherry-picking, no pressure, no scripts about stars or names.

That is the shape small Talk is built around. The request goes out by text after the job, the customer answers a few short questions about what actually happened, and the draft is built from their answers, which they edit and post themselves. Your techs never have to hover, your customers never get coached, and the reviews that come back describe the work specifically enough that you know exactly who earned them.