Google's 2026 Review Policy Update: What Every Local Business Needs to Know

Google quietly banned several review-collection practices that used to be standard advice. If your process involves screening customers before asking for a review, this affects you directly, and the enforcement isn't theoretical.

The Bloom team · July 2026

If your business collects reviews at all, you need to know about this. Google updated its Prohibited and Restricted Content policy for Google Maps in 2026, and it specifically targets practices that a huge number of local businesses, and a lot of review software companies, have been recommending as best practice for years.

This isn't a minor wording tweak. Google's own policy is explicit: merchants must not "discourage or prohibit negative reviews, or selectively solicit positive reviews from customers." That single sentence rules out a lot of what's been considered smart, standard playbook advice, and it's being actively enforced with AI-driven detection rather than sitting quietly on a policy page nobody reads.

Here's exactly what changed, why the enforcement mechanism makes this different from past policy updates, what a compliant review request process actually looks like now, and how to audit your own current process against it.

What Changed

Google's current Maps User Generated Content Policy prohibits merchants from doing several things that were common practice as recently as last year:

Review gating. This is the practice of asking customers how their experience went before deciding whether to send them a Google review link, routing happy customers to Google and unhappy ones somewhere private instead. Google's policy directly prohibits this: businesses cannot discourage negative reviews or selectively solicit only positive ones. This is the single most common violation, because it was widely taught as a growth hack for years before the crackdown.

Incentivizing reviews. Offering a discount, gift card, free product, or any other reward in exchange for a review, a review edit, or a review removal is against policy. This applies even if the incentive is offered for an "honest" review rather than explicitly a positive one, and it applies to trying to buy back a negative review with a refund or freebie in exchange for taking it down. There's no dollar threshold; a five dollar coupon triggers the same violation as a much larger incentive.

On-site pressure. Asking customers to leave a review while they're still on your premises, or setting up a kiosk or shared tablet for review collection, is now explicitly restricted. The concern here is coercion, even gentle, well-intentioned coercion, since a customer standing in front of staff feels pressure to comply that a customer reviewing later at home doesn't.

Scripted content requests. Asking customers to mention a specific staff member's name, or directing employees to hit review quotas, is prohibited. Google's systems flag reviews that repeat the same staff name across many reviews as an unnatural pattern, since organic reviews rarely converge on the same specific phrasing this consistently.

Undisclosed insider reviews. Reviews from current or former employees, or anyone with a conflict of interest, must disclose that relationship. This overlaps with Competition Act requirements in Canada, which we cover in how to get employees to help with reviews without breaking the rules.

Why the Enforcement Mechanism Matters More Than the Wording

Policy updates happen constantly and most get ignored because enforcement is inconsistent. This one is different because of how it's being detected. Google's moderation combines automated pattern-matching with human review, and the automated layer scans every review on submission for signals like:

Unusual review velocity, a sudden cluster of reviews arriving in a short window, especially if they're disproportionately positive
Sentiment-timed patterns, reviews that consistently arrive shortly after a specific type of interaction (a checkout, a completed job) in a way that suggests a triggered request rather than organic timing
Repeated phrasing or names, the same staff member's name, or oddly similar sentence structures, appearing across reviews from different accounts
Device and account signals, reviews posted from accounts with little history, or from the same general location and time window as many other new reviews for the same business

None of this requires Google to catch you in the act. It requires your review pattern to statistically resemble the patterns Google has learned to associate with gated or incentivized collection, and businesses using any of the prohibited approaches tend to produce exactly that kind of pattern, even unintentionally.

The practical consequence: enforcement can happen in bulk, removing a large share of a business's reviews in a single sweep, and it can happen without a specific warning tied to a specific review. A business owner who built 150 reviews over a year through a gated or incentivized process can wake up to a fraction of that number with no individualized explanation of which reviews were removed or why.

What's Still Allowed (and Actually Works)

Google's policy is clear that asking for reviews is fine and encouraged. What matters is how you ask:

Ask every customer the same way, regardless of how the interaction went. No pre-survey filtering based on predicted sentiment, and no version of the request that changes depending on an earlier answer.
Keep the ask neutral. "We'd appreciate your honest feedback" rather than anything that nudges toward a specific rating or specific content.
No incentives of any kind, direct or implied, including a "thank you" gift that's promised or expected in connection with reviewing.
Send the request off-premises, after the visit or job is complete, not while the customer is standing in front of you or seated at a kiosk.
Give every customer a direct link to your Google review page, not a filtered path that depends on how they answered a prior question.

