You are probably not short on customers who would say something good about the work. BrightLocal's 2026 survey found 94% of its 1,002 respondents were open to writing a review. So the practical question behind how to get Google reviews is rarely whether people are willing. It is what you say in the twenty seconds you have at the end of a job, in a text, or on the last line of an invoice.
Reviews carry the Trust lever, the one answering "should I believe you?" for somebody comparing two names on a map. They are also the visible output of Customer momentum, which feeds Attention, because a profile with recent reviews does more work in search than an old one with four.
Everything below is the human ask: the words, the timing, and how you take a no.
Why one request lands as natural and another lands as desperate
Pressure is the variable, not politeness. A meta-analysis in Human Communication Research covering 28 articles found that language threatening somebody's freedom increased anger and psychological reactance, and that those reactions tracked with weaker persuasion. It is cross-domain research rather than a Google review experiment, so read it as a reason to watch your verbs.
Conditional wording carries its own cost. Six experiments published in 2023 found that requests framed as "if you loved our product" made the retailer seem more manipulative and less trustworthy than a neutral request, even after a positive experience.
The exit matters as much as the ask. Two preregistered experiments published in 2024 found that giving people explicit language for saying no made them feel freer to refuse, while compliance did not differ significantly. So "no pressure" earns its place by changing how the request feels to the person receiving it, whatever it does to the count.
How to get Google reviews inside Google's rules
Google allows you to ask. Its user generated content policy permits soliciting reviews that reflect a genuine experience, provided no incentive is attached and no attempt is made to influence the rating or the content. Google publishes no script of its own, so the wording is yours to write inside that boundary.
The boundary is specific:
- Incentives are out. A discount, free work, or anything else of value offered for posting, changing, or removing a review is prohibited, and adding "any rating is fine" does not rescue it.
- Selective solicitation is out. Sending the link only to customers who already signalled they are happy is review gating, whether software sorts them or you do it in your head at the truck.
- Fake reviews are out, including anything written by somebody without a genuine experience of your business.
- Pressure on the premises is out. Google says you must not require or pressure somebody to leave a review while they are standing there with you.
- Telling people what to write is out. In April 2026 Google added explicit examples covering staff review quotas and requests for specific content, including naming a staff member.
That last one catches owners being helpful rather than sneaky. Referencing the job in your own message is fine, since you wrote it. Telling the customer what belongs in theirs is not.
The ask you make in person
"Thanks for trusting us with the water heater. If you'd like to leave an honest Google review later, I can text you the link. No pressure."
That wording asks for an honest review instead of a good one, which keeps you inside policy and off the hook for whatever somebody decides to say. It names the job, so it reads as a comment on the work, and it moves the posting to later, which keeps your technician out of a kitchen watching somebody type.
Make the same offer to everyone who genuinely had the service, not only the ones who seemed pleased. Consistency keeps the practice clear of selective solicitation and spares your crew the read-the-room math at the door.
The text you send yourself
"Hi Dana, this is Ryan from Ringneck Heating. Thanks again for having us out for the furnace tune up. If you'd like to leave an honest Google review, here's the direct link: [link]. No pressure."
Say who you are and name the interaction, then include one link and let the message end there. Naming the job is a tone choice rather than a proven tactic, since we found no study showing a personalized request outperforms a generic one. What it reliably does is make the message read as one to one instead of a blast.
The direct link comes from your Business Profile under Read reviews, then Get more reviews, on a profile that is claimed and verified, which is the groundwork in turning a Google Business Profile into paying customers. Your customer needs a Google account to post, though not a Gmail address.
Send it on the thread you already use with that customer, and ignore anybody quoting a win rate by channel, since those numbers measure stated preference rather than reviews actually posted.
The line on a receipt or an invoice
Share an honest Google review: [QR code] [direct review URL]
Google names receipts, thank you emails, and printed displays as places for the link or code. Applying it to a service invoice is our extension rather than Google's wording, and it works for the reason a receipt does: nobody has to say no to a piece of paper.
QR generation currently happens in a desktop browser, so build the printed piece from a computer, and keep any offer or star request off the page.
The ask after you have fixed something
Recovery changes the order of operations. Resolve the problem first and make sure the customer agrees it is resolved, because a fix sometimes needs time to prove itself before any request makes sense. GatherUp's 2025 survey found 69% of consumers who had written a negative review would give the business another chance if the owner's response resolved the issue, and 48% would update their review. Those figures describe what follows a resolution rather than a request.
When nothing has been posted publicly and the fix is holding:
"Thanks for giving us the chance to fix the drain line. I'm glad it's running right now. If you'd like to share an honest review of the whole experience, here's the Google link: [link]. No pressure."
When a negative review is already up, close the service loop and leave the review alone:
"Thank you for giving us the chance to make this right. I'm glad the system is working. If anything changes, contact me directly."
The remedy never gets conditioned on a review, and you never ask for a positive one to offset a complaint or request a star change. Google notes that constructive follow-up can naturally lead a reviewer to update what they wrote, and that stays theirs to decide.
Timing runs on when the customer can judge the work
GatherUp's 2025 respondents preferred a fast request, with 77% wanting one within three days or less, including 35% at the time of service. BrightLocal's 2025 survey found the expected window varies by category, and for trades and service businesses the most common answer sat at roughly three days to a week.
Fast is not automatically better. Two randomized field experiments published in 2023, covering 8,123 tour and 291,954 apparel customers, found that immediate reminders reduced posting against a randomized control while delayed reminders increased it. Digital reminders are not a person at a doorstep, but that is enough to retire "ask the second you finish" as a universal rule.
The workable standard is outcome first, then a prompt while the interaction is still recognizable. A water heater the customer watched get tested clears that bar at the doorstep. A roof, a landscape install, or a treatment plan may not clear it for a week.
The phrases that sound desperate, and how to take a no
Most of these come from wanting reviews for perfectly good reasons.
- Asking for five stars or "a positive review," which is a policy problem and also tells the customer their honest opinion was not what you wanted.
- Leading with your own need. "We really need reviews this month" moves the subject from their experience to your obligation.
- Apologizing your way in. A preamble about how you hate to ask signals that you believe you are imposing, and the customer takes the cue.
One neutral request is the whole play in a manual process. If the answer is no, the entire response is "No problem at all. Thanks again." Anything longer reopens a decision the customer already made. Treat hesitation the same way, and if somebody says "maybe, I'll see how the week goes," send the link once and let it sit.
A verbal yes creates one obligation, which is to send that link the same day, while the job is still the thing they were talking about. Making somebody search for you afterward is where most verbal yeses quietly expire.
Where the ask ends and the system begins
Silence after a promised link is where the manual version reaches its limit, since no reliable number of human follow-ups has been established and chasing is the behavior this whole post exists to avoid. What is left is who gets asked and when the request goes out, which is a workflow question rather than a scripting one, and we wrote that side up in building a review system that runs itself.
The reason it is worth building is the handoff back to Attention. BrightLocal's 2026 respondents were unforgiving about thin profiles, with 47% saying they would not use a business with fewer than 20 reviews and 74% caring only about reviews from the previous three months. Google states that more reviews and positive ratings can improve local ranking. One good ask is a Trust move, and a steady supply of them turns into an Attention one.
If handing off the asking, monitoring, and responses sounds better than owning it, our Reputation Engine runs at $2,000 to build and $1,000 a month per location. If you would rather get a read on where you stand first, a free consultation covers your current scripts, where your review link points, and whether anything you are doing now brushes against Google's policy. No pressure to commit to a full project. Easy to start, easy to stop.
