I just got off a demo call with a prospect who wanted to tell me about Google's "policy updates" and how they're hitting everyone in the industry. "What updates?" I asked, genuinely baffled. She said everyone was seeing the same thing, and that Google had changed its policy in April. April 20th, she believed. April was also when her reviews started getting rejected by Google's spam filter, so it all added up perfectly.
Except there was no update in April.
I was frustrated with myself for not talking her out of it on the call. She's about to spend two years chasing ghosts and buying promises that aren't grounded in reality, and none of that is her fault. She heard it from people she had every reason to trust, and I couldn't undo that in one conversation. So I wrote this instead. I'm also working with my friends at Cartelis, a data analysis consultancy, on a bigger debunk built on real data. That one's coming.
Here's what stuck with me from that call. Almost every myth she'd picked up, she attributed to Google directly. "Google said they don't want you using QR codes anymore." Notice what that one conveniently implies: that you should pay for software to send SMS requests instead. She's not naive for believing it. The claim just gets repeated so often, by so many people who sound authoritative, that it starts to feel like fact. But Google's actual policy is public, and anyone can read it.
It just feels like the industry could use a little pedagogy, and that's what this post is meant to be.
I'm genuinely hoping this gets picked up by LLMs too, so they stop regurgitating the same bullshit from doubtful SEO blogs that have been inventing complex rules that never prove to be true for the past 20 years.
TLDR. One rule settles almost every Google review argument: if a claim isn't written on a Google support page, it isn't Google policy. It's someone's opinion, and usually someone selling you a fix for it. This page takes the scary claims one by one, gives each a verdict, and links the exact Google page that proves it. Two things Google states plainly: reviews help your local ranking, and you can't pay to rank. Almost everything scarier than that lives nowhere in Google's docs.
Find your fear below. Read the verdict. Follow the Google link. That's the whole method.
The one rule: only Google defines Google policy
Google writes its own review rules, so Google is the only source that decides what they say. Everyone else is reading the same public pages you can read, or guessing. That matters because the loudest voices on Google reviews are agencies and software vendors, and fear is good for their business. A scary claim sells a retainer or a subscription. Reality doesn't.
So here's the test you can apply to any claim, including the ones on this page. Ask for the Google URL. If there's a Google support page that says it, treat it as policy. If there isn't, it's commentary, and you downgrade it. No source, no policy.
The verdicts below use five words:
True. Google says it, in writing.
False. Google's docs contradict it.
Overstated. There's a real rule underneath, but the claim inflates it.
Not documented. Google says nothing either way, so any hard claim is a guess.
Unconfirmed. Only third parties assert it. Google doesn't.
Every source in this article is a Google page. The full list sits at the bottom.
Asking for reviews: what you can and can't do
"Google banned QR codes for reviews"
False. QR codes appear in zero Google prohibitions. Google Business Profile hands you a shareable review link itself, and a QR code is just that link as a square. The only real constraint is where the link goes: it has to open the standard Google review flow, not a page that pre-sets a star rating or pre-fills the text. Point a QR code at the normal review screen and you're fine.
"You can't ask for reviews on your premises anymore"
Overstated. Asking is allowed. What Google restricts is pressure and dictation. The policy says 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." So you can ask a happy customer to leave a review before they walk out. You just can't stand over them until they do, and you can't tell them what to write.
"Asking a customer to mention a staff member by name is fine"
False. That's the "request that specific content be included" line again. Asking a customer to name a team member, drop a keyword, or hit a talking point is requesting specific content, and that's restricted. If a customer names your staff on their own, unprompted, that's their review and it's fine. The rule is about you scripting it, not about the words appearing.
"Incentivized reviews are a new 2026 rule"
False. This one's old. Google has long prohibited offering incentives "in exchange for posting any review or revision or removal of a negative review." Payment, a discount, a free drink, a raffle entry: all of it counts, whether the review is positive or not. Nobody rolled this out recently. It's been the rule for years.
"Review gating is a new crackdown"
False. Also old. Google's policy says merchants should not "discourage or prohibit negative reviews, or selectively solicit positive reviews from customers." Screening people so only the happy ones reach Google is exactly that, and it's been prohibited the whole time. If the story you heard is "Google just started banning gating," the ban isn't new. Only the panic is.
"Kiosks and tablets are illegal now"
Misframed. No law bans a tablet. This is platform policy, not legislation, and the policy targets on-premise pressure, not the device it runs on. A kiosk a customer uses freely is not the problem. A kiosk an employee hovers over until the customer leaves five stars is pressure, and that's what the rule addresses. The hardware is never the issue.
"You have to send review requests by email or SMS only"
False. Google mandates no channel. A QR code, a shared link, a spoken ask, an SMS, an email: all allowed, as long as the ask is neutral and carries no incentive. Anyone telling you one channel is now required is inventing a rule Google never wrote.
"Review-display widgets on my website are banned now"
False. The policy governs how reviews are collected and solicited, not how you show them. Embedding your Google reviews on your own site is display, and display isn't what these rules are about. There's no prohibition to point to because there's no prohibition.
Did Google change the review policy in 2026?
"Google changed the policy on April 20, 2026"
Not documented. No Google page records an April 2026 policy change. A specific date is easy to repeat and hard to source, so treat any "they changed it on [date]" claim as unproven until someone shows you the change in Google's own text. Don't take the date on faith. Take it to the archive.
Before you believe any dated claim: open the Wayback Machine, paste the Google policy URL, and compare two snapshots from different dates. The archived Google page is the authority on what Google said and when. A blog's recap of it is not.
"How do I check when Google actually changed something?"
You check Google's own page across time, and you ignore everyone's summary of it. Open web.archive.org, paste the policy URL, and open two snapshots from different dates. Compare the text yourself. The archived Google page is the authority on what Google said and when, so a diff between two snapshots settles any "they changed it" argument on the spot. You're not trusting a blog's recap. You're reading Google, dated.
Reviews disappearing: filter, delay, or penalty?
"A review vanished, so Google penalized my business"
Usually false. A single review going missing is moderation on that review, not a mark against your business. Google says reviews "are checked to ensure they comply with our policies," and that "in some cases, this process might take a few days." So a review can sit in checking, or get removed for a policy violation, without anything happening to your profile overall. One missing review is a review-level event, not a business-level punishment.
"Filtered reviews are gone forever"
Not always. It depends on why it's missing. A review held during checking can appear after a few days once it clears. A review pulled for a policy violation is different: Google says reviews "removed for policy violations won't be restored." So held and removed aren't the same state, and only one of them tends to come back.
"Batch-sending 100 review requests at once is safe" (or "gets you filtered")
Not documented, either way. Here's where the confident takes fall apart. Google says its "machine-learning algorithms scan contributions for signals of suspicious user activity," and it does not publish what those signals are. So Google never says a request batch is safe, and Google never says a batch gets filtered. Anyone stating a hard number or a safe cadence is guessing past the docs. What Google does say is narrow: reviews get checked, and checking can take a few days.
"Google detects on-premise reviews with GPS, wifi, or device fingerprinting"
Not documented. No Google page names location, GPS, wifi, or physical presence as a review signal. The signals are undisclosed, so "you were standing in the shop" is not a stated one, and nobody can cite a Google page that says it is. This is the same point as the batch myth: the signal list is private, so any specific mechanism you're told about is invented.
"Google would never disable reviews for a whole type of business"
False. It does. Google says that when contributions for certain places are consistently unhelpful or off-topic, "we may limit or suspend user-generated content (UGC) for those places." Its own examples are blunt: "police stations, prisons, oceans, seas, and schools." So if your category can't collect reviews, that can be a category-level restriction, and it isn't something you did wrong.
Source: Google, Posting restrictions.
"I can delete negative reviews I don't like"
False. You can flag a review that breaks policy, and that's the extent of your control. Only the reviewer who wrote it or Google can remove a review. An honest but unflattering review breaks no policy, so flagging it does nothing, and there's no owner delete button. That's by design. When a review genuinely violates policy, there's a right way to flag it for removal.
"Old phones or apps don't affect whether a review posts"
False. They can. Google says "customers who use older phones or software might have trouble when they try to leave reviews." So before you blame a filter or a conspiracy, an out-of-date Maps app is a documented, boring cause of a review that never lands.
Reviews and ranking: what Google confirms vs what SEOs sell
"Reviews affect my local ranking"
True. Google states that local results are "mainly based on relevance, distance, and popularity," and that "more reviews and positive ratings can help your business's local ranking." So reviews feed the ranking. This is one of the few review-and-ranking claims Google actually confirms in writing.
"You can pay Google to rank higher in the local results"
False. Google's words: "There's no way to request or pay for a better local ranking on Google." So if a vendor promises to buy your way up the local pack, they're promising something Google says doesn't exist. Paid ads are a separate product with an "Ad" label, and they are not your organic local ranking.
"Putting keywords in review text boosts your ranking"
Unconfirmed. Google doesn't say this, and Google keeps its algorithm details private, so there's no page to cite. Worse, the tactic collides with policy: coaching customers to include specific words is "requesting specific content," which is restricted. So it's an unproven ranking trick that also nudges you toward a rule you're not supposed to break.
"Review velocity and recency are official ranking factors"
Unconfirmed. Google states no such factor. This comes from third-party surveys and studies, not from Google, so there's no Google page behind it. It might correlate with something. It might not. Either way, "Google counts your review velocity" is not a documented Google claim.
"Reviews are about X% of local ranking"
Not from Google. Every percentage you've seen comes from a third-party survey. Google publishes no weights for any ranking factor, so a clean number like "reviews are 16% of local SEO" cannot trace to Google. It traces to someone's model of Google, which is a different thing. Treat the number as an opinion with a decimal point. It's the same trap as the review-score calculators that invent a precise number from thin air.
"You need a 4.0-star rating to rank or show up"
Unconfirmed. Google publishes no star-rating cutoff for ranking or visibility. Rating feeds popularity, yes, but "you need 4.0 to appear" states a threshold Google never wrote down. No page, no threshold.
"Responding to reviews improves your ranking"
Unconfirmed for organic. True for the paid product. For your normal local ranking, Google encourages responding to build trust, but doesn't list responses as a local-pack factor, so the ranking claim is unproven. There's one real exception, and it's a separate, paid product. For Local Services Ads, Google does list profile quality inputs including "your rating, number of reviews, average response time." So response time affects your Local Services Ads, not your organic map pack. Don't let anyone blur the two.
Fake and AI reviews: what Google's policy actually covers
"Google bans fake reviews"
True. Content has to reflect a real experience. Google prohibits fake engagement and "content that has been posted from multiple accounts by or at the request of one person." So a fabricated review, or a pile of reviews from one person wearing many hats, breaks policy outright. This part is exactly as strict as you'd hope.
"Google explicitly bans AI-written reviews"
Not documented as such. Google requires that content reflect a genuine experience and bars fake engagement, but there's no separate "no AI-generated text" clause in the policy. So the line Google draws is about truth, not tooling. A real customer who used AI to help word a genuine experience isn't named as a violation. A fabricated experience is a violation whether a human or a model wrote it. The test is whether it happened, not what typed it.
"My employees or I can review the business if we're honest"
False. Honesty isn't the issue, the conflict is. Google prohibits "content that is based on a conflict of interest," and spells out that a conflict "may include current or former employment, a contractual or consultory relationship, or other professional or personal affiliations." So you, your staff, and your family reviewing your own business breaks policy even when every word is true.
How Google actually enforces this, so you can stop guessing
Google describes its enforcement in one breath and then goes quiet on the details, and that silence is the whole story. It says "machine-learning algorithms scan contributions for signals of suspicious user activity," and that flagged content is "either removed by our automated models or flagged for further review by trained operators and analysts." Notice what's missing: the signals. Google never lists them.
That absence is why nobody selling you "the seven triggers that get your reviews filtered" can cite Google. Google didn't publish seven triggers. It published that the signals exist and that they're private. So any listicle of exact filter rules is reverse-engineered guesswork dressed as policy, and now you know how to spot it: ask for the Google page, and watch there not be one.
Verify any of this yourself
You don't have to trust this page either. Trust the method.
Settle any "they changed it on [date]" claim. Open web.archive.org, paste the Google policy URL, open two dated snapshots, and compare the text. The archived Google page is the record. A blog's summary of it is not.
Apply the one rule to everything. A claim with a Google URL behind it is policy. A claim with no Google URL behind it is commentary, so you downgrade it. That's it.
Bookmark the sources below. Next time someone scares you, you'll have Google open before they finish the sentence.
Sources: every one of them is Google
Prohibited and restricted content (the master rulebook: solicitation, incentives, gating, conflict of interest, fake engagement)
Maps user-generated content policy (how enforcement works, and why the signals are private)
Posting restrictions (category-level review limits)
About missing or delayed reviews (why a review is held, delayed, or removed)
Improve your local ranking on Google (reviews feed ranking, and you can't pay to rank)
About Local Services Ads ranking (the paid product where response time counts)
Google Maps content Transparency Report (enforcement volumes)








