If you run an HVAC, plumbing, roofing, or electrical shop, you already know this: reviews can make or break local rankings. Now there is a specific, avoidable risk that many operators have been using without realizing it is exactly what Google is cracking down on.
Google is enforcing GBP review policies harder after its April 2026 update. Two new bans are the focus: no staff review quotas tied to performance, and no asking customers to mention specific employee names. Google also says it uses Gemini-powered detection before reviews go live, which means mistakes get caught earlier, not later.
What Google actually changed in April 2026 (factual recap of the two new bans + Gemini pre-publication detection)
Google’s April 2026 enforcement wave targets behaviors that try to steer how reviews are written or measured inside the business. Two things are now explicitly banned:
- Staff review quotas tied to performance metrics.
- Directing customers to include specific employee names in their reviews.
Google also introduced detection that can identify policy-violating content before reviews go live. The point for you: it is not only about what a customer writes. It is about what your process prompts them to write, and what the system detects during pre-publication.
Existing rules still apply. If your team offers incentives, filters out negative reviewers, or creates reviews from staff and family, those practices were already prohibited and remain prohibited.
As enforcement ramps up, businesses are seeing more review removals and some GBP profile suspensions. The operational takeaway is simple: stop running review systems that depend on pushing customers toward a specific format, names, or measurable “review output.”
The two practices that are now explicit violations
Staff quotas tied to performance metrics
This is the easiest trap to spot once you look at it directly. If you tell technicians or dispatchers they must hit a number of reviews per week or month, and you connect that to performance in any form, you are in the danger zone.
Here is what it looks like in practice:
- “Get 3 reviews this month or you are not meeting expectations.”
- “If you are behind on reviews, you will lose bonus pay.”
- “Top performers are the ones with the most Google reviews.”
Operators sometimes do this with good intentions. They think they are just setting a goal for customer follow-up. But if the goal is measurable review volume and it is tied to performance evaluation, Google has made that the kind of staff review quota it does not allow.
Even if you never script the customer’s language, the quota itself can be used to guide review production. That is exactly the behavior Google is banning.
Employee-name solicitation in reviews
The second ban is about what your request prompts the customer to write. Google explicitly banned directing customers to mention specific employee names in reviews.
What it looks like:
- “Please include Jake’s name in your review so people know who helped you.”
- “In the review, reference the technician by name.”
- “Mention the office team member who answered the phone.”
This is common because customers often like to thank the person who showed up. But policy is about your instruction. If you are asking customers to include a specific employee name, you are steering the review toward a format. That direction is now an explicit violation.
What makes this especially tricky: many shops have review texts saved in templates. If the template includes name prompts, you may be violating even if you think the request is “polite.”
What stays the same (reviewer incentives, review gating, fake reviews)
Google’s April 2026 update does not replace the old rules. It builds a stricter enforcement pattern on top of them.
Still banned:
- Incentivizing reviews (for example, offering discounts, gift cards, prizes, or “store credit” in exchange for a review).
- Review gating (for example, blocking negative reviewers, hiding access, or creating steps designed to prevent criticism from being posted).
- Fake reviews, including reviews created by staff or family members.
If you already avoid these, you are ahead of the curve. The April 2026 changes mainly add two new “do not do this” items that have been happening in real businesses for years.
The compliant review system (a 5-step operator playbook)
You need a system that makes it easy for customers to leave honest feedback without steering how they write, who they name, or what volume your team must produce. The goal is simple: ask at the right moment, send a clean link, and request customer feedback in their own words.
Here is a five-step operator playbook you can use this week.
- Ask at the right moment
Ask for feedback right after the job is done and the customer has had a chance to confirm the work is complete. For example: after you explain the results, confirm everything is working, and answer questions. The request should sound like a normal customer follow-up, not a quota push.
Keep it short. Do not say “we need a review.” Say you would appreciate their honest experience if they are willing.
- Send a clean review link (no name scripts)
Send the review link in a way that does not include templated language that directs content. The request message should not instruct the customer to mention a specific employee by name.
A safe message looks like: “If you have a minute, here is a link to share your experience on Google.” Then provide the link.
- Request honest feedback in the customer’s own words
Use a question that invites their perspective rather than a checklist. For example:
- “What went well?”
- “How was communication?”
- “Did the work meet expectations?”
Do not tell them what to say about a particular person. Do not provide a “fill in the blank” review prompt.
- No incentives, no special deals tied to reviews
Do not offer discounts, credits, or perks for reviews. If you want to do something for customers, do it because the job is done and you want to keep relationships strong, not because a review was posted.
If you already have a customer loyalty program, keep it separate from review requests.
- Monitor and reply within 48 hours
Monitor your GBP reviews and respond quickly and professionally. This protects your customer experience and helps you correct issues publicly when they happen.
Link to action: build your “review request system” around this workflow, then tighten your response process with a cadence you can actually maintain at your shop. If you want a simple framework for day-to-day GBP tasks, use the review request system.
What to do if you've been doing this (audit, retrain, document)
Start with an honest audit of what your team is actually doing, not what you think they do. Then fix the parts that create review steering or staff pressure.
Do this in order:
- Audit your scripts and templates
Look at every review request message: text templates, voicemail scripts, follow-up emails, and any “review instructions” your staff uses. Delete anything that says “mention [name]” or that implies a customer should write the review about a particular employee.
Also remove any language that ties reviews to performance goals.
-
Check your internal incentives and expectations
List every way you measure performance that includes review counts or review output. If you track review volume by employee and use it in reviews, retrain immediately. Set customer service standards that are not review quotas. -
Retrain the team on the request format
Train for clarity, not memorization. Give a single approved version of the customer request message that:
- asks for honest feedback,
- sends a link,
- does not mention names,
- does not offer incentives.
Practice it in role-play with your front desk, dispatch, and lead techs.
- Document the compliant process
Write down your “current approved workflow” and keep it where the team can find it. Include the approved customer message, where the link comes from, and the rule: no name solicitation, no review quotas.
If you ever get questions from a supervisor or new hire, you want an answer you can point to in writing.
- Clean up your follow-up outreach
If your automated messages were built using old templates, fix them now. For example, if a system message adds “please mention our technician by name,” change that logic before it gets sent again.
You cannot undo the past review requests, but you can stop creating new violations.
Bottom line
Google’s April 2026 enforcement wave is aimed at review production practices you control: stop staff review quotas tied to performance, stop telling customers to mention specific employee names, and rely on a simple, compliant request flow that asks for honest feedback without steering. If you audit your scripts, retrain your team, and run a consistent process, you reduce the chance of removals and suspensions while keeping your GBP reviews useful for real customers.