Google now lets shoppers hide incentivized reviews. Count what's left on your best sellers
That product with 400 glowing reviews might show 60 once a shopper taps one filter. Google's product panels in Search, Shopping and AI Mode now offer "Non-incentivized only." If your review volume came from discounts or free samples, find out what a careful shopper sees now.

As of November 10, 2026, Google's product detail panels in Search, Shopping and AI Mode show a "Non-incentivized only" review filter, reported by Search Engine Roundtable. It relies on the is_incentivized_review flag Google already requires merchants to set for reviews collected with gift cards, discounts or other rewards. Check that your review feed flags those reviews correctly, count how many reviews your best sellers keep under the filter, and shift collection toward post-purchase requests.
What appeared on November 10
Search Engine Roundtable's Barry Schwartz reported on November 10 that Google's product panels now include a review filter labeled "Non-incentivized only." Click a product in regular Search, in Shopping or in AI Mode, and the detail panel on the right lets shoppers hide reviews written in exchange for a reward. He said it showed up for almost every product and query he tried. No Google announcement accompanied it, as of November 11.
The filter isn't a surprise. Google's Product Ratings policies have allowed incentivized reviews for some time, with two conditions: the incentive can't depend on the review's sentiment, and if you gave one, you must disclose it with the is_incentivized_review attribute in your review feed. Last year Google emailed merchants reminding them that every review "boosted by incentives (gift cards, rewards points, discounts)" needs that flag. The filter is what the flag was for.
How the work moves
From review request to the filter
- Request
A customer is asked for a review, with or without a reward.
- Flag
Your review platform marks it is_incentivized_review = true if a reward was offered.
- Feed
The full review feed goes to Google at least monthly, low-star reviews included.
- Filter
A shopper taps Non-incentivized only and sees the unflagged reviews.
The count that matters
Here's a made-up but familiar case. A skincare brand runs a sampling program: free minis in exchange for an honest review. Its best seller has 400 reviews, averaging 4.7. Most came from the program. Under the filter, the product might show 60 reviews and a different average.
Review count was always a number you could buy. This filter shows shoppers the part you didn't.
Most shoppers won't tap it. The careful ones will, and they're often the ones about to spend more. So the useful question isn't whether the filter is fair. It's what your top products look like to someone who uses it.
To find out, open your five best-selling products in Google Shopping, apply the filter, and write down the count and the rating with and without it. That's ten minutes, and it tells you whether this matters to your store. The filter was reported as new, so it may not show for every search or every shopper yet. If you can't see it, check your review feed instead: count how many reviews for each product are marked as incentivized, and how many aren't. That gives you the same answer without waiting for Google.
Review count was always a number you could buy. This filter shows shoppers the part you didn't.
Three fixes, in order
Get the flag right. Ask your review platform how it sets is_incentivized_review, and check it against your campaigns. Reviews from samples, giveaways, loyalty points and "10% off your next order" requests should be flagged. Reviews from plain post-purchase emails shouldn't. Wrong flags cut both ways: unflagged incentivized reviews break Google's policy, and over-flagging hides honest reviews from the filter. Google's feed schema also has an is_verified_purchase flag. If your platform can set it accurately, set it.
Send the whole feed. Google requires the full review feed at least monthly, low-star reviews included, and says you may not delete old reviews from it. Stale feeds lose eligibility for Product Ratings. A merchant who cleaned up the feed to look better is now in a worse spot than one who sent everything.
Shift where reviews come from. If the filter strips most of your reviews, the long-term fix is more reviews from people who actually bought: a well-timed request after delivery, a simple form, a reminder for repeat buyers. Our note on why a review should come from a finished order covers the timing, and our recent note on Reddit's new product review pages shows the same pressure coming from outside Google.
Decision guide
Reviewing your review program
| Consideration | Worth changing | Worth keeping |
|---|---|---|
| Who you ask | Sample recipients and contest entrants who never paid | Customers after a delivered order |
| What you offer | A reward only for five-star reviews (not allowed) | No reward, or one offered regardless of rating and flagged |
| The flag | Not set, or set by guesswork | Set from the campaign that produced the review |
| What you watch | Total review count | Count and rating under the filter on your top products |
What not to do
A few reactions feel sensible in the moment and make things worse. Avoid these.
Don't stop flagging to protect your count. Google's policies allow it to remove reviews, block feeds and, for repeated or egregious violations, suspend accounts. Don't offer a reward only for good reviews either. That's not allowed with or without the flag.
And don't panic about a smaller number. A product with 60 honest reviews and a clear rating can sell perfectly well. What hurts is a shopper noticing the gap between 400 and 60 and wondering what else was arranged.
If you do keep a sampling or rewards program, keep it for what it's good at: getting a brand-new product its first reviews, from people who've actually used it. Flag those reviews properly, and plan for organic reviews from real orders to take over as the product sells.
Five questions for your review platform
Most stores don't build their own review feed, and that's fine. A review app or aggregator collects the reviews and sends them to Google. That means the flag is set by software you didn't write, based on information you may or may not have given it. Send your provider these questions:
- How do you decide whether a review is incentivized, and can we see that setting per review?
- When we run a campaign with a reward, how do we tell you, so its reviews are flagged automatically?
- Do you set
is_verified_purchase, and from what data? - Do you send our full review history to Google every month, including low-star reviews?
- Can you give us a count of flagged and unflagged reviews for our top products?
If the answers are vague, that's your answer. A platform that can't tell you how it flags reviews can't protect you when Google checks.
Ask for the answers by email rather than on a call, and save them with your store's other settings. When the person who set up the review app leaves, the next person will want to know how the flag was meant to work.
Why this belongs with your store, not just your marketing
This is the kind of change that lands between teams, and that's why it gets missed. Marketing ran the sampling campaign, the review app was set up by whoever built the store, and the feed hasn't been opened in a year. Nobody owns the flag, so nobody notices when it's wrong.
Review collection usually lives with marketing, the feed with whoever set up Merchant Center, and the platform with a vendor. When a flag is wrong, nobody owns it. Put one person in charge of the path from request to flag to feed, and check it whenever a new campaign starts.
We help commerce teams connect the systems behind a product page so what shoppers see is accurate. See our ecommerce work or talk to us.
Related work: Paddle8
We build alongside the people doing the work.
Bring us the problem you’re thinking about.