24 items disapproved or limited in GMC
£3,940 at risk- Root cause
- Product page unreachable to crawler
- Fix owner
- Theme / product page
- First detected
- Jul 5, 23:19
- Status
- open
incident detected · 23:19 · 24 items affected
FeedWarden watches your Shopify catalog and Google Merchant Center side by side, catches every mismatch, and tells you what broke, which products it hit, what it costs you, and who has to fix it.
Read-only access · works with any feed setup · five-minute connect · 14-day free trial
evidence packet ready · download markdown / json
known failure modes · observed weekly across merchant forums
Tuesday, 9:14 AM
Your Performance Max spend is up, sales are down. Twelve of your best sellers quietly dropped out of Google three days ago. Nothing told you.
Sale weekend
Shopify shows the discount. Google still shows the old price. Google flags the mismatch and suspends the products mid-promotion.
The ticket loop
Google says “product page unavailable.” The page opens fine on your phone. Support asks for evidence you do not have, then points you back to Shopify.
None of this shows up in your Shopify admin.
All of it shows up in your revenue.
Plenty of tools will build you a feed. Almost nothing watches what happens to it after. The gap between synced and selling is where your money disappears, and that gap is exactly what FeedWarden monitors.
capabilities · six reasons the gap stays closed
Connect in minutes with read-only access. Keep the feed setup you already have; FeedWarden monitors the official channel, feed tools, XML feeds, and Merchant API sources side by side.
watched sources · access: read-only
Every problem opens as an incident: first detected, last known good, still spreading or contained, resolved only when Google actually recovers. You see what changed and when, not a number that drifted.
incident timeline · offer shopify_GB_…_5418
When two sources submit the same product, Google silently picks a winner and your titles, prices, or images flip overnight. FeedWarden detects the takeover and names both sources in plain English.
source takeover · detected between scans
price flipped £699.95 → £649.95 · image dropped
Redirect chains, robots rules, canonical tags, structured-data price and stock parity, image availability. Built for the incident where the page loads fine for you and Google still says unavailable.
pdp crawl check · /products/alpine-jacket
Each incident shows the 30-day revenue of the products it touches, in your currency. You fix the £3,940 problem before the £12 one.
open incidents · ordered by 30-day revenue
One download: Shopify's value, Google's value, what the live page says, the crawl result, timestamps, and the recommended fix owner. Paste it into any support ticket and skip three rounds of “please provide more details.”
Download a real packetevidence-packet.md
## Affected items
| Field | Shopify says | GMC says |
|------------|--------------|----------|
| sale_price | 785.95 GBP | 939.99 |
Suspected source: stale sync
Fix owner: feed app
First detected: 2026-07-05 23:19 UTCsetup · from install to first finding in about an hour
step 01 · connect
Shopify install plus a read-only Google sign-in. No feed changes, no code, nothing to migrate.
step 02 · scan
FeedWarden compares every variant against every Merchant Center item, checks live product pages, and builds your baseline within the first hour.
step 03 · know
Scheduled scans plus alerts from then on. When something breaks you get the incident, the cause, the cost, and the fix. In the app and in your inbox, or in Slack and Discord on the Command plan.
alerting · thresholds you control
No daily noise digest, no inbox with 97 warnings. Each alert names the problem, the scale, and why it matters, with thresholds set per store.
1 offer is submitted by more than one datasource. Conflicting sources overwrite each other and cause unexplained data flips.
3 items still show an old price in GMC past the 24h window. Price mismatch is a fast path to disapproval.
Product count fell 12.5% since the last scan. 3 active products are no longer served to Google surfaces.
questions merchants ask before installing
No. FeedWarden is read-only by design; that is the point. It observes your catalog and Merchant Center and never writes to either.
No. It watches whatever you already use: the official channel, a feed tool, XML feeds, or Merchant API sources. Keep your setup.
Then you have sync but no diagnosis. When something breaks, the channel tells you it synced. FeedWarden tells you what actually changed, where, and why.
Scheduled scans run continuously, and product changes flag your catalog for the next pass. Typical detection is within one scan cycle.
Shopify: read products and orders. Google: read Merchant Center. Nothing else, and nothing with write permission.
next scan · yours
The first scan is the audit. Install, connect, and see every mismatch between Shopify and Google in about an hour.