Google's 2026 Review Policy Update and How to Keep Your Reviews

Something quiet but important happened to Google's review rules in early 2026. In mid-February, Google rewrote the review section of its Maps user-generated content policy. The new text bans pressuring customers to review while they are still on the premises, bans asking for specific content in a review, and adds two lines about what merchants may ask their own staff to do.

Almost nobody noticed the staff lines until April 17, the day after Google posted a blog explaining a new wave of review protections on Maps. That is why most coverage calls this the April 2026 update.

The rewrite coincided with complaints. The week it landed, Search Engine Roundtable reported an uptick in complaints from businesses watching their reviews disappear, sometimes a handful, sometimes dozens or more, from what owners described as real customers. The policy did not arrive out of nowhere, but the new text made several gray-area habits unambiguously off-limits.

Google's systems blocked or removed 292 million policy-violating reviews in 2025, and those are the systems that enforce these rules. 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 2026, with the exact policy clauses and the real dates
• 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
• What has happened since, through October 2026, including the reviewer survey, the July incident, and Google's new spam-spike emails
• 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 2026, and When

The 2026 update was really three events, and the dates matter because most coverage folded them into one.

Mid-February 2026: the policy text changed. Archived copies of Google's Maps policy on prohibited and restricted content show the rewrite landing between February 15 and February 17, 2026. Before it, the review rules sat under a heading called "Fake engagement." After it, Rating Manipulation was a section of its own, with new language. Search Engine Roundtable reported the rewrite on February 20, a day after its story on the removal complaints.

April 16, 2026: Google's Maps blog. 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. It laid out three new protections. The first upgrades Google's systems to stop review scams, like demands for payment to remove fake one-star reviews, before the reviews go live. If a profile gets a sudden spike in spam reviews, Google said it will remove the fake content, pause new reviews, alert the owner, and show consumers a banner explaining the pause. The second uses Gemini to catch unhelpful edits to place names faster. The third is proactive email alerts so verified owners can review important edits to their profiles before they go live. The post also published Google's 2025 Trust and Safety numbers: "Our advanced systems and expert analysts blocked or removed over 292 million policy-violating reviews, while publishing more than 1 billion helpful reviews."

April 17, 2026: the staff clauses got noticed. Google Product Expert Amy Toman spotted the two staff lines and shared them on LinkedIn, and PPC Land reported them that day as a fresh change. The February archive shows they were already two months old, but April 17 is when the industry started talking about them.

Here is the sentence at the center of the rewrite: "When soliciting reviews, merchants should not require or pressure users to leave ratings or write reviews while on the premises, nor should they request that specific content be included." Two examples sit directly under it, both about what merchants may ask their own staff to do.

The first 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 it.

The second 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," and the sentence above it also covers asking customers to mention a specific service, package, or keyword. How far "specific content" reaches is still debated: in the LinkedIn thread PPC Land quoted, consultant Miriam Ellis asked whether a line like "We'd love your review of our new menu item" now crosses it, and Toman replied that the intent likely centered on review contests but that she had no official confirmation from Google. The safe reading is the literal one. The content of the review must come from the customer, not from a script.

All of this sits under Rating Manipulation, the section of the Maps policy that also covers "Content exhibiting unusual volumes or patterns of review contributions that are indicative of 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 section as incentivized reviews and conflict-of-interest reviews.

Some language carried over. The policy still says that "contributions to Google Maps should reflect a genuine experience at a place or business," it still bans incentives and conflict-of-interest content, and it still says merchants may not "Discourage or prohibit negative reviews, or selectively solicit positive reviews from customers." It also spells out what is allowed: merchants may "solicit or encourage the posting of content that does represent a genuine experience, without offering incentives to do so or attempting to influence the rating or the contents of the review." Asking for reviews is fine. Steering them is not.

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 more than 240 million in 2024, an increase of roughly 21 percent. The same April 16 post 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. By PPC Land's arithmetic, roughly 22 percent of all review activity on Maps in 2025 was policy-violating, more than one in five review attempts.

The piece of that figure most relevant to legitimate small businesses is that the enforcement is no longer manual or rare. Google credits "advanced systems and expert analysts" for the number, and in its April 2025 roundup of 2024 it said AI now lets it "revisit reviews more frequently to identify new abuse patterns even months after they were originally posted." Independent data points the same way. A December 2025 Search Engine Land analysis of 60,000 Business Profiles found a sharp increase in deleted reviews between January and July 2025. Five-star reviews made up a sizable share of the deletions, and many deleted restaurant and retail reviews were more than two years old.

