The direct answer: you are explicitly allowed to ask. Google's policy permits merchants to "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."
Two things in that sentence do the work. You may ask. You may not incentivise, and you may not attempt to influence the rating or the content. Several common review tactics run into one of those two limits, including one that is widely promoted — so it is worth checking your own process against the rules rather than assuming a popular method is a permitted one.
This guide covers exactly where the line is, why the most common shortcut is on the wrong side of it, and a request system that works without crossing it.
What Google actually prohibits
These are Google's own words, from its Maps prohibited-content policy.
Fake engagement. Content that is "not based on a real experience or does not accurately represent the location or product in question" is prohibited, as are reviews "that have been paid for, directly or in kind."
Note "in kind." A free coffee is payment in kind. So is a discount, a prize draw entry, or a loyalty-points bonus.
Incentives. Google does "not allow merchants to: 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."
Read the end of that clause. The prohibition covers incentives to post a review, to revise one, and to remove a negative one. Offering an unhappy customer something to take their review down is specifically named.
Conflicts of interest. "Content that is based on a conflict of interest" is prohibited, including conflicts arising from "current or former employment, a contractual or consultory relationship, or other professional or personal affiliations."
That covers the obvious — reviews from staff, from the owner's second account, from a friend who never used the service — and the less obvious, such as a contractor you work with regularly reviewing you as though they were a customer.
The principle underneath all of it: "Contributions to Google Maps should reflect a genuine experience at a place or business."
The common tactic that breaks the rules
Here is the one worth stopping on, because it is often promoted as best practice and appears as a feature in some review tools.
Review gating is the practice of asking customers how they feel first — often a "rate us 1–5" step — and then routing only the happy ones to Google while sending the unhappy ones to a private feedback form. It is popular because it works, in the narrow sense that it raises your visible average.
You do not have to infer anything here. Google's rating-manipulation rules name it directly: merchants must not "Discourage or prohibit negative reviews, or selectively solicit positive reviews." A flow that sends happy customers to Google and unhappy ones to a private form is selective solicitation by design — that is the whole point of it.
The related rules in the same section are worth knowing while you are there: merchants should not require or pressure people to leave reviews while on the premises, should not request that specific content be included, and should not set staff quotas for review counts or ask staff to solicit reviews containing specific content.
If a vendor demo shows you a flow where a 1–3 star response goes somewhere other than Google, that is review gating, whatever it is called on the slide. Ask the vendor to point you at the policy language that permits it.
The honest version is simpler and less comfortable: ask everyone, and accept what comes back.
What you can do instead
Everything below is permitted under the policy quoted above. None of it requires software.
Use one consistent trigger, at the same point in every job. This is workflow advice rather than a Google requirement. The rule is that you must not selectively solicit positive reviews, and a fixed trigger is the simplest way to be certain you are not. Choosing who to ask based on how you think they feel is where selective solicitation starts, and the line is easier to hold if you never make that judgement at all — a job qualifies because it is finished, never because it went well.
Ask at the moment of completed value. Not at the invoice. The right moment is when the thing they wanted has visibly been delivered — the repair is complete, the appointment has taken place, the problem is gone. That is when the memory is specific enough to write about.
Consider asking in person first, then following up in writing. One workable pattern is a verbal ask followed by a text containing the direct link, so the message is expected rather than cold. Treat that as an example to test in your own business, not a measured winner — we have no conversion data for it and neither does anyone quoting you a figure without a study behind it.
Make the link one tap. Google Business Profile provides a short review link. Removing the step where someone has to search for you is a sensible reduction in friction.
Invite an honest review — do not steer what it says. Google's rating-manipulation rules prohibit requesting that specific content be included, as well as asking staff to solicit reviews containing specific content. So "please mention the new bathroom fit-out" is out, and so is "please leave us five stars." Both are steering.
What is left is simple and works fine: invite them to share their honest experience, in their own words, and leave it there. You are asking for a review, not for a particular review.
Never make it conditional. No discount, no entry into anything, no free add-on. Not for the customer, not for the staff member who collects the most.
A note on staff, because this part is explicit rather than inferred. Google's rules name merchants "requesting that staff solicit a certain number of reviews" and "requesting that staff solicit reviews that include specific content" as prohibited. So a review-count target for your team is not a grey area.
Tying pay to review volume is a related risk rather than a separately named rule: it puts pressure on the person asking, and pressure is what tends to bend a process. If you want to recognise staff here, recognise the asking being done consistently, not the number of reviews that come back.
Two scripts you can use today
These are deliberately plain. Adapt the wording; keep the structure.
In person, at completion:
"Glad that's sorted. One thing that genuinely helps us — if you've got a minute later, a quick Google review makes a real difference for a business our size. No worries if not. I'll text you the link either way."
Why it works: it is honest about why you are asking, it gives explicit permission to decline, and it sets up the follow-up so the text is expected rather than cold.
The follow-up text, same day:
"Thanks again for today. Here's that review link if you have a moment: [link]. If anything wasn't right, reply here and I'll sort it."
That last line is the important one, and it is not gating. You are not routing the unhappy away from Google — the review link is right there for them too. You are offering to fix a problem, which you should do regardless, while leaving the choice entirely with them.
Responding to reviews
Google's guidance is direct: "When you reply to customer reviews, it shows that you value their feedback." Google also states that "More reviews and positive ratings can help your business's local ranking."
Two honest caveats on that second sentence, since it is the one most often over-read: it says reviews can help local ranking. It is not a formula, not a guarantee, and nobody outside Google can tell you how much weight it carries relative to anything else. Treat it as a reason to take reviews seriously, not as a lever with a known multiplier.
A workable response habit:
- Reply to all of them, positive included. A one-line thanks is enough.
- Reply to negative ones last, and slowly. Draft it, wait an hour, then send.
- Do not argue the facts in public. State what you understand, take responsibility for what is yours, and move it offline: "I'd like to sort this out — can you call us on X?"
- Never offer anything in exchange for changing or removing a review. This is explicitly prohibited by the incentives clause above. Fix the underlying problem; if the customer chooses to update their review afterwards, that is their decision, unprompted.
When a review is genuinely against policy
Some negative reviews are not customer feedback at all — they are from a competitor, a former employee, or someone who has confused you with another business. Those fall under the fake engagement and conflict-of-interest rules quoted above, and can be reported through Google.
Three realistic expectations:
- Reporting is not appealing a bad opinion. A genuine customer who had a bad experience and said so is not a policy violation, however unfair it feels.
- Removal is not guaranteed, and the process can be slow.
- Reply publicly while you wait. A calm, factual reply is visible to every future reader, which is usually worth more than the removal you may not get.
The checklist
Your asking system
- Have you picked one moment in the job when the ask happens, every time?
- Does everyone on the team ask at that moment, rather than choosing who seems happy?
- Do you have the direct review link saved and one tap away?
- Is there a same-day follow-up message with the link in it?
- Is the ask free of any incentive — for the customer and for your staff?
Policy check — answer honestly
- Does any step in your process route unhappy customers somewhere other than Google? If yes, that is gating; remove it.
- Has anyone connected to the business ever left a review? Employees, family, contractors?
- Have you ever offered anything for a review to be posted, changed, or taken down?
Responding
- Are you replying to reviews at all — including the positive ones?
- Do negative replies go out after a pause, and move the detail offline?
Measurement, honestly
- Are you tracking review count and average over time, rather than inferring a ranking effect you cannot measure?
Where AlgoEthos fits
Our AI Visibility service covers agreed listings, content and posts, and review replies prepared for your approval, with a scheduled monthly service review.
Two things that is not, stated plainly so nobody buys the wrong thing: it is not an outbound review-request service — the asking system in this article is yours to run — and the monthly review is a scheduled check-in, not continuous monitoring.
We would not build you a gating flow if you asked. The policy risk is real, but the better reason is that an average produced by filtering out unhappy customers tells you nothing true about your own business, and the value of reviews is that they are information you can act on.
If you would rather run all of this yourself, run it. It is public policy and two text messages.
Next step: book a free walkthrough and we will look at your current profile and review pattern with you.
Related reading on this site
- AI Visibility — listings, reviews and local search
- AI for Local Business — the practical overview
- Contact — book the walkthrough
Sources
Both checked 12 September 2026. Google updates these policies; re-check before relying on them.
- Google Maps user-contributed content policy — prohibited and restricted content — fake engagement, paid reviews "directly or in kind", the incentives prohibition covering posting/revision/removal, conflict-of-interest rules, and the explicit permission to solicit genuine reviews without incentives or attempting to influence the rating or content.
- Tips to improve your local ranking on Google — replying to reviews shows you value feedback; more reviews and positive ratings can help local ranking.
- Reply to Google reviews — direct review link, encouraging balanced feedback, and replying helpfully and promptly. These are Google's suggestions for responding, not requirements.