Google's April 2026 Review Policy Update: What Changed and How to Keep Your Reviews

Something quiet but important happened to your Google reviews in late April 2026. On April 16, Google posted a blog explaining a new wave of review protections on Maps. The next day, the Maps user-generated content policy gained two short new clauses under the Rating Manipulation section.

In the days that followed, monitoring tools and small-business owners started watching review counts drop. Sometimes by a few reviews, sometimes by dozens, often without any notification at all.

The reviews that got pulled were not just obviously fake ones. They were short five-star reviews that named an employee, clusters of reviews that landed within hours of each other from the same general area, and templates that agencies had been running for years. The policy did not arrive out of nowhere, but the new text made several gray-area habits unambiguously off-limits, and the enforcement caught up the same week.

Quick Answer: Google updated the Maps review policy on April 16 to 17, 2026 with two new prohibitions: directing staff to hit review quotas, and directing staff to solicit reviews that include specific content like an employee's name. The update also reinforced existing rules against on-premises pressure, review kiosks, and review gating.

Google's systems blocked or removed 292 million policy-violating reviews in 2025, and the same systems are now applying the new language. The compliant playbook is a single neutral request to every customer, sent after the visit, paced as a slow drip. For the full evergreen reference, see our guide to Google review policies.

In this guide, you will learn:

• What Google actually changed in April 2026, with the exact policy clauses
• How the 292 million removed reviews number frames the enforcement risk
• Which common collection habits are now policy violations, including ones agencies have been running for years
• The safe, slow-drip way to ask for reviews that survives the new enforcement
• What to do right now if your review count has already dropped
• How to think about the update if you manage reviews for clients

What Google Actually Changed in April 2026

The April 2026 update was two events on two days, and the difference matters because the policy clauses arrived a day after the public blog post and got noticed by far fewer people.

On April 16, 2026, Google's official Maps blog published "New ways we're protecting businesses on Maps," authored by Bibek Samantaray, Group Product Manager for User Generated Content. The post laid out three new protections rolling into Google Maps. The first uses Gemini to catch review extortion scams before reviews go live. The second is faster filtering of unhelpful place edits. The third is a proactive email alert to verified Business Profile owners when something happens to the listing. The post also published Google's 2025 Trust and Safety numbers, and that is where the headline figure came from: "Our advanced systems and expert analysts blocked or removed over 292 million policy-violating reviews while publishing more than 1 billion helpful reviews" in 2025. The post stated explicitly that "The latest protections help detect fake reviews faster and block suspicious edits before they appear."

On April 17, 2026, the Maps user-generated content policy page itself was edited. Two new bullet points appeared under the Rating Manipulation section, both of which directly address what merchants are allowed to ask their own staff to do.

The first new clause prohibits merchants requesting that staff solicit a certain number of reviews. This is the policy-language version of an employee review quota. Any structure where a salesperson, technician, server, or front-desk associate is asked to bring in a specific count of reviews per week or per month falls inside this clause now.

The second new clause prohibits merchants requesting that staff solicit reviews that include specific content, including content that identifies a staff member. This one is broader than it sounds. It is the policy-language version of "tell customers to mention you by name in their review," but it also covers asking customers to mention a specific service, package, or keyword. The content of the review must come from the customer, not from a script.

Both new clauses sit under Rating Manipulation, which is the section of the Maps policy that explicitly governs "content showing unusual volumes or patterns of contributions that indicate efforts to manipulate a place's rating." The placement is deliberate. Google is saying that staff-directed solicitation is a form of rating manipulation, in the same family of violations as buying reviews and running review exchanges.

The longer-standing language did not change. The Maps policy still says that "contributions to Google Maps should reflect a genuine experience at a place or business," and that incentivized content, conflict-of-interest content, and review gating all violate policy. What changed is that the gray-area practices many agencies were quietly running now sit on the prohibited side of an explicit line.

Industry coverage of the change appeared almost immediately. PPC Land documented the new clauses on April 17, framing the update as Google closing a gap that had let staff-directed solicitation run for years. Search Engine Roundtable confirmed the policy change the same week.

The 292 Million Number and Why It Frames the Risk

