Two changes landed on Google reviews this year that most local businesses have not noticed. One is helpful. The other quietly made a very common review-request habit into a policy violation.
\n\nEvery contractor has had this conversation. A customer says they left a five-star review. You look at your profile. It is not there. Historically Google gave no explanation to anybody — not to you, not to the customer.
\n\nGoogle now tells the reviewer when their review was not published, which policy it fell foul of, and offers them a route to appeal if they think the decision was wrong.
\n\nThat matters more than it sounds, because review recency is one of the strongest signals on a profile. A review that never publishes is not a neutral event. It is a lost ranking signal that you paid for in labour, and until now you had no way of knowing it had even happened. Now the customer can tell you, and can push back.
\n\nIn April 2026, Google added clauses to its Maps rating manipulation policy. Two of them are worth reading slowly, because they prohibit things that are extremely common:
\n\nLook at the review-request SMS your team actually sends. If it says \"leave us a 5-star review\" or \"please mention the kitchen remodel,\" it is now on the wrong side of the line. That phrasing is in a huge number of templates, including ones handed out by software vendors.
\n\nThis is the one I want to be blunt about, because we see it pitched constantly in this industry, including in partner materials from established local SEO suppliers.
\n\nReview gating is the flow where you first ask the customer how their experience was, and only send the happy ones to Google while the unhappy ones get routed to a private feedback form. It is presented as reputation management. It is prohibited by Google, and in the US it also runs into FTC rules on fake and misleading reviews, which since 2024 carry civil penalties.
\n\nIf a vendor demo shows you a \"happy path / unhappy path\" split before the Google link, that is review gating with better branding. Decline it. The rankings you would gain are not worth a warning label on your profile telling customers that fake reviews were removed.
\n\nShort, neutral, no quota, no script for the customer, no filtering:
\n\nThe uncomfortable truth is that the compliant version converts slightly worse per send. It also does not put a fake-review warning on your listing, which is a cost that never shows up in the vendor demo.
\n\nMost businesses did not build their review-request flow in a single sitting. It evolved — a software vendor provided a default template, a manager added \"5-star\" somewhere, someone else added a keyword for a city they wanted to rank in. By the time the policy changed, the non-compliant phrasing had been baked in for months. Here is a methodical way to find and fix it.
\n\nThere are businesses for which the review-count problem is not the immediate priority, and it would be dishonest to pretend otherwise.
\n\nIf your Google Business Profile has fewer than thirty or forty reviews and you are in a market where competitors have two hundred or more, the gap in volume is harming your visibility regardless of how clean your request process is. Getting compliant and getting more reviews are not in conflict — a clean, consistent ask sent to every job will close that gap over time — but if you are starting from near zero, the first job is getting the volume up at all. Fix the template, then focus on the send rate.
\n\nSimilarly, if your profile has other structural problems — no services section, no posts in recent months, no booking link, a business description that does nothing — reviews are one signal among many. In a sample of 1,440 Google Business Profiles we collected across the top-10 results in 29 US cities and 5 trades in May and July 2026, 1,426 of those profiles had no services section populated at all. Across those same profiles, every single one had gone more than 90 days without a post, and 93 percent had no Q&A entries. A business with 900 reviews and none of those things filled in is still leaving signals on the table. Reviews matter. They are not the whole picture.
\n\nYou can reference your overall star rating in advertising or on your website when you are reporting a fact — \"we have a 4.8-star average\" is a factual statement, not a content direction. What the policy prohibits is telling a customer what rating to leave when you make the request. The direction flows to the customer; that is the line.
\n\nTell them honestly that you cannot suggest content, and that whatever they felt was most useful to them is what future customers would want to read. That answer is both compliant and, in practice, tends to produce more detailed reviews than a script would have anyway.
\n\nYes. The policy applies to the content of the request, not the channel. An in-person ask that does not name a star count or suggest specific phrasing is compliant. An in-person ask that hands the customer a card saying \"please leave a 5-star review mentioning our drain cleaning service\" is not.
\n\nGoogle can remove reviews it identifies as policy violations, and it can apply a notice to the profile visible to anyone searching for your business. That notice is designed to signal that the profile's reviews may not be reliable. There is no published threshold for when enforcement triggers, which is a reason to treat compliance as a floor rather than an optimization.
\n\nAsk them to show you, in the actual product, the exact message a customer receives and the exact path they are routed through. If any step asks the customer how satisfied they were before showing the Google link, that is a gating flow. If any step includes a star count or a phrase suggestion in the message to the customer, that is a content direction. You do not need their legal opinion. You need to see the screen.
\n\nRewrite your review request so it stays inside the rules.
\n \n