You can still offer customers a way to flag problems privately. That's good customer service, and Google's policy doesn't restrict it, but it has to sit alongside the public review option, not replace it for anyone. The distinction that matters to Google's enforcement systems isn't whether a private channel exists, it's whether the public review path is equally available and equally visible to every customer regardless of sentiment.

For exact request language you can use immediately, see the compliant way to ask for Google reviews in 2026, which has ready-to-use templates that follow these rules.

It's Not Just Google

If your business also collects reviews on Yelp, the same underlying principle applies there too, and Yelp has actually enforced against review solicitation for longer than Google has. Yelp's long-standing "Don't Ask" policy treats any prompted review as suspect regardless of intent, and its filtering algorithm reportedly filters out a substantial share of submitted reviews it judges to be solicited, incentivized, or otherwise non-organic. Yelp explicitly names "review gating" as a prohibited practice in its own guidelines: using a survey to route only satisfied customers to a public review while suppressing criticism through private channels. If you're building one review-collection process, it's worth designing it to satisfy the stricter of the two platforms' rules rather than assuming Google-compliant automatically means Yelp-compliant. We cover the platform-by-platform differences in Google reviews vs. Yelp vs. Facebook.

Auditing Your Current Process

Run your existing review request process through this checklist:

Does every customer receive the same request, regardless of how the interaction went? If there's any branching logic based on a satisfaction question, that's the core gating pattern.
Is there any incentive, direct or implied, connected to leaving a review? Include anything that could read as a thank-you gift tied to review activity.
Are staff directed to ask for reviews mentioning their own name, or to hit a personal quota? Both are now explicit violations.
Is the request sent after the customer has left, rather than while they're still present?
Do employees or family members ever review the business without disclosing the relationship?

If your process fails any of these, the fix isn't complicated in principle, though it may require an actual change to how requests are built, not just a copy edit. The core adjustment is always the same: send the identical, unconditional request to everyone, every time.

What This Means If You're Already Collecting Reviews

The businesses with the most exposure right now are the ones who built review velocity through gating or incentives without realizing the practice had shifted from "smart marketing" to "policy violation." If that describes your current process, it's worth treating this as a near-term priority rather than something to fix eventually, since the risk isn't a warning letter, it's the reviews themselves disappearing in a sweep with no notice.

The businesses with the least exposure are the ones who've always sent a plain, unconditional request to every customer. That approach felt less "optimized" for years, but it's the only version that was never actually at risk, and it's the version that builds a review base durable enough that a single enforcement sweep somewhere else in the industry doesn't touch it. See how to get more Google reviews for your business for the mechanics of doing this consistently.

Frequently Asked Questions

Is review gating actually against Google's rules, or is this just cautious advice? It's directly against Google's official Maps User Generated Content Policy, which states merchants may not discourage negative reviews or selectively solicit positive ones from customers. This isn't a gray-area interpretation, it's stated policy, and it applies regardless of intent.

Can I still offer a general "thank you" gift to customers who leave any review?

This is risky. If the gift is promised or expected in connection with reviewing, Google treats it as an incentive regardless of what you call it. The safer approach is thanking customers after they've reviewed, with no prior promise connecting the two.

Does this affect reviews I've already collected? Potentially. Google's enforcement can retroactively remove reviews that match prohibited patterns, even if they were collected before you knew about the policy. It's worth auditing your process going forward rather than trying to predict which specific past reviews might be affected.

What happens if my Business Profile gets flagged? Consequences range from individual review removal to profile-wide restrictions on features, and in repeated cases, account suspension. Google generally doesn't offer a detailed explanation for each individual removal.

Is there a compliant way to still route unhappy customers somewhere useful? Yes. Offer a private feedback or support channel to every customer alongside the public review link, not instead of it. The difference that matters to Google is whether the public review path is available to everyone equally, not whether a private option also exists.

Does responding to a review after it's posted create any policy risk? No. Responding publicly to reviews, positive or negative, is unrelated to the collection-side rules covered here and is explicitly encouraged by Google. See how to respond to negative Google reviews for guidance on that side of the process.