Google blocked or removed over 292 million policy-violating reviews in 2025, up 21% year over year, along with 13 million fake Business Profiles and posting restrictions on more than 782,000 accounts. Those are Google's own numbers from its 2025 Trust and Safety report.
So why does your flag keep coming back denied?
Because the automated sweep and your individual request are two different systems. The sweep catches patterns at scale. Your request gets evaluated against one question, and it is not the question you think you are asking.
Google does not remove reviews for being false. It removes reviews for violating a written policy. Its own help documentation says it directly: "Google doesn't get involved in conflict between businesses and customers."
That distinction is why most owner-submitted removals fail. You flag a review as "spam" because it is a lie, a reviewer checks it against the spam policy, sees a real account leaving a plausible complaint, and declines. Your actual grievance was never assessed.
This guide closes that gap: how to map your fake review onto the policy that gets it pulled, and what to do at each rung of the ladder when it does not.
Lever 1: Pick the policy, not the grievance
Before you touch the flag button, read the review and decide which written policy it breaks. Google's Prohibited and Restricted Content policy is the operative document, and these are the categories that actually apply to a fake review on a service business.
| Policy category | What it covers | What you need to show |
|---|---|---|
| Conflict of interest | Competitors, former employees, contractual or personal affiliations. Explicitly prohibits "content posted on a competitor's place or business to undermine that business' reputation" | The reviewer's link to a competitor: account history, named mentions, shared posting patterns |
| Fake engagement | Content not based on a real experience, content posted from multiple accounts at one person's request | No record of the job, accounts created same-day, identical phrasing across accounts |
| Off-topic | Content not based on an experience at your location, general rants, social commentary | The review describes no service, no date, no job, no interaction |
| Personal information | Names or images of a person posted without consent | The review names a non-public employee |
| Impersonation | Posing as a person, group, or organisation | Reviewer uses a fabricated or borrowed identity |
| Restricted or offensive | Profanity used to emphasise criticism, unsubstantiated allegations of criminal wrongdoing | Direct quote of the language used |
The mismatch between what owners flag and what the policy says is the whole problem. Consider the most-upvoted recent case: in April 2026, r/smallbusiness user monsoon__004 described exactly this pattern, in a post that drew 181 upvotes.
Watch out
"None of the names are in our customer database and they all vaguely mention a better alternative in town, which makes it super obvious it's a competitor paying for negative reviews. I flagged all of them as spam and opened a ticket with Google Business Profile support but they just sent back an automated email saying the reviews don't violate their policies."
Flagged as spam. Denied. But "reviews that mention a better alternative in town" is not a spam case, it is a textbook conflict of interest case, which Google's policy names explicitly. The evidence was strong. The category was wrong.
Lever 2: The named-employee route almost nobody uses
Here is a removal path that appears in Google's policy and almost never in removal guides.
Google's personal information policy prohibits content containing "personal information of another posted without their consent such as: full name, or last name, their face in a photograph." It then carves out an exception, and the exception is where the nuance lives:
An individual's name if they are a public-facing professional conducting business under their name. This includes: doctors, lawyers, realtors, financial planners, contractors and others professionals doing business under their names.
Read that carefully, because it cuts both ways for a trades business.
If the review names you, the owner, and you trade under your own name, that is allowed content and the personal information lever is closed. But if the review names your installer, your technician, or your office admin, a person who is not a public-facing professional trading under their own name, that is personal information posted without consent, and it is removable regardless of whether the review's claims are true.
This is a common shape for retaliatory reviews. In April 2026, r/smallbusiness user Powerful_Outcome_917 described fake accounts "specifically targeting a single employee," adding: "I also don't appreciate my employees being called out/named like this." That is a personal information violation sitting unflagged while the owner argues about accuracy.
Tip
If a review names a member of your crew who does not trade under their own name, flag it under personal information and quote the employee's non-public status in your evidence. This is a cleaner case than proving the review is fake, because you do not have to prove anything about the underlying claim.
Lever 3: Work the escalation ladder in order
Each rung is a distinct system with a distinct reviewer. Skipping rungs, or repeating one, wastes the queue.
- Flag from your Business Profile. Read reviews, select Report next to the review, choose the category you decided on above.
- Track it in the Reviews Management Tool. This is where status lives. Google says evaluation "typically takes several days."
- Submit the one-time appeal. If the flag is denied, the Reviews Management Tool offers a single appeal. You get one. Do not spend it on the same argument that just failed. Change the category or add evidence that removes the need for interpretation.
- Post in the Google Business Profile Help Community with your case ID. Product Experts there can escalate internally. This is the rung most owners never reach.
- The merchant extortion form, if and only if money was demanded. See below.
The thing to understand about rung 3 is that a denial is not a verdict on the truth. It is a verdict on whether one reviewer, in a few seconds, could see an unambiguous policy breach. In November 2024, r/GoogleMyBusiness user Rude-Imagination1041 documented a reviewer who "spammed 10 businesses with 1 star with no comments within 2 minutes of each other," screenshotted it, appealed, and was told it was not spam. The evidence was genuinely good. It still needed to arrive pre-interpreted, with the pattern spelled out, rather than as raw screenshots.
Note
Do not re-flag the same review repeatedly, and do not ask friends to flag it. Google weighs account trust and history when evaluating reports, and repeated identical reports from low-history accounts do not add signal. One well-built case beats fifty flags.
Review attacks hurt most when Google is your only source of work. If a five-review swing can take your phone from ringing to silent, the problem is not the reviews, it is a single-channel pipeline. We build lead generation systems that run independently of your map pack position, so a bad fortnight on Google is an annoyance rather than a crisis.
Lever 4: If money was demanded, skip the queue
There is a separate, higher-priority reporting channel that most removal guides published before mid-2026 do not mention, because it did not exist.
If you get a sudden wave of one and two-star reviews followed by someone demanding payment to remove them, that is an extortion scam, and Google runs a dedicated merchant extortion report form for it. It goes to an investigating team, not to the general review queue.
Google's instructions are specific. Do not engage. Do not pay. Do not attempt to negotiate directly. Gather evidence immediately, and submit:
- Screenshots of every demand, showing date, time, and the sender's contact details
- Direct links to each suspicious review
- Any names, usernames, emails, phone numbers, or social profiles tied to the people making demands
- The date and time you first noticed the review spike, and the date you first received the demand
Operators recognise the pattern independently. In April 2026, r/smallbusiness user MegaMAGA84 described it precisely: "Fake or questionable accounts leave negative reviews. Business owner gets concerned. Someone reaches out offering paid removal help." In December 2025, cubemaster27 reported obtaining "a direct written admission from the person involved stating they were paid to place the reviews," then filed with both Google Trust and Safety and IC3.
Google confirmed in April 2026 that it had upgraded its systems to detect "attempts to demand payment in exchange for removing fake one-star reviews." On a detected spike it will now remove the content, pause new reviews, alert the owner, and show a banner explaining the pause. That banner matters: it is a public signal that you were attacked rather than that you are bad at your job.
Lever 5: Do the recovery math before you panic
Most owners badly misjudge the damage, in both directions. Here is the arithmetic.
A one-star review pulls your average down by an amount that depends entirely on how many real reviews you already have. Below is what five fake one-stars do to a profile sitting at a 4.8 average.
| Real reviews before the attack | Average after five fake one-stars | Five-star reviews needed to get back above 4.5 |
|---|---|---|
| 20 | 4.04 | 23 |
| 40 | 4.38 | 11 |
| 80 | 4.58 | 0 |
| 120 | 4.65 | 0 |
Now the number that reframes the whole problem. To restore your original 4.8 average after five fake one-stars takes about 95 new five-star reviews, and that figure is the same whether you had 20 reviews or 120. Each one-star costs you 3.8 rating points against a 4.8 baseline, and each new five-star only buys back 0.2.
Chasing your old decimal is therefore a losing game. Defending a threshold is not.
And the thresholds moved sharply this year. BrightLocal's Local Consumer Review Survey 2026, run across 1,002 US adults, found 31% of consumers will only use a business with 4.5 stars or more, up from 17% the year before. 68% now require four stars or better, up from 55%. Meanwhile 47% will not use a business with fewer than 20 reviews, and 74% only care about reviews written in the last three months.
Put those together and the defensive strategy writes itself. Volume is armour, recency is the maintenance schedule, and the decimal is mostly vanity. A profile with 80 genuine reviews absorbs a five-review attack without crossing a single buying threshold. A profile with 20 falls through two of them.
That is the strongest argument for treating review generation as a standing habit rather than a campaign. The reviews you collect this quarter are the buffer that makes next year's attack a non-event.
By the numbers
An r/smallbusiness reputation operator posted a February 2026 case study of a client hit with 15 to 20 fake one-stars in 10 days: the rating fell from 4.8 to 3.9, the profile dropped out of the Local Pack, and call volume fell 40%. Recovery took roughly 30 days and required documenting the pattern, citing specific policy violations, and rebuilding genuine review velocity.
Lever 6: Four pieces of common advice that make it worse
Every one of these appears in the Reddit threads on this topic. Every one is a mistake.
Delete your profile and start fresh. Suggested by r/GoogleMyBusiness user SmallBizOwner67 in December 2024: "you're probably better off just closing your Google account and opening a new one, then asking the customers that left you reviews to repost them." This is catastrophic. You permanently lose every genuine review, your photos, your profile age, and your recency signal, then re-enter a market where 47% of consumers will not use a business with fewer than 20 reviews. Almost nobody who left a review will ever repost it.
Review-bomb them back. As one commenter put it: "Find the companies doing this and leave them bad reviews also." That is the same violation you are reporting, it is trivially traceable, and it converts a clean complaint into a mutual dispute in which Google has grounds to restrict your account.
Get friends to mass-flag it. Google weighs "account information, user actions and whether a pattern of harmful behavior exists" when assessing reports. A brigade of low-history accounts adds volume without credibility, and report count is not what decides the outcome.
Pay a removal service. Some are legitimate, none can guarantee anything, and the market rate is brutal. SmallBizOwner67 cited a $10,000-per-review quote with no guarantee against a repost. A former reputation-management employee described the standard method in the same thread: mass-reporting every review an account has ever left, from aged accounts across many regions, "completely automated using mobile emulators." That breaches Google's policy on device tampering and emulated engagement, and if it is traced to your profile you hold the risk.
Lever 7: Know when the legal route is genuinely available
This is where the advice on the rest of the internet is written for the wrong country, and where Canadian owners have a materially stronger position than they realise.
Most guides tell you that suing is theoretical because platforms are immune. In the United States that is broadly accurate: section 230 of the Communications Decency Act gives platforms wide protection for user-generated content. Canada has no equivalent statute, and Canadian courts have been steadily narrowing the passive-intermediary defence.
The case law has moved fast:
- Thorpe v. Boakye (2022, Ontario Superior Court). A Brampton daycare was targeted by false reviews from a former customer, her husband, and others who had never been customers. Google sought summary judgment arguing it was a passive intermediary. Justice Price refused, holding that hosting reviews is materially different from linking to content, because Google built the platform, surfaced the reviews in Search and Maps, and controlled whether they stayed up.
- Jeffery v. Almusslat (2025, Ontario Small Claims Court). A Toronto lawyer was hit with more than two dozen false one-star reviews, some under fictitious names. Deputy Judge Timms held that once Google's own team receives a complaint, assesses it, and decides the content stays, Google is no longer neutral and becomes a publisher. General damages of $15,000 were awarded against Google and the posters jointly and severally, with a further $7,500 in aggravated damages against the posters.
- A.B. c. Google (Quebec Superior Court). $500,000 in moral damages plus an injunction, in a case where Google removed a defamatory link and then restored it.
The practical significance for a contractor is the venue. Ontario's Small Claims Court limit rose from $35,000 to $50,000 on 1 October 2025 under O. Reg. 42/25. The Jeffery award sat comfortably inside that. This is a claim a licensed paralegal can run, not a Superior Court action requiring a litigation budget.
Two things to do now, well before you decide whether to sue:
Put your complaint in writing, with specificity. Both Thorpe and Jeffery turned on what Google knew, when it knew it, and what it chose to do. A formal written complaint identifying the exact content, explaining why it is defamatory, and requesting removal creates the evidentiary record. Informal flagging does not.
Preserve everything immediately. Timestamped screenshots, the reviewer's profile and full review history, your job records showing no such customer, and every exchange with Google including case IDs.
Watch out
This is background on where the case law sits, not legal advice, and defamation has strict procedural traps including notice and limitation periods that differ by province and by publication type. If you are seriously considering a claim, speak to a defamation lawyer or paralegal early, because the deadlines can be short.
Reporting a competitor who is buying positive reviews
The reverse case has its own route, and it now carries statutory teeth on both sides of the border.
In Canada, materially false or misleading representations to promote a business are reviewable conduct under the Competition Act, and the June 2024 amendments under Bill C-59 expanded the deceptive marketing provisions and extended private-party access to the Competition Tribunal for deceptive marketing. Complaints go to the Competition Bureau.
In the United States, the FTC's rule at 16 CFR Part 465 took effect on 21 October 2024 and bans the buying, selling, and writing of fake reviews outright, with civil penalties currently up to $53,088 per violation. Benesch reported in April 2026 that the FTC has moved into active enforcement under the rule.
Neither route is fast, and neither will clean up your own profile. But if a competitor's 300-review profile is obviously purchased, these are the channels that carry actual consequences, as opposed to a flag that disappears into a queue.
The owners who handle review attacks calmly are the ones whose lead flow does not depend on a star rating. Pavado builds the conversion page, the qualifying form, and the tracking, then feeds it with outreach and Meta campaigns you own. Book a free lead plan and we will show you what your pipeline looks like without Google in the middle of it.
The first 48 hours: a checklist
When a wave lands, the order of operations matters more than the speed.
- Screenshot everything before you flag. Reviews, reviewer profiles, each reviewer's full contribution history, and the timestamps. Reviewers delete accounts.
- Check your job records and confirm in writing that no such customer exists. This is your core evidence.
- Map the pattern. Posting times, account ages, repeated phrasing, whether the same accounts left five stars for one particular competitor.
- Pick one policy category per review. Conflict of interest for competitor attacks. Personal information where a non-public employee is named. Off-topic where no service is described.
- Reply once to each, briefly and without emotion. State that you have no record of the job and invite genuine customers to contact you. This is written for the next prospect, not for the attacker. 89% of consumers expect owners to respond, and 50% are put off by generic templated replies, so vary them.
- Flag, then record every case ID.
- If any payment was demanded, file the merchant extortion report and stop engaging entirely.
- Start the review engine the same week. Ask every completed job. Volume is the only defence that compounds.
- If the appeal fails and the damage is real, get the written complaint on file and take advice on your options.
The uncomfortable truth is that step 8 outperforms steps 1 through 7 combined over any horizon longer than a month. Removal is a coin flip you cannot control. Review volume is a process you can. If Google removed 292 million reviews last year and operators are still posting these threads, individual removal will keep being unreliable, and the businesses that shrug off attacks are the ones that built the buffer before they needed it.
If your profile is also struggling to surface at all, removal is the smaller problem. Start with why your Google Business Profile is not showing up, then come back to the reviews.