What Rabbot checks, and what counts as an issue

What a check is

Rabbot visits your monitored pages on a schedule, reads what is there, and compares it against what it saw last time. When something worth telling you about is different, it writes a finding. A finding is one card on your dashboard: a title, a severity chip, the pages it touches, and a plain explanation of what changed and why it matters.

The kinds of problems Rabbot looks for

Most findings fall into a handful of groups.

Pages that stop working. A monitored URL starts answering with an error, or your whole storefront goes down. This is the most urgent kind, because a shopper hits it too.

Pages that block a sale directly. Things like a missing add-to-cart button or a storefront that has gone password-protected. A shopper cannot buy while these stand. Those two can also be deliberate, a pre-launch password gate or a custom purchase flow of your own, so they are the sale-blocking findings Rabbot will accept a dismissal on.

Search and metadata problems. A changed page heading, a missing meta description, a canonical tag that points somewhere wrong, missing product data, or a broken hreflang tag. None of these stop a sale today. Left alone, they erode how well your pages show up in search over time.

Feed and channel disapproval risk. Rabbot cross-checks your product feed against what Google, Meta, and TikTok Ads (Beta) expect, and flags product data likely to trip their rules. Read more in the feeds category.

Sales-blocking versus traffic-eroding

Findings sort broadly two ways. Some block a sale: a shopper hits them right now and cannot buy. The rest do not stop a sale today, and most of those erode traffic instead: nothing is broken for a shopper, but the page slips in search results the longer it stands. The severity chip (critical, warning, info) tells you whether something broke. Which way a finding sorts tells you what it costs you if you leave it. Read the plain explanation on each card, it says which in plain words.

What is not an issue

Rabbot only writes a finding when something is worth your attention. A page that has always looked the same way does not generate new findings just because Rabbot keeps checking it. Content you changed on purpose is not a problem either, and you can tell Rabbot that directly (see Dismiss as intentional) so it stops repeating itself on that one item.

Where to go from here

Open the Critical tile first if it shows anything above zero. From any finding card, choose Show affected pages to see the URLs involved, and read What critical, warning, and info mean for how Rabbot ranks what needs you today against what can wait.