The headline figure from Google's April 16 blog post is doing a lot of work, and it pays to understand what it actually means before deciding how worried to be about your own reviews.

Google said its systems blocked or removed over 292 million policy-violating reviews on Maps in 2025. That is up from 240 million the year prior, an increase of roughly 21 percent. The Trust and Safety report also said Google blocked 79 million inaccurate or unverified edits to Business Profiles, placed posting restrictions on more than 782,000 policy-violating accounts, and removed over 13 million fake Business Profiles. About one in five review attempts on Maps in 2025, roughly 22 percent of all review activity, was classified as policy-violating.

The piece of that figure most relevant to legitimate small businesses is that the enforcement is no longer manual or rare. Gemini-powered moderation reviews patterns across the whole platform continuously, and the system has gotten dramatically more aggressive over the last twelve months. Search Engine Land reported review deletion rates surged by 600 percent between January and July 2025 after Google integrated Gemini into the moderation stack. That climb has continued.

For a single business, the practical implication is simple. The classifier does not know that your review collection process is well-intentioned. It scores patterns. A cluster of short five-star reviews posted within the same hour from the same neighborhood, a wave of reviews mentioning the same employee name, a sudden spike that does not look like the listing's normal weekly rhythm, all read to the system as the same shape as obvious manipulation. The legitimate reviews that get caught in the sweep are the cost of running collection tactics that produce a shape the classifier flags.

Once a review is removed, it almost never comes back without a specific, well-documented appeal. We covered that recovery process in detail in our guide on why Google reviews disappear and our walkthrough on how to track removed Google reviews. Catching the drop quickly is the first move. Changing the collection process so the next batch does not look like the last batch is the second.

The Collection Habits That Are Now Policy Violations

Some of what the April 2026 update made explicit was already a violation under existing policy language. The difference now is that the practices have specific names attached to them in the policy and the moderation systems are actively scanning for them.

Here is the quick reference, with the detail on each one below.

Asking Customers to Name an Employee in Their Review

This is the practice most directly addressed by the new April 17 clause. Scripts that tell customers to "mention your stylist by name" or "let them know who took care of you today" produce reviews that follow a predictable pattern, often a short five-star review with the employee's first name in the second sentence. The classifier sees the pattern across a profile and across the platform.

Why Google flags it: The new policy text explicitly prohibits directing staff to solicit reviews that include specific content, including content that identifies a staff member. The pattern is the violation.

What to do instead: Let customers mention staff on their own if they want to. A genuine review that says "Sarah at the front desk was great" is fine. A row of fifteen reviews that each mention Sarah within the same two weeks is a pattern Google reads as directed.

Tying Employee Bonuses to Review Counts

This was always shaky under the incentivized-content language. The April 2026 update makes it explicit by prohibiting merchants from directing staff to solicit a specific number of reviews. A bonus structure that pays an employee per review effectively makes the employee the incentivized party, which is structurally the same shape of violation as paying the customer.

Why Google flags it: Quotas push staff toward the easiest reviews to collect, which usually means on-premises requests, scripts that mention the employee's name, and clusters of reviews posted within a single shift. Every one of those is now a pattern the classifier scores.

What to do instead: Recognize team review performance privately. Internal dashboards, monthly one-on-ones, and team-level acknowledgment are all fine. Per-review payouts and public leaderboards are the structures that have been getting reviews removed.

Asking for Reviews While the Customer Is Still on the Premises

The April 2026 update reinforced longstanding language about not pressuring customers to leave reviews while still on the premises. The classifier has gotten much better at spotting reviews posted from inside or immediately outside a business location, often from the same wifi network or the same general GPS area.

Why Google flags it: A review submitted from inside the business reads as coerced even when it is not. Multiple reviews submitted from the same network during the same shift compound the signal. Industry coverage of the update noted that the new enforcement uses GPS, IP, and device fingerprinting to score on-premises patterns.

What to do instead: Send the request after the visit. A short follow-up email or SMS later that day, the next morning, or two days out lands far better and looks far cleaner to the classifier. Mention to the customer in person that they will get a quick follow-up, but do not put the device in their hands at the counter.

Review Kiosks and Shared Tablets at Reception

