Reputation 4 min read

Can you block bad Google reviews? No — and the real problem is how you ask for good ones

There is no way to block or filter negative Google reviews. But many businesses unknowingly run review gating — a practice that violates Google's policies and a 2024 FTC rule — and it quietly caps their review growth.

A business owner asked us recently whether bad Google reviews can be blocked before they appear. It is one of the most common questions in reputation management, and the honest answer disappoints people for about a minute — until they hear what we found in their own review system.

The short answer: no

Google provides no mechanism to block, pre-approve, filter, or hide reviews by star rating. None. The only path for removing a review is reporting it for a policy violation — spam, fake engagement, a conflict of interest, off-topic content, or harassment. A genuine one-star review from a real customer, however unfair it feels, does not qualify.

Any vendor selling "bad review blocking" or "review protection" is describing one of two things: reporting reviews and hoping, or a practice called review gating. The first is legitimate but limited. The second can get you penalized.

What review gating is, and why you might be doing it by accident

Review gating means checking how happy a customer is first, and only inviting the happy ones to leave a public review. The classic setup looks completely innocent:

  1. Send every customer a satisfaction survey.
  2. If they score high — say, 9 or 10 out of 10 — send them the Google review link.
  3. If they score low, route them to a private feedback form instead.

It feels like smart customer service. It is also explicitly against Google's review policies, and since late 2024 it falls under a Federal Trade Commission rule covering consumer reviews in the United States. The logic is simple: a review profile built only from pre-screened happy customers is not a genuine picture, and both Google and the FTC treat it that way.

The businesses running this pattern almost never chose it deliberately. It usually arrives bundled inside a "reputation tool" someone signed up for years ago, set once, and forgot.

The hidden cost is bigger than the compliance risk

Here is what surprised the owner who asked us: gating was not just a rules problem. It was the reason their review count had stalled.

A survey-first flow means only customers who complete the survey ever see the review invitation. Survey completion rates are typically low — often ten to twenty percent. Gate on top of that (only the 10-out-of-10 responders get the link), and you have quietly filtered away the vast majority of customers who would have happily left a five-star review if anyone had simply asked them.

Their competitors were not gating. They asked everyone. That is the entire mystery of "why do they have three hundred reviews and we have forty" for a lot of businesses.

The compliant setup — which is also the one that grows reviews

The fix keeps everything the survey was trying to achieve, without the gate:

  • Ask every customer for a review, at the right moment — when the job is finished, the order is delivered, the case is closed. Route the request to the correct location's profile if you have more than one.
  • Keep the satisfaction survey as a separate, internal tool. It is your early-warning system, not a gate. Run it in parallel.
  • When someone signals they are unhappy, a human calls them — before anything else happens. That instinct is right and it stays. You are allowed to do service recovery; you are not allowed to condition the public review invitation on the score.
  • Respond to every review, positive and negative, in your own voice, without confirming private details about the customer.

One sentence to remember: ask everyone, respond to everything, never condition the ask on the score.

How Alfie handles this

This is exactly the kind of always-on, easy-to-get-wrong routine our systems are built for. When a job closes in your existing tools, Alfie sends the review request to that customer, pointed at the right location, on a schedule that follows up politely if there is no response. The satisfaction survey runs separately, and a low score raises a hand to a human immediately. Replies to incoming reviews are drafted in your voice — and anything negative always waits for a person.

No gating, no policy exposure, and the review count grows because every happy customer finally gets asked.

If your review system checks satisfaction before showing the review link, it is worth fixing this week — for the compliance reason and for the growth one. Tell us what your current flow looks like: hello@hirealfie.com

Have a question about implementing this in your business?

We can walk you through exact operational automations for your team.

Book a 30-minute call