high
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
Your products break in Google Shopping. Silently.
FeedWarden is feed-health monitoring for Shopify stores that sell on Google Shopping. It only reads data and never writes to your catalog or feed.
It compares your Shopify catalog with Google Merchant Center, detects catalog and page mismatches, and tells you what broke, which products it hit, what it costs you, and who has to fix it.
App Store listing pendingSee a sample incident
Open incidentslast scan 06:00 · 312 products checked
high
1 offer submitted by conflicting datasources
£680 at riskmedium
Sale price stale in GMC on 3 items
£1,215 at riskevidence packet ready · download markdown / json
known failure modes · observed weekly across merchant forums
This is how it usually goes.
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
Watches the gap. Changes nothing.
Connect in minutes. FeedWarden only performs reads and never changes your catalog or feed. Keep the setup you already have while it monitors the official channel, feed tools, XML feeds, and Merchant API sources side by side.
watched sources · behavior: read requests only
- Google & YouTube channel
- Feed tool (API source)
- Supplemental XML feed
Incidents with a timeline, not a health score.
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
- Jul 3, 06:00 last known good
- Jul 5, 23:19 disapproved: page unreachable
- Jul 6, 06:00 still down · not spreading
- pending resolves when Google recovers
Catches feed sources fighting over your products.
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
Google & YouTubeSupplemental feed
price flipped £699.95 → £649.95 · image dropped
Checks your product pages the way Google's crawler does.
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
- ✓HTTP 200 in 412 ms
- ✓robots.txt allows Googlebot
- ✕302 → /password · access wall
- –schema parity: unreachable
Ranks every incident by revenue at risk.
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
Ends the support runaround with an evidence packet.
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 staged sample 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
The first scan is the audit.
step 01 · connect
Connect
Shopify install plus Google sign-in. FeedWarden only reads Merchant Center data and does not make feed changes, but Google's content permission can technically allow writes.
step 02 · scan
Scan
FeedWarden compares eligible catalog rows within the supported limits, checks the highest-priority live product pages up to your plan's per-scan limit, and builds your baseline.
step 03 · know
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 through external alerts on Protect and Command.
alerting · thresholds you control
Alerts fire on meaningful breakage.
No daily noise digest, no inbox with 97 warnings. Each alert names the problem, the scale, and why it matters, with thresholds you can tune on Protect and Command.
Conflicting feed sources detected
1 offer is submitted by more than one datasource. Conflicting sources overwrite each other and cause unexplained data flips.
Sale price stale beyond your sync window
3 items still show an old price in GMC past the 24h window. Price mismatch is a fast path to disapproval.
GMC product count dropped sharply
Product count fell 12.5% since the last scan. 3 active products are no longer served to Google surfaces.
questions merchants ask before installing
Fair questions.
Does it change my feed?
No. FeedWarden only performs reads and does not modify your catalog, feed, or Merchant Center data. Shopify grants read-only scopes; Google's Merchant Center content scope can technically allow writes, but FeedWarden does not use that capability.
Does it replace my feed app?
No. It watches whatever you already use: the official channel, a feed tool, XML feeds, or Merchant API sources. Keep your setup.
What if I only use the official Google channel?
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.
How fast will I know when something breaks?
Scheduled scans run continuously, and product changes flag your catalog for the next pass. Typical detection is within one scan cycle.
What does it need access to?
Shopify: read_products and read_orders, with no Shopify write scopes. Google: the Merchant Center content scope. FeedWarden only reads items, statuses, and data sources, although Google's scope can technically allow writes.
next scan · yours
Your feed broke at some point this quarter.
Find out if it is broken right now.
The first scan is the audit. Install, connect, and see the mismatches FeedWarden detects between Shopify and Google.
App Store listing pendingSee pricing