Everything Rabbot watches.
Rabbot keeps a record for every page of your store. Each entry names the check that saw the change, when the problem opened, when it closed, and whether a fix was confirmed. On Growth and above, the entry also sets Shopify's own visit and checkout numbers beside the gap. Rabbot joins two views of your product feeds. It shows the verdicts Google, Meta and TikTok (Beta) give your products, read daily, beside what your storefront shows for price and stock. In September 2026 we found no app that continuously monitors the deterministic plumbing across page, Google, Meta, TikTok and agent channels and alerts on breakage. This page lists every check.
Free forever. No card required. Writes only when you tap.
Rabbot runs dozens of distinct checks on your store, on a schedule.
- 35checks it runs
- 3channels at launch
- $0forever, no card
Search and indexability.
Some changes remove your pages from search with no warning. Rabbot learns what each page tells Google, then watches for the change.
Page hidden from Google Critical
This page now tells Google not to list it, so it disappears from search and the organic clicks it brought in stop.
- Page hidden from Google
- Critical
- A meta tag, a header or a theme change can all do it.
- robots.txt changed
- Critical
- Canonical tag changed
- Warning
- The page tells Google another page is the original.
- Titles and descriptions
- Warning
- Sitemap not loading
- Warning
- Structured data broken
- Warning
- Redirect loops and growing chains
- Info
- Language and region tags broken
- Warning
Every search check, in full
SEO & indexability
Some changes remove your pages from search with no warning. Rabbot records every one and tells you which ones matter.
- Page hidden from Google
- Rabbot catches a page flipped to noindex before it drops out of search. A meta tag, a header, or a theme change can all do it.
- Canonical tag changed
- The canonical tag tells Google which version of a page is the master. A wrong one hands your ranking to another URL. Rabbot flags canonical changes on products, collections, and variants.
- Indexing signal changed
- Rabbot tells you when the reason a page stays indexed changes. The page can still look perfectly normal in a browser.
- robots.txt changed
- Rabbot watches robots.txt, the file that tells crawlers where they can go. One bad edit or error can block crawlers from your whole store.
- Sitemap not loading
- Your sitemap.xml is the map search engines follow. Rabbot alerts you when it stops responding.
- Rich results at risk
- Rich results are the extras Google shows under a listing, like stars and prices. Rabbot checks the Product, Breadcrumb, and Article markup behind them for missing required fields.
- Structured data broken
- Rabbot catches invalid structured data. It also flags schema types that appear or vanish after a theme change.
- Titles and descriptions
- Rabbot tracks your page titles and meta descriptions for unexpected changes. It also flags lengths that get cut off in search results.
- One tap puts a field back
- An SEO title, SEO description or search visibility (noindex) setting changed on you. Rabbot shows the value it had before, you confirm, and it goes back. Undo for 30 days. Starter and above.
- Heading problems
- Rabbot flags a missing or duplicated main heading on a monitored page.
- Language and region tags broken
- The set of language and region tags on a page changed from what it was before. Catches a Markets or translation app rewriting them without telling you. The validity of each tag is its own check, listed below.
- Hreflang integrity for international stores
- Stores on Shopify Markets, multiple languages, or a translation app all run hreflang tags. On every plan, each monitored page is checked for "Language or region tag invalid". That catches a bad language or region code, or a link that is not a full web address. Paid plans add a daily site-level sweep for two more: "Hreflang pages not linking back" and "Hreflang tag points to a broken page". Google ignores tags like these, so shoppers can land on the wrong country’s page. Rabbot alerts urgently when a previously-correct tag breaks, and confirms the fix on its next check.
- Large content changes
- Rabbot notices when a page changes a lot in one go. A jump that size usually means an app or a theme went wrong.
- Page needs JavaScript to load
- Rabbot warns you when page content moves into JavaScript. Search crawlers may never see it there.
- Image alt text missing
- Alt text describes an image to search engines and screen readers. Rabbot tracks it across your monitored pages.
Availability and the add-to-cart form.
A page can load fine and still be unable to sell. Rabbot reads three witnesses for every catch and tells you which ones agree.
The three witnesses, in the docsAdd-to-cart form missing Critical
The form is gone from the page's HTML. The theme script it needs returned 404 at 09:12.
Shopify's catalog for shopping agents still offers the product. Price and stock match.
Yesterday's visits against the same weekday in the four weeks before.
- Page returning an error
- Critical
- An error instead of content, on any plan.
- Add-to-cart button missing
- Critical
- A file the form depends on stops loading, or loads and fails a syntax check.
- Store-down heartbeat
- Critical
- Your homepage, about every 5 minutes, on every plan.
- Three witnesses for every catch
- Shopper numbers, the morning after
- Growth and Pro
Every availability check, in full
Availability & funnel
A page can load fine and still be unable to sell. That stays invisible until a shopper complains. Rabbot checks whether the page can still sell.
- Page returning an error
- A monitored page starts answering with an error instead of content. Rabbot treats this as critical on every plan.
- Storefront password-protected
- Your store shows the coming-soon screen instead of the storefront. Shoppers and crawlers are both locked out.
- Add-to-cart button missing
- The product page loads, but the one button that makes money is gone. Rabbot also checks that the code files the product form needs still load and are valid code. It says which file stopped and when.
- Broken product images
- Rabbot flags product images that stopped loading on your monitored pages.
- Insecure content on a secure page
- Browsers warn shoppers when a secure page loads something over plain HTTP. Rabbot flags it before that warning reaches your checkout path.
- Redirect loops and growing chains
- Rabbot catches redirect loops outright and flags chains that grow a hop at a time. On the finding, one tap points a chain straight at its end, or puts a loop’s earlier destination back.
- Product address shows Page not found
- A product’s web address changed and the old one shows Page not found. Keep the new address and Rabbot adds the redirect, or put the old address back. You confirm first, and you can undo for 30 days. Starter and above.
- Three witnesses for every catch
- Each finding shows what is broken, what Rabbot checked and when, and what shoppers did. Rabbot reports which witnesses agree and never guesses a cause.
- Shopper numbers, the morning after
- On Growth and above, Rabbot reads Shopify’s own shopper numbers once a day, after your day ends. It shows visits, cart additions and checkouts against the same weekday in the four weeks before. The card says when a store has too few visits to tell a real change from a quiet day.
- Broken links jumped
- Rabbot flags a sudden rise in broken links on a page, internal or outbound.
Store-down heartbeat
Some failures cannot wait for a scheduled check.
- Homepage checked about every 5 minutes
- Every plan gets this check, including the free plan. A store that is fully down raises one critical alert for the whole incident, not one alert per page.
The free day-0 audit.
You see what is already broken before you pay for anything. The first check runs the same day you install, on the 20 pages that matter most, and lands in the dashboard, never in an alarm.
Your first check, in the docsWhat the free audit includes
The free day-0 audit
You see what is already broken before you pay for anything.
- The day-0 audit
- The audit runs the day you install, on every plan, no card required. It shows what is already broken before Rabbot starts watching for what breaks next.
- One-time feed cross-check
- The day-0 audit includes one full feed cross-check of your chosen products. Paid plans run the same cross-check daily.
- Free forever
- Rabbot checks twenty pages of your choosing at least every week, daily when a page keeps changing. The day-0 audit and the weekly digest are included. Your homepage is always guarded.
Two feed checks.
Rabbot's own cross-check of your product data, and the verdicts from Google, Meta and TikTok (Beta), checked daily on paid plans. A disapproval reaches you the day the channel decides it.
A price that disagrees with your catalogue gets the product disapproved. Rabbot tells you before the channel does.
- Price mismatch
- Warning
- Availability mismatch
- Warning
- Missing product data
- Warning
- Identifier, brand, image, the fields a feed spec needs.
- Google Shopping verdicts
- Daily, paid plans
- Meta catalog verdicts
- Daily, paid plans
- TikTok catalog verdicts (Beta)
- Daily, paid plans
Every feed check and channel, in full
The feed cross-check
This is Rabbot’s own cross-check, the first of two separate feed layers. It compares the product data your feeds are built from (price, availability, required fields) against what your storefront actually shows shoppers, reading your storefront and your Shopify product data and nothing else. It never connects to your Google or Meta accounts to do this. The second layer, connected channel verdicts, is a different subsystem and entirely optional.
- Price mismatch
- Your storefront shows one price and your product data says another. That is the kind of gap that gets a product disapproved.
- Availability mismatch
- A product looks out of stock to shopping channels while shoppers can still buy it. The reverse happens too.
- Product page unreachable
- A product URL redirects, errors, or points at a draft. Any channel that follows it finds nothing.
- Missing product data
- Shopping channels require identifiers, brand, images, and descriptions. Rabbot finds the gaps in your product data.
Channel verdicts: Google, Meta, TikTok (Beta)
The second feed layer, and a separate subsystem from the independent cross-check. That cross-check needs no external account at all. Channel verdicts do: you add the channel in Settings to give Rabbot read access, and what that channel itself decided about your products then arrives every day. Optional, and off until you turn it on. Google and Meta are in Settings today. TikTok (Beta) connects the same way as Google and Meta. Beta means the channel is still being polished.
- Google Shopping verdicts
- Included at launch
- Rabbot shows Google’s own daily verdicts on your products: disapprovals, demotions, and items stuck in review. Each one comes with what to do next.
- Google Search Console
- Included at launch
- Search Console is Google’s own report on your pages. It confirms when a page dropped out of the index. Google publishes it with a lag, and Rabbot says so.
- Meta catalog verdicts
- Included at launch
- Rabbot covers Facebook Shops and Instagram Shopping. You see Meta’s own review results for your catalog: rejections, items stuck in review, and the data-quality issues that come before them.
- TikTok catalog verdicts (Beta)
- Included at launch
- Rabbot shows TikTok’s own catalog verdicts every day, beside Google’s and Meta’s. TikTok is the newest channel and it carries a Beta label. It connects the same way as Google and Meta, from the TikTok Ads card in Settings. Beta means the channel is still being polished. Give it a slot when TikTok is the only place your products sell. On Growth and Pro it runs alongside Google and Meta rather than in place of them.
- Channel slots that scale
- Included at launch
- Your plan sets how many channels run continuously. A downgrade pauses a channel. The findings and history Rabbot already recorded for it stay, read-only.
Site signals and tracking tags.
Nothing here breaks all at once. A theme update drops a pixel, an app rewrites a sharing image, and nobody notices until a report looks wrong.
- Tracking tag missing
- Warning
- The analytics tag or the pixel, usually after a theme or app update.
- Internal links dropped
- Page no longer linked
- Page buried deeper in your store
- Large content changes
- Warning
- A page that lost most of its text since the last check.
- Storefront password-protected
- Critical
- Your store behind a password wall, by accident.
Every signal check, in full
Site signals & tracking tags
Nothing here breaks all at once. Rabbot watches link structure, crawl depth, and the tracking tags a theme update can drop.
- Page no longer linked
- A page lost its last internal link. It is still live, but nobody can reach it by browsing.
- Internal links dropped
- A monitored page loses the internal links that gave it weight in search.
- Page buried deeper in your store
- A page now takes more clicks to reach than before.
- Tracking tag missing
- A monitored page lost its analytics or pixel tag. A theme or app update is the usual cause. Rabbot closes the alert itself when the tag comes back.
- Rabbot tells you when it is blocked
- If Rabbot cannot check a page, it tells you. Silence never stands in for a clean result.
Alerts without the noise.
An alarm you learn to ignore protects nothing. Rabbot warns you once per change, in plain words, with the page and the fix, and goes quiet until something new happens. One email a week shows the work.
Why Rabbot warns you onceCritical: a page is hidden from Google
/products/weekly-mug was set to noindex at 02:04 UTC. Google will drop it from search. Rabbot can put it back with one tap, and will re-check and confirm.
Open the findingEvery alert rule, in full
Alerts without the noise
An alarm you learn to ignore protects nothing. Every Rabbot notification rule exists to keep the one honest alarm believable.
- Plain-English alerts
- Every alert says what broke, on which page, why it matters, and what to do. It carries the before-and-after values and a link to the exact spot.
- One alert per finding, reminders only for sales blockers
- Each finding alerts you once. Only a finding that blocks sales is chased, on a slowing schedule, until it closes. One bad incident means a handful of emails, never a flood.
- Storm rollup
- When many things change at once, Rabbot sends one summary. The rest waits in the dashboard and the weekly digest. You hear about it once, not forty times.
- Dismiss as intentional
- Mark a change as deliberate per finding from the dashboard. Your agent can dismiss a change type store-wide over MCP, and Settings lists every store-wide dismissal so you can revoke it. Rabbot keeps watching and alerts in full if it changes again. You cannot dismiss a sales-blocking issue, with two documented exceptions: a deliberate password gate or a custom purchase flow.
- Severity that respects your inbox
- Critical issues alert the same day on every plan. Warnings alert the same day on paid plans and wait for the weekly digest on the free plan. Informational findings go in the digest and never page you.
- Slack alerts
- On paid plans, Rabbot posts critical catches to your Slack channel the same day. Warnings and informational findings stay out of Slack.
The weekly digest
One email a week shows the work: what Rabbot caught, what you closed, and what is still open.
- The weekly digest, on every plan
- The digest groups every catch by the channel it threatened. It shows what opened, what closed, and what still waits on you. A clean week says so plainly.
Ask it, keep it, trust it.
Every answer Rabbot has is available to Shopify Sidekick and to any MCP client. Every catch and every tap stays in a history you can undo from. And the worst case is boring by design.
Rabbot answers inside Shopify Sidekick, and speaks MCP to any agent you already use.
Fifteen tools, plainly named. Thirteen reads and two guarded writes.
Every change and issue Rabbot has recorded stays in your history.
Seven days on the free plan, the full record on paid plans. Every tap can be undone for 30 days.
Three read permissions at install. Write access only when you tap, through Shopify's own prompt.
No customers, no orders. Tokens encrypted, data in the EU, erased after uninstall.
Agent access, history and privacy, in full
Agent access: Sidekick and MCP
Rabbot answers inside Shopify Sidekick, the assistant built into your Shopify admin. Every answer comes from Rabbot’s own checks. Rabbot only reads there: asking Sidekick changes nothing in your store. Rabbot runs its own MCP server too, so any MCP-capable agent can query the same records once you mint a token.
- Ask Sidekick inside the Shopify admin
- Ask Sidekick what is broken on your store. It answers what is blocking sales too, and why one product page cannot sell. Ask how to fix a named check and the answer names the admin screen to open. Every answer describes Rabbot’s last completed check, so nothing is crawled while you wait. Rabbot never tells Sidekick what Google, Meta or TikTok (Beta) reported about your products. It holds no order data at all. An empty answer is never an all-clear: every reply says how many pages and checks it covered, and what is still open elsewhere.
- A real MCP server, fifteen tools
- Mint a scoped, revocable token and any MCP-capable agent can query Rabbot.
whats_blocking_salesnames what is stopping a sale right now.get_url_timelinereturns a page’s history: last 7 days free, full history on paid plans. Connecting the agent is free on every plan. - Two write actions, guarded
dismiss_findingmarks a finding as intentional so Rabbot stops flagging it, store-wide or one page at a time. It refuses on anything blocking a sale, with two documented exceptions: a deliberate password gate or a custom purchase flow.fix_undoreverses a fix Rabbot made. An agent can preview a fix withfix_previewand can never apply one: that takes your two taps in the app.- A verdict, not a row count
- A generic integration built on raw store data returns a list. Rabbot’s MCP returns what broke, what is blocking a sale, and history no fresh integration can rebuild, because Rabbot already recorded it.
Guarded history
Every change and issue Rabbot has recorded stays in your history. Routine all-clear check records are pruned after about a month.
- A guarded history for every URL
- Rabbot keeps a per-page timeline. It records every change, every problem, and every confirmed fix. An upgrade reveals everything it already recorded.
- Fixes confirmed, not assumed
- Rabbot re-checks automatically and records when a fix is verified. You get receipts, not vibes.
Private by design
Rabbot is built so the worst case is boring.
- Read-only install, writes only on your tap
- Installing Rabbot grants three read permissions. Write access is asked the first time you tap a fix, through Shopify’s own prompt. Rabbot never writes on its own and never touches your theme.
- No customer data, ever
- Rabbot never touches orders, customers, or checkout data. Switch the revenue line on and it reads daily sales totals from Shopify’s own reports, nothing per customer, kept 90 days. It puts no pixels on your storefront.
- EU-hosted and encrypted
- Your data lives in the EU and tokens are encrypted at rest. Uninstalling purges your data after Shopify’s redaction window.
- A crawler that signs its name
- Rabbot’s crawler identifies itself. It cryptographically signs every request to your storefront.
See what's already broken on your store.
No card required. One-click install.