For a single business, the practical implication is simple. Google does not publish the signals its systems score, but its policy names the shape it looks for: "unusual volumes or patterns of review contributions." An automated system cannot see that your collection process is well-intentioned. A burst of reviews that does not match the listing's normal weekly rhythm, or a run of reviews mentioning the same employee, matches the patterns the policy describes even when every reviewer is real.

Once a review is removed for a policy violation, Google's help center says it won't be restored. We covered what you can still do 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.

What Has Happened Since April: Enforcement Through October 2026

The 2026 update was not a one-week event. The months since have brought a new signal Google collects straight from reviewers, removals of older reviews, one large July incident Google treated as an error, and a new email that tells owners when Google pauses their reviews.

Google Maps now asks reviewers whether the business offered a reward. Some Maps users are shown an in-app question asking whether the business offers rewards in exchange for reviews, with Yes, No, and Not sure as the options. PPC Land documented it on June 5, 2026, citing a Search Engine Roundtable report that the prompt had been appearing for about nine months. Colan Nielsen of Sterling Sky said that when a user answers yes, those reviews are getting deleted. Claudia Tomina of Reputation Arm shared data from one client showing 1,045 deletions in December 2025 alone, and a large share of the reviews deleted in late 2025 had originally been posted in August and September 2024. If any part of a collection program involves discounts, gift cards, or freebies, Google is no longer just inferring it from patterns. It is asking customers directly.

Enforcement reaches back. Google says it revisits reviews "even months after they were originally posted," and the deletion data above includes reviews that had been live for more than a year. Cleaning up the collection process protects the next batch, but older reviews stay exposed to the same checks.

Formal profile restrictions are the escalation path. Google's published penalty for fake engagement goes beyond removing individual reviews. Business Profile restrictions can block a profile from receiving new reviews for a set period, unpublish its existing reviews, and display a public warning telling consumers that fake reviews were removed from the listing. Owners are notified by email and can appeal, but the warning label is the reputational version of a penalty box.

The July 2026 vanishing-reviews incident was treated as an error, not a sweep. In early July 2026, owners reported review counts collapsing within a day; one wrote that about 4,651 reviews dropped to 63. Search Engine Roundtable covered the wave of complaints on July 3. A Google spokesperson said that when its systems detect suspicious reviews, they may remove reviews and temporarily pause reviews on the profile, and that Google was investigating and would restore any reviews that were incorrectly removed. Google later said the issue was resolved and the missing reviews should be visible again. A separate "You have no reviews yet" bug followed the next week; Google said those reviews remained published on Search and Maps and only the owner dashboard was affected. The practical lesson: you cannot tell an error from a policy sweep unless you know exactly what you had before the drop.

Spike protection is live, and it emails owners. In September 2026, Search Engine Roundtable published the email Google now sends when it detects a burst of spam reviews: "Google has detected a spike in spam reviews on your Business Profile and removed them so they do not affect your Google rating." New ratings, reviews, and other contributions are paused, and "Google will lift this pause once the risk is mitigated, typically within a few days." The email says owners who believe legitimate reviews were removed by mistake can request a review. Amy Toman described a former client, known for a steady stream of reviews, that got the email after opening a new location, and said the filter "needs to be refined a bit." It is not only spam attacks that trip it.

Appeals are backed up, and flooding support now has its own policy. On September 29, 2026, Search Engine Roundtable reported a new "Misuse of support channels" section in Google's Business Profile third-party policies. Its warning: "Repeated unfounded submissions can result in rejection of all further complaints without assessment." On October 20, it reported that review appeals were delayed again, quoting Google's Dan Boguslavsky: "Due to high volume of review related appeals, processing times are currently extended." His advice in the same post: "Do not create a duplicate appeal."

The Collection Habits That Are Now Policy Violations

Some of what the 2026 rewrite made explicit was already a violation under older policy language. The difference now is that the practices have specific names attached to them in the policy.

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 February 2026 staff 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.

Why Google flags it: The policy text explicitly names merchants requesting that staff solicit reviews that include specific content, including content that identifies a staff member. The direction 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 looks directed, whatever the intent.

Tying Employee Bonuses to Review Counts

The 2026 text names merchants requesting that staff solicit a certain number of reviews. A per-review bonus is not word for word a quota, but it pays staff for the same thing: a count. PPC Land's coverage of the clauses listed review contests and staff leaderboards among the practices they target.

