Rabbot

Everything Rabbot watches.

Rabbot runs dozens of distinct checks on your store, on a schedule. It tells you the same day one of them finds a problem. This page lists every check.

Example alert, illustrative data:

Canonical tag changed

Page /products/sample-hoodie

Before canonical → /products/sample-hoodie

After canonical → /products/sample-hoodie-copy

Resolved Confirmed by re-check.

Illustrative example, not a real store.

day 0

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 every week. The day-0 audit and the weekly digest are included. Your homepage is always guarded.

the checks

What Rabbot checks.

SEO & indexability

14 checks

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.

10 more checks

  • 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.

  • 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 & funnel

7 checks

A page can load fine and still be unable to sell. That stays invisible until a shopper complains. Rabbot checks the path to a sale itself.

  • 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.

  • Broken product images

    Rabbot flags product images that stopped loading on your monitored pages.

3 more checks

  • 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. It also flags chains that grow a hop at a time.

  • Broken links jumped

    Rabbot flags a sudden rise in broken links on a page, internal or outbound.

The feed cross-check

4 checks

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.

Site signals & tracking tags

5 checks

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.

1 more check

  • Rabbot tells you when it is blocked

    If Rabbot cannot check a page, it tells you. Silence never stands in for a clean result.

always on

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.

Illustrative ping pattern.

channel verdicts

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 support is in Beta and currently open to a limited pilot, so the TikTok Ads card is there for stores in the pilot.

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. Support is currently open to a limited pilot, so the TikTok Ads card appears in Settings for pilot stores. 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.

alerts

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.

  • First alert same day, reminders back off

    The first alert always goes out at once. Reminders for a still-open issue slow down on a schedule. 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

    One click marks a change as deliberate, per page or store-wide. 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. Minor findings wait for the weekly digest. Nothing informational ever pages you.

  • Slack alerts

    On paid plans, Rabbot posts catches to your Slack channel the same day.

Illustrative inbox, not a real store.

the digest

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.

Illustrative digest, not a real store.

agent access

Agent access

Rabbot runs its own MCP server, not a generic wrapper around your store’s raw data. Any MCP-capable agent can query it once you mint a token, and every answer comes back as a verdict, not a row count.

  • A real MCP server, nine tools

    Mint a scoped, revocable token and any MCP-capable agent can query Rabbot. whats_blocking_sales names what is stopping a sale right now. get_url_timeline returns a page’s history: last 7 days free, full history on paid plans. Connecting the agent is free on every plan.

  • One write action, guarded

    dismiss_finding mutes a finding you already marked intentional, 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. It never needs a reason.

  • 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.

See every tool and how to connect an agent.

Illustrative MCP exchange.

history

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.

privacy

Private by design

Rabbot is built so the worst case is boring.

Read-only by design

Rabbot can read your products, content, and themes. It cannot change any of them.

No customer data, ever

Rabbot never touches orders, customers, or checkout data. It puts no pixels on your storefront. There is nothing to leak.

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.

Install Rabbot and your first audit runs the same day. Free forever, no card required.

Add to Shopify, free foreverAdd to Shopify

Free forever · no card required · read-only