The Compliant Way to Ask for Google Reviews in 2026 (With Templates)

A lot of the "best practice" review request scripts floating around are now policy violations under Google's 2026 update. Here's language that's both compliant and actually works, across every channel you're likely to use.

The Bloom team · July 2026

If you've read Google's 2026 review policy update, you already know a lot of what used to count as smart review-request practice, pre-screening by sentiment, incentives, scripted content asks, is now explicitly prohibited and actively enforced. That leaves a real, practical question: what does a request that's both compliant and effective actually sound like, across text, email, and in-person materials?

Here are templates you can use directly, organized by channel, along with the reasoning behind why each one is built the way it is, and what the data says about getting the best response rate without crossing any lines.

The Core Rules Behind Every Template

Before the templates themselves, the three things every compliant request needs to have:

Sent to every customer, the same way, regardless of how the interaction went. No pre-survey, no filtering based on a prior answer.
Neutral language, no direction toward a specific rating or specific content to mention.
No incentive attached, direct or implied, including a "thank you" gift that's promised in connection with the review.

Every template below follows these rules. If you adapt them, keep those three things intact, they're what separates a compliant ask from a policy violation, not the specific wording you choose.

Text Message Template

Hi [Name], thanks for choosing [Business Name] today! If you have a minute, we'd really appreciate your honest feedback on Google: [link]. It helps other people in [city] find us, and it helps us know what to keep doing well.

Why this works: it's sent identically to every customer, doesn't suggest a star rating or specific content, and frames the ask around helping others and improving, not around getting a good score. Text messages also tend to see meaningfully higher response rates than email for this kind of request, since they're read faster and require less deliberate action to open.

Email Template

Subject: How did we do?

Hi [Name],

Thanks again for your visit to [Business Name]. We'd love to hear about your experience, good, bad, or anywhere in between. If you have two minutes, a Google review helps other people in [city] find us and helps us keep improving.

[Review link]

Thanks for your time either way.

[Name / Business Name]

Why this works: explicitly inviting any kind of feedback ("good, bad, or anywhere in between") is one of the clearest ways to demonstrate the request isn't sentiment-filtered, which matters both for Google's policy and for how genuine the request feels to the customer reading it.

QR Code / In-Person Card Language

We'd love your honest feedback. Scan to leave a Google review: [QR code]

Keep in-person materials brief and neutral. Since Google's 2026 update restricts pressuring customers to review while still on premises, the QR code or card should be something customers can act on later, not something staff actively push in the moment. A card left at a table or counter works; a staff member standing over a customer's shoulder while they scan it does not, and this distinction is one of the more commonly overlooked parts of the policy update.

Verbal Script, If Staff Mention It At All

Google's restriction on on-premises pressure doesn't mean staff can never mention reviews verbally, but it does mean the framing matters. A compliant version sounds like: "There's a QR code on your receipt if you'd ever like to share feedback, totally up to you." This mentions the option without requesting action in the moment, and avoids anything that could read as staff soliciting a specific outcome. A non-compliant version, "if you could leave us a great review, that would really help us out," crosses into exactly the kind of on-premises, outcome-directed solicitation the update restricts.

Follow-Up After a Service Recovery

For situations where you've resolved a complaint and want to invite a review afterward, covered in more depth in how to turn an angry customer into a 5-star review:

Hi [Name], I wanted to follow up now that everything's sorted. We're glad we could get this fixed for you. Whenever you have a moment, we'd appreciate your honest feedback on Google: [link]. No pressure either way, just wanted to check in.

The "no pressure either way" line matters more than it might seem, it explicitly signals the request isn't conditional on a positive outcome, which is both the compliant version and the version that reads as most genuine to the customer given what they just went through.

Template for Repeat or Regular Customers

For businesses with frequent repeat visitors, requesting a review after every single visit tends to feel repetitive and can reduce response rates over time. A reasonable version for regulars:

Hi [Name], you've been coming in for a while now and we really appreciate it. If you've never had a chance to leave us a Google review, we'd love to hear your honest take whenever you have a minute: [link]. No worries if you'd rather not, just wanted to ask once.

This works well as a quarterly or occasional touchpoint rather than a per-visit request, and the explicit acknowledgment that it's fine to decline tends to improve rather than hurt response rates, since it removes any sense of obligation.

What to Avoid in Any Version

"Leave us a 5-star review" or any specific rating mention
"Mention [staff name] if they helped you!", banned under the 2026 policy update
Any version sent only to customers who indicated satisfaction first, this is review gating
Anything tied to a discount, gift, or entry into a draw
Sending it while the customer is still on-site, or in a way that pressures an immediate response

Timing Matters as Much as Wording

Send the request shortly after the experience is complete, generally within a day, while it's still fresh, but after the customer has left. Waiting too long reduces response rates significantly, since the specific details of the experience fade and the request starts to feel disconnected from the visit. Asking too early, before the service is actually finished, reads as premature and can produce reviews about an incomplete experience, or simply get ignored because the customer hasn't fully formed an opinion yet.

What Response Rate Should You Actually Expect?

This varies meaningfully by industry and by how well-targeted the timing is, but a consistent, well-timed, neutral request typically converts a meaningful minority of customers who receive it, not a majority, and that's normal rather than a sign something's wrong. The more useful number to track isn't the response rate on any single request, it's the cumulative review count and recency trend over several months, since even a modest per-request conversion rate compounds into significant review velocity when it's applied consistently to every customer rather than sporadically to a subset.

Businesses that see meaningfully better response rates than average tend to share a few traits: they send the request promptly (within a day), they use a channel the customer already checks regularly (text over email for most consumer businesses), and they make the actual action required as short as possible, ideally a single tap through to a pre-loaded review screen rather than a multi-step process the customer has to navigate themselves.

Making This Consistent Without Relying on Memory

The biggest gap between businesses with strong review velocity and everyone else usually isn't the quality of the ask, it's whether the ask happens every single time. Manual processes depend on someone remembering, during a busy shift, to send the message. That's the exact problem a QR-based or automated trigger solves: the same neutral request goes out after every visit, without depending on staff memory, which is also what keeps the process compliant, since there's no manual point where someone could start filtering by sentiment, intentionally or not.

Frequently Asked Questions

Is it okay to personalize the customer's name in an automated request? Yes, personalization with the customer's name and the specific visit doesn't affect compliance, what matters is that the same neutral, unconditional request goes to everyone.

Can I vary the wording between customers? Yes, as long as every version stays neutral and unconditional. What's not allowed is varying who gets asked, or how prominently the Google link is presented, based on how the interaction went.

How often should I send requests if a customer visits frequently? Once per visit is reasonable for infrequent customers; for regulars, most businesses space requests out (quarterly or so) rather than asking after every single visit, to avoid it feeling repetitive and to protect response rates over time.

Does it matter whether the request comes from a personal name or the business name? Both work. A request that feels like it's from a specific person, an owner or a staff member, sometimes gets slightly higher response rates, but either is compliant as long as the content follows the same rules.

What response rate should I expect from a well-built request? It varies by industry, but a consistent, well-timed, neutral request typically converts a meaningful minority of customers, enough that steady volume adds up significantly over a few months, even without anyone individually chasing reviews.

Should the private feedback option be mentioned in the same message as the Google review request? It can be, as long as it's offered alongside the Google link rather than instead of it, and the Google link stays equally visible regardless of what the customer indicates. A version that says "leave us a review, or if something wasn't right, let us know privately here instead" risks reading as gating depending on how prominently each option is presented.