You get more Google reviews by asking every customer, in person, at the moment they can see the work is done, with a short link they can open on the phone already in their hand. That is the whole answer. Everything else is a variation on timing, wording, and who does the asking.
The reason most businesses do not get reviews is not that the tactic is complicated. It is that the ask is delegated to an automated email nobody opens, or it is aimed only at customers the owner already knows are happy, or it is bolted onto a discount that quietly makes every resulting review removable.
Two of those three are policy problems, and they are worth understanding before you build anything. Google’s Maps content policy states that merchants may not “discourage or prohibit negative reviews, or selectively solicit positive reviews from customers.” It also states that merchants may not “offer incentives, such as payment, discounts, free goods and/or services, in exchange for posting any review or revision or removal of a negative review.” Both of those describe practices that reputation vendors still sell as standard features.
What Google does permit is stated just as plainly: 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.” That is a wide lane. Here is how to run in it.
How many Google reviews do you actually need?
Fewer than the round numbers people fixate on, and more consistently than they expect.
The useful frame is relative, not absolute. Search your primary service term plus your city, look at the map pack, and write down the review count and average rating for the three businesses that appear. That set is your actual benchmark. In some categories the leaders sit at 60 reviews. In others they sit at 900. A dentist in a dense metro and a commercial roofer in a rural county face completely different bars, and a generic target of 100 is meaningless in both cases.
Two patterns hold across categories, though. The first is that recency carries disproportionate weight with human readers. A profile with 400 reviews where the newest is fourteen months old reads worse to a prospective customer than a profile with 90 where the newest is from last week, because the stale profile suggests a business that peaked. The second is that a perfect 5.0 average reads as suspicious past a certain volume. A 4.7 with visible criticism and visible owner replies converts better than a flawless run of five-star one-liners, because readers use the negative reviews to calibrate whether the positive ones are real.
That has a direct implication for the ask. When people say they want to get more Google reviews, what they usually mean is that they want a higher rating, and those are different goals with different methods. You are not trying to accumulate five-star reviews. You are trying to accumulate a representative sample of your actual customer base, and a representative sample of a good business is overwhelmingly positive on its own. If your honest sample is not overwhelmingly positive, you have an operations problem that no review strategy fixes.
The Receipt Rule: ask at proof, not at payment
Almost every business asks at the wrong moment, and the wrong moment is checkout.
Payment is when you got what you wanted. Proof is when the customer got what they wanted, and those are frequently not the same event. A roofer gets paid when the invoice clears; the customer feels the value the first time it rains hard and the ceiling stays dry. A dentist gets paid at the front desk; the patient feels it two days later when the sensitivity is gone. A software company gets paid on signature; the buyer feels it the first week the old manual process disappears.
The Receipt Rule is the fix. Attach the ask to the moment the customer receives visible proof that the job is done, not to the moment money moves. The receipt in question can be literal or figurative: the after photo, the delivery confirmation, the completed-repair text, the first successful report, the handover walkthrough. That is your window, and it is usually narrow.
This single change does more to get more Google reviews than any tooling decision, and the mechanism is simple. Review-writing is an emotional act, and emotion decays fast. The customer who just watched you fix something is a different person from the same customer four days later, when the fix has become invisible and normal.
For businesses where proof and payment genuinely coincide, such as a restaurant or a retail counter, the rule collapses to asking at the table or at the bag handoff rather than in an email that night. For businesses with long delivery cycles, it means finding the milestone that feels like completion to the customer and building the ask around it, which may be weeks before or after the invoice.
One warning that comes straight from policy. Google’s rules say merchants should not require or pressure users to leave ratings or write reviews while on the premises, and should not request that specific content be included, including content naming a staff member. Asking at proof is fine. Standing over someone while they type is not, and neither is “if you could mention Dave by name, that really helps him.”
What Google’s policy bans, and what it allows
Three practices get businesses in trouble, and two of them are marketed openly as services.
Review gating is the first and most common. This is the funnel where you send everyone to a survey, ask how the experience was, route the happy ones to Google and the unhappy ones to a private feedback form. Vendors describe it as “protecting your rating.” Google’s policy describes selectively soliciting positive reviews as prohibited. Beyond the policy exposure, gating is self-defeating: it produces a profile with an implausibly clean rating and no criticism, which is precisely the pattern that makes readers discount everything on it.
Incentives are the second. Discounts for reviews, entry into a drawing, a free dessert, a gift card, a partner referral fee. Google’s policy names payment, discounts, and free goods or services explicitly, twice, including content posted following requests for revision or removal of a review in exchange for an incentive. Incentivized reviews are subject to removal, which means you can spend real money generating volume that evaporates in a cleanup sweep.
Bulk and staff-quota schemes are the third. Google specifically calls out merchants requesting that staff solicit a certain number of reviews, and merchants requesting that staff solicit reviews containing specific content. A monthly review quota tied to compensation reliably produces exactly the behavior the policy prohibits, because the person under quota will start asking friends.
What remains legitimate is not a narrow residue. You can ask every customer. You can ask more than once. You can hand them a card, text them a link, print a QR code on the invoice, put a link in your email signature, and train staff to ask verbally, all without touching a prohibited practice. The line is drawn at filtering by predicted sentiment and at paying for the outcome, and everything on the near side of that line is open.
There is one adjacent behavior worth naming because it is also policy-relevant and more consequential than owners realize. Reviews from employees, former employees, contractors, family, and anyone with a professional or personal conflict of interest are prohibited as conflict-of-interest content. Staff writing reviews of their own workplace is one of the most common self-inflicted wounds in this whole category.
Five asks that work, ranked
The verbal in-person ask outperforms everything else by a wide margin, and it is the one businesses skip because it feels awkward. A named human, at the proof moment, saying a specific sentence: “If this went well, a Google review would genuinely help us. I can text you the link right now.” The offer to send the link immediately is the part that matters, because it removes the search step that kills most intentions.
The immediate text with a short link is second, and it is the workhorse for service businesses. Google Business Profile generates a short review link you can copy from your dashboard, which drops the customer directly into the review composer rather than onto your profile page. Send it within minutes of the verbal ask, from a real number, with one sentence and nothing else. No branding, no paragraph about how much you value feedback, no second link.
The printed QR code on the invoice, receipt, or leave-behind is third. It costs nothing per unit and it works for the customers who leave before anyone asks. Print it with a single line of context so people know what they are scanning, and check quarterly that it still resolves, because a dead QR code can sit on ten thousand invoices unnoticed.
The follow-up email is fourth, and its ranking here is deliberate. It is the channel most businesses use first and it converts worst, because it arrives after the proof moment has passed and it competes with everything else in an inbox. It is still worth running as a net for the customers you missed. Send one, at most two, and put the link in the first line rather than beneath three paragraphs.
The recurring touchpoint ask is fifth and is underused by subscription and maintenance businesses. Any moment where you deliver ongoing value, a quarterly service visit, a renewal, a support ticket resolved well, is a proof moment even though the sale happened long ago. These customers are your most satisfied and your least asked.
Across all five, the wording rule is the same: ask for a review, not a good review. Requesting a positive rating is attempting to influence the rating, which is the thing the policy prohibits. It is also unnecessary, because customers who had a bad experience mostly do not write anything at all, and the ones who do are giving you information you need.
Keep the flow running after the push
Most businesses run a review campaign, add forty reviews in six weeks, feel good, and stop. Six months later the newest review is from last spring and the profile reads as neglected again.
The fix is to make the ask part of a process rather than a project. Businesses that get more Google reviews year after year are not running better campaigns, they are running the ask as a permanent step in the job. Whoever owns the proof moment owns the ask, and it goes into the job checklist, the closeout script, the delivery workflow, wherever your actual work is tracked. Then measure one number weekly: reviews received divided by jobs completed. Not total count. The rate. A business converting eight percent of completed jobs into reviews and running steadily will pass a business that converted thirty percent during one heroic quarter and then quit.
Reply to all of them, including the good ones, in two or three sentences that reference something specific from the review. This is not decoration. Owner responses are visible to every future reader, they signal an active operator, and the specificity is what separates a real reply from a template. It also builds the habit that makes handling the eventual bad review much less dramatic.
Watch for disappearances. Google removes reviews it flags under its policies, and a batch vanishing usually means something in your process crossed a line: a staff member asking friends, a promotion someone attached an incentive to, or a burst of reviews from a single location that pattern-matched to manipulation. Investigate rather than appeal first, because if the flag was correct the appeal will fail and the practice will keep costing you.
Get this right and the reviews stop being a marketing project you have to restart every year, because the asking is already inside the work.