Viewer counters and Merchant Center: what you can show
A “12 people are viewing this” counter is a claim about your live traffic, so it has to come from your analytics at that moment, not a random number. Plenty of these widgets ship with demo numbers switched on, and plenty of stores never switch them off. Tie the counter to real session data, or take it down and let real reviews do the persuading.
Why this matters
Merchant Center's Misrepresentation policy covers every statement you make about an offer, and a live-viewer count is one of them. It rules out offers that represent you or your products in a way that's “not accurate, realistic, and truthful”. A number drawn from a random range, or the same number stamped on every product at once, is not a measurement of anything. It is decoration pretending to be data, and the policy has no category for decoration.
Google's “Building trust with your customers” page points at the honest version of social proof: “Show reviews and testimonials about your products and business.” A review count from verified orders, a verified-buyer label or a true dispatch time does the reassuring job without inventing a crowd. Viewer pop-ups can add a second problem when they sit on top of the product. Google's landing page requirements say “Avoid layouts that hide key elements of the page”, and that “a pop-up or download banner shouldn't cover important information for your customers.”
Product Experts on Google's Merchant Center Community are blunter with stores trying to get reinstated: no urgency overlays, and nothing “that could be interpreted as false scarcity”. A crowd that is not there is exactly that. Community advice, stricter than policy, and sensible either way.
The free scan flags a “people viewing” counter wherever it finds one, and it visits the page twice in fresh sessions: an activity pop-up that repeats itself or changes its number between those visits is reported as a failure. The widget is visible to the scan; your analytics are not, so the comparison with real sessions is yours to make. The same pass covers “sold in the last hour” pop-ups and countdown timers, and the misrepresentation checker lists every urgency and social-proof check.
Typical evidence
Forty-seven shoppers on a store that gets eight a day
A “live viewers” counter asserts something about current traffic. If the number redraws on every load, treat it as wording to review rather than proof of real activity.
The public signals this check looks for:
“23 people are looking at this right now” on a store whose analytics show two visitors in …
“23 people are looking at this right now” on a store whose analytics show two visitors in that hour.
The same viewer number on a best-seller and on a product that has not sold in a year
The same viewer number on a best-seller and on a product that has not sold in a year.
A number that changes on every refresh, inside a fixed range, with no link to real session…
A number that changes on every refresh, inside a fixed range, with no link to real sessions.
A social-proof app still running its demo or sample data months after install
A social-proof app still running its demo or sample data months after install.
A count that keeps climbing at 3am, when the analytics say the store is empty
A count that keeps climbing at 3am, when the analytics say the store is empty.
A viewer pop-up that covers the price or the buy button on a phone
A viewer pop-up that covers the price or the buy button on a phone.
What it looks like once it is right
The counter is gone. The product page shows “148 reviews, 4.7 average” from verified orders, and anyone can open the review app and check the number.
Common mistakes
Common mistake
Fix checklist
Three reloads, three numbers to investigate
Repeated captures can show that a viewer count changes, but they cannot reveal the private analytics behind it. Compare the same timestamps with the merchant’s records.
Questions merchants ask
Are “people viewing this” widgets allowed on Google Shopping?
A true count is a true statement, and Google's Misrepresentation policy has no rule against real numbers. What it rules out is an offer that is not accurate, realistic and truthful. A count taken from a random range, demo data or a fixed setting is none of those, so it has no place on a page you send shoppers to from Google.
How do I know if my viewer counter is fake?
Look at its data source in the app settings. Demo, sample or random-range settings mean the number is invented. For a live setting, compare the counter with the real-time view in your analytics for the same product at the same minute. If they do not match, the widget is guessing.
What can I show instead of a viewer count?
Things you can prove. Google's Building trust page asks merchants to show reviews and testimonials about their products and business. A review count from verified orders, a verified-buyer label or a true dispatch time does the same reassuring job without inventing an audience.
Remediation
Risk signal
Similar cases
Sources
Community guidance
Written by Product Experts, the users Google recognises for their answers on its Merchant Center Community forum. Often stricter than Google’s help pages, and not Google policy.
Last reviewed 23 Sep 2026.
That is one issue. The library documents 134.
The free scan lists what it finds on your store. The paid report adds the affected pages, captured evidence and step-by-step fixes. Start free, with no account needed.