Why Google flags it: Quotas push staff toward the easiest reviews to collect, which usually means asking at the counter, scripts that mention the employee's name, and clusters of reviews posted within a single shift. The same policy section names each of those separately.

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 reward exactly the count the policy names.

Asking for Reviews While the Customer Is Still on the Premises

Since February 2026, the policy says merchants "should not require or pressure users to leave ratings or write reviews while on the premises." Google has not said how it detects on-premises reviews, so be wary of anyone who claims to know the exact signals.

Why Google flags it: A review written at the counter, with staff watching, is the pressure the rule describes, even when the customer is happy to do it. Several reviews posted from inside the business during one shift also add up to the kind of unusual pattern the same section names.

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 gives the customer room to decide on their own. 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. The policy never mentions kiosks, but a tablet at reception is the on-premises request in hardware form: the customer reviews where staff can see, on a device the business controls, before they leave.

Why Google flags it: It combines the on-premises request with a pattern problem. Many reviews from one device in one place over a short window look like orchestrated collection, even if every individual review is from a real customer expressing a real opinion.

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 own device, not when scanned from a fixed device at the counter. Google's own tips suggest asking customers to visit a review link or scan a QR code. 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. Google has prohibited it since April 2018, when Sterling Sky reported the guideline change, and the policy now says merchants may not "Discourage or prohibit negative reviews, or selectively solicit positive reviews from customers." The 2026 rewrite did not introduce this rule; it moved it under Rating Manipulation. For the full picture, including the FTC's example of the practice and a compliant feedback-first flow, see our review gating guide.

Why it backfires: Google's own review tips say "A mix of positive and negative feedback often feels more trustworthy." And when gating is reported, the cost can be large: Sterling Sky documented a business with over 400 reviews that lost over 80% of them after it was reported for gating through a widget on its website, including reviews left two years earlier.

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

The policy does not mention AI by name, and Google does not publish how it screens review text. What it does say covers the practice: merchants and users may not "Solicit or encourage the posting of content that does not represent a genuine experience," and merchants may not request that specific content be included.

Why it is a violation: A review the business wrote, by hand or with AI, is the business's words, not the customer's experience in their own words. Pre-written templates also tend to repeat the same handful of phrases across many reviews, which is easy to spot.

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 exhibiting unusual volumes or patterns of review contributions that are indicative of 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. Google's spam-spike emails from September 2026 show it acting on bursts directly: it removes the reviews it judges to be spam and pauses new ones for a few days.

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 in 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, which our free review link generator can find for you. 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 time, with nobody waiting at the counter.

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 exactly the kind of burst the policy's "unusual volumes or patterns" line describes. 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. A sensible default is somewhere 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. For a deeper look at timing the request, see our guide on the best time to ask for a Google review.

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.

You cannot act on a removal you never noticed. Removed review tracking scans your full history daily and keeps a record of what Google took down, with a 24-hour confirmation window before alerts so you are not chasing false alarms.

What to Do If Reviews Have Already Been Removed

If you are reading this after watching your review count drop at any point in 2026, the order of operations matters more than the panic. Document what disappeared first, while you can still tell.

Confirm it is not a display glitch

Google has occasional display issues where reviews vanish from one view but remain in others. In July 2026, a dashboard bug told owners they had no reviews yet while Google said the reviews stayed published on Search and Maps, and the larger July incident ended with Google saying the missing reviews should be visible again. 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

If the removals cluster, look for what they share. 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 is the best clue you will get to what Google's systems flagged, which tells you what to stop doing.

Know what Google will and will not restore

Google is blunt about policy removals: "Reviews removed for policy violations won't be restored." Its page on reporting reviews adds that automated spam detection "may also mistakenly remove legitimate reviews" and says to contact support if that happens. If the removal came with Google's spam-spike email, use the option in that email to request a review. When you contact support, send one request per problem with the reviewer's name, the approximate date, and the review text if you preserved it, then wait. Google has said review appeals are taking longer than usual and asked owners not to file duplicates, and repeated unfounded submissions can now get all further complaints rejected without assessment. 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 2026 policy text. The version that survives the audit is the one that asks without steering, pressuring, or paying.

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 2026 rules raised the stakes, 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 survive the 2026 policy text. 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 reward the count the policy now names. 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 2026 update.
• Don't flood support on a client's behalf. Google's Business Profile third-party policies now include "Misuse of support channels," which warns that repeated unfounded submissions can result in rejection of all further complaints without assessment. One well-documented request per problem.

