What feed monitoring is

The problem it solves

Your product feed is the file that tells shopping channels what you sell, for how much, and whether it is in stock. Your storefront is the page a shopper actually lands on after the click. The two are supposed to say the same thing.

They are edited by different hands at different times. A price changes in your admin. A stock sync from a supplier app lags, or stops working after an update. The feed and the page drift apart, and the channel spots it before you do.

What Rabbot checks

Rabbot cross-checks what your feed says against what your storefront shows, product by product. The comparisons that matter most:

• Price in the feed against the price on the page.
• Availability in the feed against whether the page can actually be bought from.
• Required identifiers, such as the barcode number a channel expects.
• Missing or empty product data that a channel treats as incomplete.

If a feed app sits between Shopify and the channel, the cross-check sees Shopify’s product data and the channel verdicts show what the channel decided. Neither one validates the feed app’s own rewrites.

When the two disagree, Rabbot raises it as disapproval risk. The gap is the kind of thing that gets a product pulled from a shopping channel. A cross-check finding comes from Rabbot’s own comparison, made while you still have time to close the gap. What the channel itself decided is the second layer, covered below.

Free plan and paid plans

Rabbot runs one feed cross-check on the day it installs. It is a one-time check as your store is set up, and adding a channel later does not trigger it again. On Free that single check is the whole of your feed checking: a taste of the paid sweep, free forever, no card required, and it usually finds something.

Continuous feed-integrity monitoring is the paid part. It sweeps your full catalogue daily and re-checks a product as soon as your store reports a change to it, so a gap that opens on a Tuesday is a finding on Tuesday, not a disapproval you discover three weeks later. Your plan sets how many channels you can monitor at once.

The channel’s own verdicts

Connect a channel in Settings and Rabbot also reads that channel’s own verdicts on your products once a day on paid plans. For Google that means products disapproved, products demoted, and items in review. For Meta it means products rejected, items in review, and data-quality issues. TikTok (Beta) reports catalog diagnostics and data-quality issues.

A critical verdict (a product Google disapproved or Meta rejected) reaches you the same day Rabbot reads it: one email on every plan, plus a Slack post on paid plans with Slack set up. Warnings from Google and Meta are emailed on paid plans. Every verdict appears in your dashboard and weekly digest, and your agent can read them over MCP. TikTok (Beta) diagnostics appear in the dashboard and digest only. On Free, Rabbot runs its own day-zero feed cross-check at install, a deterministic check that needs no channel connection. Connecting a channel needs Starter or above: on Free, the card in Settings shows See plans. The daily reading starts on Starter.

Channels

The Google and Meta (Facebook & Instagram) cards live in Settings. Choose Connect on the card for the channel you sell through. TikTok Ads (Beta) connects the same way, from its card in Settings alongside the other two. Beta means the channel is still being polished. The TikTok channel (Beta) covers it.

The Google channel covers both Google Merchant Center and Google Search Console on one connection, so Google, Meta, and TikTok (Beta) are the three channels today. Starter monitors one channel, Growth up to three, and Pro every channel, current and future. On Starter and Growth you can change which channels fill your slots once every 30 days. Reconnecting the channel you held most recently never counts against the 30-day rule. Switching which feed channel Rabbot watches has the rules. Each channel has its own article in this section.