What exactly counts as review gating?
Gating is not "asking for reviews." Asking is fine and encouraged. Gating is the filter you put in front of the ask. The classic version: a text or email asks "How was your service, 1 to 5?" Four and five stars get the Google link. One through three get a form that goes to your office instead of your public profile. The happy customers post. The unhappy ones get quietly intercepted.
That routing is the problem. Google's policy prohibits "discouraging or prohibiting negative reviews, or selectively soliciting positive reviews from customers." The word that matters is selectively. If your process treats a satisfied customer differently from an unsatisfied one at the point of the ask, you are gating.
Some gating is obvious. A lot of it is baked into review software the contractor never questioned. Here is what crosses the line versus what stays clean:
| This is gating (banned) | This is fine |
|---|---|
| Star-rating survey that branches happy to Google, unhappy to a private form | Same review link sent to every customer regardless of how the job went |
| "If you were happy, leave us a Google review" (conditional on sentiment) | "We'd appreciate an honest review of your experience" |
| Only texting the customers you know loved the work | Texting a review request after every completed job |
| Offering a discount in exchange for a 5-star review | Making it easy to review with a one-tap link |
The tell is always the same. Does a customer's likely opinion change what you send them, or when? If yes, it is gating.
Why did Google and the FTC crack down on it?
Two separate authorities now govern this, and contractors need to understand both because they carry different consequences.
Google has prohibited gating in its Maps and prohibited content policies for years. Google's enforcement is platform-level: it can remove individual reviews it believes were solicited improperly, remove your review-generating content, or in repeat cases suspend the Business Profile. Google rarely explains a removal, so a contractor whose reviews start disappearing often has no idea a gating tool is the cause.
The FTC is the bigger change. In August 2024 the Commission finalized its Rule on the Use of Consumer Reviews and Testimonials, effective October 21, 2024. It bans fake reviews, undisclosed insider reviews, buying positive reviews, and, directly relevant here, review suppression: using unfounded legal threats, intimidation, or false claims to prevent or remove honest negative reviews. Gating that intercepts unhappy customers so they never post publicly falls squarely in the suppression bucket. The FTC can seek civil penalties up to $53,088 per violation, and each intercepted review can count as a separate violation.
The reason both moved is the same. Reviews stopped being a vanity metric and became infrastructure. They are a ranking input for the Google map pack, and they are a citation source that AI answer engines quote when a homeowner asks "who's the best HVAC company near me." When the star average is manufactured, every one of those systems lies to the consumer. Regulators and platforms both decided that was worth policing.
What can a contractor still legally do?
Plenty. The ban is narrow. It targets sentiment-based filtering, not the act of requesting reviews. Everything below is allowed and, done consistently, out-earns any gated funnel because it produces more total reviews.
- Ask every single customer. Same request, every completed job, no pre-screening. Volume is legal and it is what actually moves your star average and your map-pack position.
- Send a direct review link. A one-tap link to your Google review form removes friction. Making it easy is not gating. Deciding who gets the link based on mood is.
- Follow up. One or two reminders to a customer who has not responded is standard and permitted. Follow up with everyone, not just the pleased ones.
- Ask at the right moment. Time the request to job completion, the final walkthrough, the paid invoice. Timing is neutral. It applies to happy and unhappy customers alike.
- Respond to reviews, including bad ones. A calm, specific owner response to a 1-star is your strongest reputation move. It signals to the next reader, and to Google, that you engage.
- Route service problems separately, without blocking the review. You can tell every customer "call the office if anything's wrong" AND send everyone the review link. The rule breaks only when the service channel replaces the review link for unhappy customers.
That last point is where most contractors trip. Caring about problems is good. Using "let us fix it first" as a gate that steers the review away from Google is not. Offer both paths to everyone.
How do I know if my current review tool is gating?
Many contractors are gating without knowing it because a piece of software does it automatically. If you bought a review-request tool, run it through these checks before you send another request.
Open the actual message flow a customer sees. Send yourself a test request and click through as if you were unhappy. Watch where a low rating sends you.
- Does it ask for a star rating BEFORE showing the Google link? A mid-funnel rating gate is the single most common gating mechanic. If the customer rates first and the destination changes based on that rating, it is gating.
- Where does a 1, 2, or 3 go? If low ratings land on a private feedback form and only high ratings reach Google, that is textbook interception.
- Is the copy conditional? Language like "if you had a great experience, leave a review" is a soft gate. It solicits selectively.
- Are you choosing who gets asked? Manual gating counts too. Cherry-picking the customers you request from is the same violation without the software.
If any answer is yes, the fix is straightforward: rip out the branching. Send one message, to everyone, that goes straight to your Google review link. No survey in front of it. That is the entire correction, and it is usually a settings change or a switch to a compliant flow, not a rebuild.
This is the layer we handle inside reputation management: the review-request flow, the monitoring that catches removals, and the response drafting that turns a bad review into a signal you handle problems. We run it as one system per trade so the mechanics stay compliant while the volume climbs.
What happens if you get caught gating?
The consequences stack, and they arrive at the worst possible time: after you have built a rating you now depend on.
On the Google side, the most common outcome is silent. Reviews you generated through a gated tool start disappearing, sometimes in batches. Your count drops, your average shifts, and Google sends no notice. In harder cases the Business Profile gets suspended, which erases your presence from Maps and the local pack until you appeal. For a contractor whose phone rings off the map pack, a suspension is a direct hit to booked jobs.
On the FTC side, the exposure is financial. Civil penalties reach up to $53,088 per violation, and the Commission has signaled it treats each suppressed review as a separate count. The realistic risk for a small contractor is not a random federal audit. It is a competitor complaint, a disgruntled ex-employee, or a customer who realized their negative feedback never posted. Any of those can trigger scrutiny.
There is a quieter cost too. A gated rating is fragile. It looks great until the gate comes off or a wave of real feedback lands, and then it corrects downward fast, right when you have the fewest reviews to cushion it. A rating built by asking everyone is durable. It reflects reality, so reality never surprises it.
The math favors compliance anyway. Gating suppresses a slice of your feedback to protect the average. Asking everyone produces far more total reviews, and volume plus recency is what the map pack and AI answer engines actually reward. Playing clean is not just safer. It ranks better.
How to switch from gating to a compliant review system
If you have been gating, the transition is a weekend of work, not a quarter. Here is the order of operations.
- Turn off the sentiment gate first. Whatever branches your flow by star rating, disable it today. Every future request goes straight to the Google link with no rating survey in front.
- Write one honest ask. Same message to every customer: a short thank-you, a one-tap review link, and a line inviting honest feedback. "Honest" over "positive" is the whole difference.
- Set the trigger, not the target. Fire the request on a neutral event every job hits: invoice paid, final walkthrough done. The event decides who gets asked, not the customer's mood.
- Add a real service path, in parallel. Give everyone your office number for problems too. Both channels, every customer. That keeps you caring about issues without gating the review.
- Build a response habit. Reply to reviews, especially the negative ones, within a few days. This is your public proof you handle problems, and it does more for the next reader than a suppressed 1-star ever could.
- Monitor for removals. Watch your review count over the first month. If gated reviews get purged, your compliant volume needs to be climbing to cover the gap. That is exactly why you start the new flow immediately, not after cleanup.
The whole shift is one principle: stop deciding who deserves to review you. Ask everyone, the same way, and let the work speak. Contractors who do this end up with more reviews, a more believable rating, and no exposure on either the Google or the FTC side.