The agencies that adapt quickly will look fine on the other side of the enforcement wave. The ones that keep running the old playbook risk losing 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 2026 update did not touch is responding to reviews. Replying to every new review, positive or negative, remains entirely compliant, and Google's own tips to get more reviews list replying among its best practices. BrightLocal's 2026 Local Consumer Review Survey found that 97% of consumers read reviews for local businesses, and 80% say they're likely to use a business that responds to all of its reviews.

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 customers as an attentive business. 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 2026: 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 steady pattern of 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 2026?

In mid-February 2026, Google rewrote the review rules in its Maps user-generated content policy. Merchants should not pressure customers to review while on the premises or request specific content, and the policy names two examples: directing staff to hit review quotas, and directing staff to solicit reviews that include specific content like an employee's name. The staff lines drew wide notice on April 17, 2026, which is why most coverage calls it the April 2026 update.

Why are reviews suddenly being removed in 2026?

Google blocked or removed over 292 million policy-violating reviews in 2025, up from more than 240 million in 2024, and it says it now revisits reviews months after they were posted. The February 2026 rewrite put several common collection habits explicitly out of bounds, and Google now pauses reviews and emails owners when it detects a spike in spam reviews.

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

Yes, since February 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?

It is risky. The policy names merchants requesting that staff solicit a certain number of reviews, and a per-review bonus pays for exactly that kind of count. Recognize team performance privately instead.

Is review gating against Google's policy?

Yes, and it has been since April 2018. The February 2026 rewrite kept the rule and moved it under Rating Manipulation. 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.

Is Google asking customers whether a business paid for their review?

Yes. Google Maps shows some users a question asking whether the business offers rewards in exchange for reviews. Sterling Sky's Colan Nielsen said that when users answer yes, those reviews are getting deleted, and one client's data shared by Reputation Arm showed deleted reviews that had been posted more than a year earlier.

Why did Google reviews disappear in July 2026?

Early July 2026 brought a wave of vanishing reviews that Google treated as an error, not a policy sweep. Google said it was investigating and would restore any reviews that were incorrectly removed, and later said the missing reviews should be visible again. Policy-based removals are different: they are selective, and Google says reviews removed for policy violations will not be restored.

Did Google change its review policy in October or December 2025?

Not the written rules. Archived copies show the review sections of Google's Maps policy unchanged from September 2025 until mid-February 2026. Late 2025 brought a wave of review removals that Search Engine Roundtable said started in October and was fixed in December, plus, per PPC Land, Google's first formal help documentation for review links and QR codes on December 31, 2025.

Is this the same as Google's April reviews update?

No. Google Search's reviews updates, such as the April 2023 reviews update, affect how Search ranks websites that publish review articles, and Google says that system "does not evaluate third-party reviews, such as those posted by users in the reviews section of a product or services page." The Maps policy in this guide governs reviews customers leave on your Business Profile.

What does Google's spike in spam reviews email mean?

Google detected what it judged to be a burst of spam reviews on your profile, removed them, and paused new ratings and reviews until the risk passes, which the email says happens "typically within a few days." If you think genuine reviews were caught, the email offers a way to request a review. It can fire on real reviews too, so check whether your own requests went out in a burst.

The Bottom Line

The 2026 update did not invent new rules so much as it wrote down rules that had been operating in the background. Google rewrote the text in February, the industry noticed the staff lines in April, and by September Google was emailing owners when it paused their reviews after a spike. Plenty of the businesses losing reviews are not bad actors. Many are running collection programs an agency set up years ago, programs that produce the volumes and patterns the policy now names. 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 rewrote its Maps review policy in mid-February 2026, adding an on-premises rule, a ban on requesting specific content, and examples covering staff review quotas and employee names. The staff lines drew wide notice on April 17, 2026.
• Google's systems blocked or removed 292 million policy-violating reviews in 2025, up from more than 240 million in 2024.
• Asking customers to name an employee, paying staff per review, on-premises review kiosks, review gating, and business-written review text are all sitting on the wrong side of the line.
• Enforcement has continued through October 2026: Maps asks reviewers whether the business offered rewards, removals reach reviews more than a year old, and Google now emails owners when it pauses reviews after a spam spike.
• 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, know that policy removals are not restored, send one well-documented support request, and rebuild the collection process before the next batch.
• Responding to every review is unaffected by the update, and Google lists replying among its own best practices.

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.

---