Review gating, screening customers before asking for reviews, violates Google's policies and can get your reviews removed. Here's what counts as gating, what the risks are, and compliant alternatives that still generate great reviews.
There's a version of review gating that most business owners don't realize they're doing. It's not the obvious version, the service that makes unhappy customers fill out an internal feedback form while routing happy customers to Google. That one, almost everyone knows is wrong.
The less obvious version is asking your staff to "feel out" a customer before sending a review request. Or sending review request emails only to customers who gave positive scores on an internal satisfaction survey. Both of those are review gating under Google's policy, and both can get your reviews removed or your profile suspended.
This guide covers exactly what review gating is, what Google's policy says, where the line actually falls between gating and legitimate review management, and what compliant review acquisition looks like.
Understanding Review Gating
The Risks and Alternatives
Review gating is the practice of filtering customers based on their expected sentiment before asking them to leave a review, routing customers who seem satisfied toward a public review platform, and routing customers who seem dissatisfied toward a private feedback channel instead.
The intent is to create a publicly visible review profile that shows only positive experiences, while keeping negative feedback from appearing where prospective customers can see it.
Review gating exists on a spectrum. At one end: a formal system that asks customers "How would you rate your experience? If you said positive, click here to leave a Google review. If you said negative, click here to tell us privately." At the other end: a staff member who decides not to send a review request to a customer who seemed unhappy.
Both ends of that spectrum violate Google's review policies. The difference is that the formal version is easy to identify and enforce; the informal version is harder to detect but still prohibited.
🛠️ Action Step: Look at your current review request process. At what point do you decide whether to send a review request? If the answer is "it depends on how the customer seemed," you have a review gating problem to address.
Google's review policies explicitly prohibit review gating under the "Discourage or prohibit negative reviews" section. The specific language states that businesses should not:
"Discourage or prohibit negative reviews or selectively solicit positive reviews from customers."
The policy applies to any method of filtering customers before review requests, automated or manual, formal or informal. It also extends to third-party review management platforms and any tool or process that intercepts customer sentiment before directing them to Google's review system.
This policy exists because Google's review system is designed to be a complete, unfiltered record of customer experiences, not a curated highlight reel. When businesses gate reviews, they corrupt the signal that Google's ranking algorithm and users rely on.
💡 Pro Tip: Google's policy says "discourage OR prohibit." You don't have to block customers from leaving negative reviews to violate this policy. Simply making it easier for satisfied customers to leave reviews than dissatisfied ones, through any systematic process, crosses the line.
Example 1, The Sentiment Survey Gateway
A business sends post-service emails with a satisfaction question: "How was your experience today? Rate us 1-5." If the customer selects 4 or 5, the next screen shows a Google review link. If they select 1, 2, or 3, the next screen shows an internal feedback form. This is the most common formal review gating implementation, and it's a direct policy violation.
Example 2, The Selective Review Request
A business sends review requests only to customers who completed a post-service survey with a high satisfaction score. Customers who didn't complete the survey or scored it negatively don't receive a review request. This is gating through omission, not all customers get equal access to the review request.
Example 3, The Staff Filter
A business trains staff to send review requests only to customers who seemed happy at checkout. Staff judgment replaces a formal filter, but the outcome is the same: unsatisfied customers don't get asked for reviews. This is informal review gating.
Example 4, The Two-Track Reputation Tool
Some third-party "reputation management" tools offer features that route customers through a preliminary rating step before directing them to external review sites. If the preliminary rating is positive, the tool sends them to Google. If not, the tool captures the feedback internally. Any tool that works this way violates Google's policy, and the policy violation falls on the business using the tool, not just the tool vendor.
⚠️ Common Mistake: Believing that a review gating tool is compliant because the tool company says it is. Google's policy enforcement focuses on outcomes, not process design. If your tool produces gated reviews, you're violating the policy regardless of what the vendor told you.
The line between gating and legitimate review management isn't always obvious. Here's what is explicitly allowed:
Asking all customers for reviews, regardless of sentiment. You can have a systematic review request process that contacts every customer after a transaction. The key is that all customers receive the same invitation, not a filtered subset.
Responding to negative reviews publicly. Responding to a negative review, offering to resolve the issue, and providing contact information for direct follow-up is not review gating. You're engaging with feedback that's already public, not filtering feedback before it becomes public.
Making it easy for happy customers to review. You can send thank-you messages to satisfied customers that include a review link. As long as you're not simultaneously routing dissatisfied customers away from the same review invitation, you're not gating, you're just asking.
Timing review requests thoughtfully. Sending review requests after a completed service, successful delivery, or resolved support ticket is not gating. Asking at moments of high satisfaction is smart, as long as you're not also not-asking at moments of low satisfaction.
Encouraging more detail in reviews. Asking a reviewer to "mention the specific service you received" or "name your service provider" helps future customers and is not gating. You're shaping the content of reviews, not filtering who gets to leave them.
💡 Pro Tip: A compliant review request process is one you could describe to Google without hesitation: "We send a review request to every customer within 48 hours of service completion, regardless of what we know about their experience." If your process has any conditional step, any decision point where some customers get the request and others don't, review it carefully.
The motivation for review gating is understandable: a 3-star review from an unhappy customer is publicly visible to every potential customer who looks you up. A business with 50 4-star reviews and 1 1-star review has an average of 3.98, a single unhappy customer changes your entire public reputation.
The problem is that review gating doesn't actually solve the underlying issue. The business that gates reviews still has unhappy customers, it just doesn't hear from them publicly. The service quality problem that caused the dissatisfaction doesn't get addressed. And when review gating gets caught, the consequences are far worse than whatever negative review the business was avoiding.
Here's the deeper issue: negative reviews handled well are net positives. Prospective customers expect some negative reviews, a profile with nothing but 5-star reviews often reads as fake. A business that responds thoughtfully to a 2-star complaint, resolves the issue, and follows up publicly demonstrates something more valuable than a perfect rating: it demonstrates that problems get handled.
📊 Flento Data: Flento's analysis shows that businesses with average ratings between 4.1 and 4.6, which implies some negative reviews exist, actually convert more profile visitors to calls than businesses with 5.0 ratings. The presence of some critical reviews, combined with professional responses, builds trust that a perfect score often can't.
Review removal. Google's automated systems and manual review teams flag suspected gating patterns. If your account shows an unusual review velocity (many reviews suddenly, then nothing), an unusually high positive-to-negative ratio for your business category, or reviews that appear suspiciously uniform in content and timing, Google may remove reviews from your profile.
Profile suspension. Repeated or egregious review gating violations can result in your Google Business Profile being suspended, removed from Maps and search results. Reinstatement after a policy violation suspension requires formal appeal and documentation.
FTC enforcement risk. In the United States, the FTC's rules on endorsements and testimonials address review filtering as a deceptive practice. The FTC has taken enforcement action against companies using third-party tools that gate reviews. This risk is particularly relevant for businesses with a national or multi-location presence.
Loss of review tool access. Third-party review platforms (Google, Yelp, Trustpilot) can revoke API access or ban accounts of businesses found to be systematically filtering reviews. If your review management platform loses Google API access, your entire review management workflow breaks.
⚠️ Common Mistake: Assuming Google can't detect review gating because it's done informally or through a third-party tool. Google's detection systems look at patterns, not individual requests. A business that consistently receives reviews only from satisfied customers in a predictable pattern will trigger anomaly detection even if no individual request was provably gated.
Getting more positive reviews without gating is straightforward, it just requires consistency rather than filtering.
Ask every customer. Set up a review request that goes to every customer after service completion. Automate it if possible so it's not subject to staff judgment about who "deserves" a review request.
Ask at the right moment. The best moment to request a review is immediately after a positive touchpoint: after a successful delivery, at checkout when the customer can see the result, or after a support ticket is marked resolved. Timing matters, but timing is not gating.
Make the link frictionless. Send a direct link to your Google review page, not your homepage, not a multi-step process. Every extra click loses completions. The link format is: https://search.google.com/local/writereview?placeid=[your Google Place ID]. Find your Place ID in your GBP dashboard.
Give reviewers a framework. "Mentioning which service you received and what you found most helpful gives other customers useful information." This guidance helps reviewers write useful reviews, and is not gating.
Respond to every review. Your response to existing reviews signals to future customers that you engage with feedback. A professional, helpful response to a negative review often does more for your reputation than five new 5-star reviews.
Resolve issues before they become reviews, correctly. If a customer has a problem, resolving it directly and quickly is legitimate. Contacting a customer to resolve their issue before they decide to review you is fine. Contacting a customer to resolve their issue specifically to prevent a negative review is a gray area, the distinction is whether resolution is your primary goal or whether the review outcome is.
🔥 Quick Win: Set up an automated review request message that goes to every customer 24-48 hours after service completion. Keep it to 3 sentences: thank them for their business, mention how much reviews help your small team, and include the direct review link. No satisfaction survey, no conditional routing, just a universal invitation.
Here's a simple test for any review acquisition practice you're considering:
Would you send this review request to a customer who just gave you a 1-star service experience?
If yes, your process is compliant. You're inviting all customers equally.
If no, you're gating. Some customers get the invitation and some don't, based on their perceived sentiment.
Apply this test to every step of your review process: the initial request, the follow-up, the timing trigger, and any conditional logic in your review management tool. Any step that answers "no" to the test above is a review gating risk.
The goal isn't to get perfect reviews, it's to get an honest, representative sample of your customer experiences. A business with 4.3 stars from 200 real reviews is more trusted than a business with 4.9 stars from 40 potentially filtered ones.
What is review gating? Review gating is the practice of filtering customers based on their expected sentiment before asking them to leave a review, directing satisfied customers toward a public review platform (like Google) and dissatisfied customers toward a private feedback channel instead. The result is a publicly visible review profile that shows only positive experiences. Google explicitly prohibits review gating as a violation of its review policies.
Is review gating illegal? Review gating violates Google's review policies and can violate FTC endorsement guidelines in the United States. It isn't universally illegal in a criminal sense, but it creates significant regulatory and platform risk. The FTC has taken enforcement action against companies found to be systematically filtering reviews. Google's response is review removal, profile suspension, and API access revocation.
What's the difference between review gating and asking happy customers for reviews? The difference is whether all customers receive the same review invitation. Asking happy customers for reviews is fine, as long as you're also asking unhappy customers (or at minimum, not specifically excluding them). If you ask every customer for a review regardless of their perceived satisfaction, that's compliant. If you only ask customers who seem satisfied, that's gating.
Can I ask a customer to change their negative review if I've resolved their issue? You can contact a customer who left a negative review, let them know you've resolved the issue, and note that you'd appreciate them updating their review if their experience has changed. You cannot offer incentives for a review change, pressure a customer to update or remove their review, or make resolution contingent on a review change. Organic review updates from genuinely resolved situations are fine, solicited review modifications in exchange for something are not.
What happens if Google catches you review gating? Google's responses range from removing suspected gated reviews from your profile to suspending your Google Business Profile entirely. The severity depends on the scale and intentionality of the gating. An automated system that's systematically routing customers is treated more seriously than an isolated incident. Reinstating a suspended profile after a policy violation requires formal appeal and documentation, and there's no guarantee of approval.
Are there review management tools that make review gating easy to do accidentally? Yes. Some reputation management platforms offer "sentiment-based routing" features that send customers through a preliminary rating step before directing them to external review sites. These features are designed for review gating, the tool just doesn't call it that. Before using any review management tool, verify that its routing logic sends all customers to the same review invitation, not just customers who rate positively in a preliminary step. Check the tool's terms against Google's review policies directly.
Does Flento support review gating? No. Flento's Google Review Management Software sends review requests to customers after service completion without sentiment filtering. All customers receive the same invitation. Review response templates and timing optimization are available, but no conditional routing based on expected sentiment.