Closely related. A single tablet or kiosk used by every customer who walks in produces reviews that all originate from the same device, same IP, and same physical location. The pattern is unmistakable to the classifier, and it has been one of the visible drivers of the post-update removals.

Why Google flags it: Same-device, same-network submissions over a short window are the textbook pattern of orchestrated review collection. Even if every individual review is from a real customer expressing a real opinion, the fingerprint is the violation.

What to do instead: Push the request to the customer's own phone, ideally after they have left. A QR code linked to your review URL is fine when scanned later from the customer's device on their own network, not when scanned from a fixed device at the counter. See our guide to Google review links and QR codes for the compliant version.

Review Gating

Review gating is the practice of routing customers to an internal feedback form first, then sending only the happy ones to Google. The Maps policy has prohibited this since 2018 with the language that businesses must not "discourage or prohibit negative reviews or selectively solicit positive reviews." The April 2026 update did not introduce this rule, it just amplified it.

Why Google flags it: A profile with an unusually steady stream of four and five-star reviews, no negative content, and a measurable bias in incoming sentiment looks artificially curated. Sterling Sky has documented businesses losing hundreds of reviews over enforcement of this rule alone.

What to do instead: Send the exact same review request to every customer, regardless of how the experience appeared to go. If a customer wants to leave a negative review, the system has to allow it. Handling those negative reviews well is the actual job, and our guide on responding to negative Google reviews walks through that side of the work.

AI-Generated or Templated Review Text

This one is not new in the April 2026 update, but the same Gemini-based moderation that is enforcing the new clauses is also far better at detecting reviews that read like they came out of an AI template. Reviews that share suspicious phrase overlap with other reviews on the platform, or that show the linguistic fingerprints of a single generator, get removed in batches.

Why Google flags it: AI-written reviews are not "genuine experiences" in the policy sense, no matter how positive the customer felt. They also tend to cluster around the same handful of generic phrases, which is exactly what the classifier is scoring for.

What to do instead: Never write reviews for customers. Never offer "we will write the review for you, just approve it." The compliant version is asking the customer to leave their own words. If they need a prompt, a single neutral question like "what would you tell a friend about your visit?" is fine. AI is genuinely useful on the response side, where it helps the business write back to reviews quickly, but it has no compliant role on the writing-the-review side.

Sudden Spikes That Look Like Manipulation

The Rating Manipulation section of the policy specifically calls out "content showing unusual volumes or patterns of contributions that indicate efforts to manipulate a place's rating." That is the policy-language definition of a spike-and-drop pattern: a business that has been averaging two reviews a month suddenly gets twelve in three days, then goes quiet again.

Why Google flags it: A real business's review velocity is roughly steady, with seasonal variation. A spike that does not match the baseline reads as orchestrated. The Gemini-based classifier scores the velocity pattern across the profile.

What to do instead: Pace the requests. A slow drip across weeks looks like a healthy business with steady customer flow. A batch send to two hundred customers on the same Tuesday looks like a campaign. The compliance version of "bigger" is a longer drip, not a denser one.

The Safe Way to Ask for Reviews After April 2026

After everything above, the compliant playbook is actually short. The hardest part is giving up the tactics that produced the fastest visible review growth.

One identical neutral request, sent to every customer

The single most important shift is symmetry. The exact same request goes to every customer, no matter how the visit went. The same wording, the same channel, the same timing relative to the visit, the same link. The request does not steer toward a rating, does not ask for any specific content, and does not mention any specific employee. It is a neutral invitation to leave honest feedback if the customer feels like it.

A clean template looks like this:

"Hi [Name], thanks for choosing [Business]. If you have a moment, we would love to hear about your visit. You can leave us a quick review here: [direct review link]. Either way, thank you for stopping in."

That is it. No rating prompt, no employee name, no service detail. The link goes to your standard Google review URL. Every customer gets the same one.

Send it after the customer has left

The request lands in the customer's inbox or SMS thread after they are off the premises. A short delay, anywhere from a few hours to a day or two, is ideal. The customer responds on their own device, on their own network, on their own time. The review carries the fingerprint of a real customer experience, not an on-premises capture.

Drip slowly across the week, not all at once

