Google banned staff-name review requests. The 30-day sweep for multi-location ops

Somewhere in your brand standards there is a line telling staff to ask happy customers for a Google review, and to ask them to mention the team member by name. It is on a counter card, in an onboarding deck, possibly in a bonus calculation. Across two hundred branches it has been repeated tens of thousands of times.

Google's Rating Manipulation policy now prohibits exactly that. The consequence is not one bad review; it is one bad script executed at scale, in every location, with your brand's name on it.

What Google's policy actually says

The live Rating Manipulation policy lists, among prohibited practices, "Merchants requesting that staff solicit a certain number of reviews" and "Merchants requesting that staff solicit reviews that include specific content", specifically naming "content that identifies a staff member". It also prohibits merchants that "require or pressure users to leave ratings or write reviews while on the premises".

Google defines the wider offence broadly: rating manipulation is "any attempt to directly or indirectly influence the star rating of a place on the map through fake and misleading content", per its rating manipulation definition. A separate policy defines incentivised reviews as those "influenced by a payment, discount, free goods or services, or any other benefit offered to the reviewer; or biased by a personal or professional conflict of interest".

Note what is still allowed, in Google's own words: you 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 for a review is fine. Scripting what it says is not.

One more line matters for anyone using AI anywhere near this: Google states that its policies "apply to all Maps user generated content, regardless of whether the content is human-generated or AI-generated content" (prohibited and restricted content).

Google's policy pages carry no changelog, so we are not going to put a date on when those staff-name bullets appeared. The trade press placed it in April 2026; what is verifiable is that the text is live today.

The enforcement side moved first

The policy wording followed a step change in detection. In a post published on 16 April 2026, Google said it blocked or removed 292 million policy-violating reviews in 2025, removed more than 13 million fake Business Profiles, and restricted over 782,000 policy-violating accounts. The comparable 2024 figures from the previous year's post were 240 million reviews, 12 million profiles and 900,000 accounts.

The same post describes Gemini models now blocking policy-violating Maps edits before they publish, rather than after. If your review programme depends on content that breaches a policy, the failure mode is no longer a slow takedown. It is content that never appears, and a profile that accumulates signals you cannot see.

The second regulator most ops teams have not read

Google is not the only body with a view. The FTC's Consumer Reviews and Testimonials Rule has been in effect since 21 October 2024. Its guidance is direct: "you can't suggest to consumers that their reviews must be positive (or negative) in order to obtain a promised incentive", and insiders writing reviews must "disclose their relationships". It also confirms what you may always do — "respond publicly to the review".

Enforcement is live. On 22 December 2025 the FTC warned ten companies about possible violations, noting civil penalties of up to $53,088 per violation. On 11 May 2026 the FTC and Illinois took action against a home services company that the complaint says created thousands of fake business listings and used "made-up five-star reviews to dilute legitimate one-star reviews from actual customers".

No enforcement action has been announced specifically over staff-name review scripts. The point is not that the FTC is coming for your counter card. It is that "we told customers what to write" sits close to a rule with per-violation penalties, and multi-location brands multiply violations by definition.

The four SOPs most brands still have live

An audit across a multi-site estate usually turns up the same four:

• A review target per branch or per shift. Prohibited where staff are asked to solicit a certain number of reviews.
• A script asking customers to name the person who served them. Prohibited as requesting specific content identifying a staff member.
• A tablet at the till, handed over before the customer leaves. Prohibited as pressuring users to review while on the premises.
• A bonus tied to named mentions. This is the expensive one, because it is wired into payroll rather than a poster, and it converts a policy breach into a standing incentive.

The 30-day sweep

Week one, find every instance. Search your LMS, brand standards, counter-card artwork, email and SMS templates, receipt footers and QR landing pages for "mention", "name", "five star" and "review target". Week two, rewrite to the permitted form: invite a review, say nothing about rating or content. Week three, retrain and change the incentive — reward the behaviour customers are describing, measured from reviews you receive, not from the words you asked for. Week four, re-measure and keep the evidence: what changed, when, and who signed it off.

What about the reviews that already name staff?

Leave them alone. The policy restricts what a merchant requests, not what a customer freely wrote, and there is no obligation on you to remove historical content. Attempting a mass cleanup would be worse than useless: it deletes genuine customer voice and it creates an edit pattern across hundreds of profiles that Google's detection is explicitly built to notice.

What does need attention is anything downstream that was calculated from those mentions. If a league table, a bonus run or a quarterly award is still being computed from a period when staff were scripted to ask for names, the data is contaminated. Draw a line at the date you changed the SOP, keep the historical numbers for the record, and start the new measure from a clean base.

Why the response side is the safer place to spend effort

Every hour redirected from soliciting reviews to answering them is spent on something no policy restricts and consumers actually notice. BrightLocal's 2026 survey of 1,002 US adults reports that 97% of consumers read reviews for local businesses and 74% look for reviews written in the last three months. Recency and responsiveness are the levers still available to you.

The gap is wide enough to be worth chasing. If the multi-location average is 46.9% of reviews answered at 4.3 days, a brand that answers 90% within 24 hours is visibly different on every profile page a customer opens — and it got there without a single scripted request.

You can still recognise your best people, by reading instead of asking

The policy restricts what you request. It does not touch what customers volunteer, and customers volunteer names constantly. The compliant version of a named-mentions programme reads the reviews you already have, extracts the names customers chose to write, and ranks by them. Nobody is scripted, and the recognition is better evidence because it was unprompted.

That is the job Loculens does across a multi-location estate: every branch's Google reviews in one workspace, sentiment and topics per location, team members matched against your own roster, and a reply drafted in your voice for the ones still unanswered. A person reads it and presses send, which is also the only way to stay inside the line above.

What to measure from here

Replace the review-count target with three numbers that are safe to chase. Response rate and response time: SOCi's 2026 Local Visibility Index, covering 2,751 brands and around 350,000 locations, found 46.9% of Google reviews receiving responses at an average response time of 4.3 days. Set your SLA against what customers expect — BrightLocal's 2026 consumer survey (1,002 US adults) reports 89% expect business owners to respond, 19% expect a response the same day, and 81% within a week.

Third, unprompted named mentions per branch per month. It is the metric your old programme was trying to buy, it is now the only legitimate way to get it, and it moves only when service does.

One caution before anyone rewrites a content strategy around AI search: Google's Search Central documentation on AI features states plainly that "There are no additional requirements to appear in AI Overviews or AI Mode, nor other special optimizations necessary." Fix the SOPs because the policy and the FTC rule say so, not because an agency deck promised an AI ranking boost.