Invalid clicks on Google Shopping: feed, scrapers, and CPC waste
Product feeds attract scrapers as fast as shoppers. A practical checklist for spotting junk Shopping clicks before they distort ROAS and inventory decisions.
Topics
Why Shopping is a magnet for scrapers
Price and availability pages are useful to competitors and automated tools. Those visits can register as paid clicks when Shopping ads are the entry point — then leave zero purchase intent behind.
Because item-level reporting is busy, junk can hide inside healthy product groups until margin reviews expose the leak.
New listings and sudden price drops are especially attractive. Scrapers arrive within hours of a public change, often before organic discovery catches up.
PMax Shopping surfaces amplify the problem: channel mix is opaque, so scraper waste looks like “the feed underperformed” when the real issue is traffic quality.
Competitor price tools are not always malicious in intent, but they are still not shoppers. Paying CPC for their crawls is optional once you can see them.
Marketplace sellers monitoring your prices create similar patterns. Treat monitoring traffic as a protection problem, not a merchandising insult.
Patterns worth a saved view
Look for bursts on newly listed SKUs, identical behavior timelines across many products, and high-risk sessions that never reach cart or PDP engagement milestones.
Holiday feed expansions amplify both real demand and scrapers. Revisit defaults before major catalog pushes.
Identical bounce timing across dozens of products from the same ASN is a stronger tell than a single soft ROAS day.
Mobile carrier noise can look suspicious on retail sites. Keep a watchlist for borderline cases instead of mass-blocking ranges that also carry real shoppers.
Tag promotional SKUs in your views before a sale starts. You want the scraper baseline ready before the volume arrives.
Compare desktop and mobile junk share separately. Some scrapers skew hard to one surface and vanish in blended totals.
- Bursts on newly listed or repriced SKUs
- Identical timelines across many products
- High risk with zero cart or PDP depth
- ASN spikes after feed pushes
- Overnight scrapers on brand-heavy titles
Protect the catalog without hiding winners
Block clear junk IPs first. Keep a watchlist for borderline mobile carrier noise that can look suspicious on retail sites.
Share weekly junk share by product type with merchandising. When a category is mostly scanners, the fix may be feed hygiene as much as media.
Do not pause a winning SKU because ROAS dipped during a scraper wave. Exclude the junk, then re-evaluate the product on cleaner traffic.
Separate brand and generic Shopping structures when you can. Brand terms often attract competitor monitoring; generics attract price scrapers. Different patterns need different saved views.
When a hero SKU looks soft, pull junk share before you rewrite the title. Many “dead” products revive on cleaner traffic.
Tie feed ops to media ops
When a new brand or price drop hits the feed, tell the media buyer the same day. Scrapers often arrive within hours of public price changes.
A shared calendar of feed pushes and promotion windows makes those spikes explainable.
Include title and image changes in the same calendar. Creative refreshes can coincide with junk spikes and produce the wrong creative post-mortem.
Ask merchandising for a “watch these SKUs” list before big launches. Pre-building a risk view beats discovering waste in the monthly ROAS review.
A fifteen-minute standup after big feed pushes beats a two-hour autopsy later. Make it a habit for peak season.
Metrics that matter for Shopping protection
Track junk share of paid Shopping sessions, excluded IP growth, and engagement on remaining PDP visits. When junk falls and PDP depth rises, protection is working.
Compare ROAS on a fourteen-day window before and after a major exclusion wave. Single-day Shopping noise is legendary; multi-week windows are fairer.
Export the top junk ASNs monthly for finance. Even without a platform credit, the packet shows stewardship of catalog spend.
Include excluded-audience growth next to IP list size. Rotation-heavy scrapers show up there first.
A weekly Shopping protection checklist
Monday: open high-risk Shopping sessions and promote clear scrapers to the exclusion export.
After every major feed push: skim the new-SKU view for twenty-four hours and note any ASN bursts.
Month end: send merchandising a one-pager — junk share by category, exclusions added, SKUs that looked soft only while scrapers were active.
If any of those habits slip for two weeks, reinstate them before you blame the feed or the bid strategy.
Archive the monthly merchandising one-pager. Seasonal patterns become obvious when you can flip back a year.
Peak season without peak waste
Before a major sale, pre-build saved views for new SKUs, promotional categories, and overnight sessions. Scrapers love the same windows merchandising loves.
Agree with feed ops on a same-day ping when prices drop publicly. Hours matter more than decks when automated tools notice a change.
Cap how many Shopping IPs you exclude in a single day during peak unless the pattern is overwhelming. False positives during high demand are expensive.
After the sale, send merchandising the junk-share-by-category note while memories are fresh. Next year’s playbook writes itself from those notes.
Remember that ROAS dips during scraper waves are not always creative failures. Clean the traffic, then judge the product on what remains.