If you have a backlog of customers to ask, do not batch the request. Spread it across days. A small business sending fifteen requests over a week looks healthy. The same fifteen requests sent on a single Tuesday afternoon looks like a campaign and produces a velocity spike the classifier will notice. Volume is fine. Density is the problem.

Use multiple channels, but the same neutral wording

Email and SMS are both fine. The two channels reach different customers and produce a more natural mix of review sources. The wording stays identical across channels. Do not write a "fun" SMS version and a "formal" email version. Identical request, two delivery methods, same neutral tone.

Ask close to the experience, but never on it

The window between the visit and the request matters. Too soon, and the request reads as on-premises pressure. Too late, and the customer has moved on and the review never gets written. Most service businesses land in a comfortable window between four hours and two days after the visit, depending on the category. A restaurant might ask the next morning. A service-call business might ask later that day. A medical practice might ask two days out. The exact timing is less important than the principle: after, but not much after.

Open-ended phrasing only

The request should ask for honest feedback in general terms. It must not prompt for a rating, a star count, a service mention, or an employee name. The customer's review is whatever the customer wants to write. The job of the request is to invite the review, not to shape it.

For a fuller walkthrough of the compliant collection process, see our guide on how to ask for Google reviews and our broader piece on how to get more Google reviews.

What to Do If Reviews Have Already Been Removed

If you are reading this after watching your review count drop in late April or early May 2026, the order of operations matters more than the panic. The faster you document what disappeared, the better the recovery odds.

Confirm it is not a display glitch

Google has occasional display issues where reviews vanish from one view but remain in others. Check your listing in an incognito browser, on a phone, and through Google Business Profile itself. Wait 48 to 72 hours. If the count is still down, the reviews are actually gone.

Document what is missing

This is the step most owners skip and most regret. Pull your current review count, compare it against the count from before the drop, and try to identify which specific reviews disappeared. If you have notification emails from Google, those preserve the text of reviews even after the review itself is gone. If you have a monitoring tool that archives reviews, this is where it earns its keep. We covered the full process in how to track removed Google reviews.

Identify the pattern

The reviews that got removed in the April 2026 enforcement wave were not random. Look for shared characteristics. Were they short? Did they name an employee? Did they cluster on the same day? Did they all come in within hours of a visit? The pattern tells you what the classifier flagged, which tells you what to stop doing.

File a specific appeal, but expect a low success rate

For each removed review that you believe was legitimate, you can file a missing-review request through Google Business Profile support. Include the reviewer's name, the approximate date, the review text if you have it preserved, and the reason you believe the removal was incorrect. Appeals are read by humans, but the success rate is modest. The bigger payoff is the next batch of reviews, not the appeal of this batch.

Audit your current collection process

The single most useful action after a removal wave is changing the collection process so the next wave does not produce a similar pattern. Pull every email template, every SMS template, every QR code location, every script the front desk uses, and check each one against the April 2026 clauses. The version that survives the audit is the version that produces reviews the classifier accepts.

For a deeper look at the recovery side, see our guide to handling fake Google reviews and our walkthrough on why Google reviews disappear.

What the Update Means for Agencies Managing Client Reviews

For marketing agencies that run review collection on behalf of multi-location clients, the April 2026 update raised the enforcement risk significantly, because non-compliant templates scale. A single review request that mentions an employee name, run across forty client locations, produces forty pattern exposures, not one. The same is true of kiosk programs, employee bonus structures, and on-premises review collection setups deployed at scale.

A few practical implications for agency review programs:

• Audit every template before the next send. The wording that worked in 2023 may not be the wording that survives the April 2026 enforcement. Strip out employee names, service mentions, rating prompts, and any language that steers the content of the review.
• Move review collection off the premises and onto the customer's device. No tablets at reception, no kiosks at the counter, no QR codes scanned from a device the business owns. The request reaches the customer through a channel they control, after the visit.
• Replace per-review staff bonuses with team-level recognition. Per-review payouts produce the patterns the classifier is now scoring for. Team-level dashboards, internal recognition, and salary-based performance reviews are the compliant version.
• Pace sends across days and weeks, not in batches. A campaign that lands two hundred reviews in three days looks like manipulation. The same two hundred reviews spread across six weeks looks like a healthy business.
• Document the compliance work for clients. When a client's review count drops, the conversation is much easier if you have a written record of the collection practices, the template wording, and the changes made after the April 2026 update.

The agencies that adapt quickly will look fine on the other side of the enforcement wave. The ones that keep running the old playbook will lose reviews on a rolling basis, and the clients those reviews belong to will eventually notice.

How Responding Fits Into the New Compliance Picture

One of the few review-program activities that the April 2026 update did not touch is responding to reviews. Replying to every new review, positive or negative, remains entirely compliant and remains one of the strongest signals to Google that the listing is actively managed. BrightLocal's 2025 consumer survey found that 93 percent of consumers read reviews before visiting a business, and the visible business response is part of what they read.

Where AI fits into this safely is on the response side, not on the writing-the-review side. A reply drafted in seconds and sent within minutes of the review landing reads to future readers as an attentive business and reads to Google as a healthy profile. Our broader guide to Google review management walks through the full review-response framework, and the guide on reviews and local SEO covers how response activity feeds visibility in local search.

The simplest mental model for the post-April 2026 era: ask less aggressively, ask more carefully, and reply to every review that lands. The collection side gets quieter, the response side gets faster, and the listing builds the kind of pattern that the classifier reads as a real business.

Want a clean response draft the moment a review lands? Try our free AI response generator for an on-brand starting draft in seconds, no signup needed.

Frequently Asked Questions

What changed in Google's review policy in April 2026?

Google added two clauses to the Rating Manipulation section of its Maps user-generated content policy on April 17, 2026: no directing staff to hit review quotas, and no directing staff to solicit reviews that include specific content like an employee's name. The update also reinforced existing rules against on-premises pressure, review kiosks, and review gating.

Why are reviews suddenly being removed in 2026?

Google integrated Gemini models into its review moderation systems in 2025, and removal rates climbed sharply through the year. The April 2026 policy update made several common collection tactics explicitly off-limits, and the same systems are now scoring those patterns against the new language.

Is asking customers to mention a staff member's name in a review against Google's policy?

Yes, as of April 17, 2026. The business cannot direct the content, including asking customers to name a staff member. A customer can still mention staff on their own.

Can I pay my employees a bonus for collecting Google reviews?

Per-review bonuses now sit on the wrong side of the line. The new policy clause against directing staff to hit review quotas covers almost every bonus structure tied to review counts. Recognize team performance privately instead.

Is review gating against Google's policy?

Yes, and it has been since 2018. The April 2026 update reinforced the rule and enforcement has stepped up. The compliant version is the same neutral request sent to every customer, regardless of how the visit went.

How do I collect Google reviews safely in 2026?

Ask every customer with the same neutral request, sent after they leave the premises, paced as a slow drip across days. Use open-ended language with no rating prompts, no employee names, and no service mentions. Email and SMS together work well, with identical wording across both.

The Bottom Line

The April 2026 update did not invent new rules so much as it wrote down rules that had been operating in the background, and the same week it wrote them down, the moderation systems started enforcing them in plain sight. The businesses that lost reviews in the days after April 17 mostly were not bad actors. They were running collection programs that an agency set up years ago, the same programs that had quietly been producing review patterns Google's classifier had been getting better at scoring. The safe version is slower, plainer, and looks more like a real business asking customers a real question. That version will hold up through the next policy revision too.

Key Takeaways:

• Google updated the Maps review policy on April 16 and 17, 2026 with new clauses against staff review quotas and directing review content, including employee names.
• Google's systems blocked or removed 292 million policy-violating reviews in 2025, and the same systems are applying the new clauses now.
• Asking customers to name an employee, paying staff per review, on-premises review kiosks, review gating, and AI-written review text are all sitting on the wrong side of the line.
• The compliant collection playbook is a single identical neutral request to every customer, sent after the visit, paced as a slow drip, with no rating prompts and no employee names.
• If reviews have already dropped, document what is gone, identify the pattern that triggered the removal, file specific appeals, and rebuild the collection process before the next batch.
• Responding to every review is unaffected by the update and remains one of the strongest signals of a healthy listing.

For the broader evergreen reference, see our complete guide to Google review policies. For the recovery side, see how to track removed Google reviews and handling fake Google reviews.

---