What critical, warning, and info mean
Rabbot sorts every finding into three levels so you know what to fix first and what can wait.
Three levels, in order
Every finding Rabbot shows you carries one of three severity chips: critical, warning, or info. The dashboard sorts by them, and the Critical and Warnings tiles at the top count them for you. The order is the whole point: it tells you what needs you today and what can wait.
Critical
Critical means something that was healthy has broken. Rabbot saw the page working on an earlier check and sees it failing now. A monitored page that starts answering with an error is critical on every plan, the free one included. A store that goes fully down raises one critical alert for the whole incident rather than one per page.
A fresh break is the thing worth stopping for. If the Critical tile shows anything above zero, open that first and leave the rest of the list alone until it is closed.
Warning
Warning means the state is wrong, but it did not break today. Either it has been that way since before Rabbot started watching, or it has held the same way check after check.
Nothing broke today, so a warning rarely needs you this hour. Left alone for a month, though, this is how a page slides down the results and stays there.
Info
Info is a record, not a request. Rabbot noticed a change, it costs you nothing that Rabbot can see, and it sits there so you have the history when you need it. Reading the info items once a week is enough.
Severity is not the same question as cost
Severity says whether something broke. It does not say what it costs you. Some findings stop a shopper buying. Others erode your search traffic over time. Those are a separate axis, and the two cross: a finding can be critical and still be a slow traffic problem rather than a blocked checkout. Read the plain explanation on the card, which says what the change means for your store, before you decide the order you work in.
Working the list
Go top down. Open a card, read the plain explanation on it, then choose Show affected pages to see which URLs are involved and what changed on each one.
If a finding is something you did on purpose, choose Dismiss as intentional on that row. Rabbot stops alerting on it and keeps watching. Two things worth knowing about that: anything blocking a sale refuses to be dismissed, by design, apart from two documented exceptions that can genuinely be intentional (a deliberate password gate and a custom purchase flow), and a dismissal never fakes a close. Repair the underlying thing and the finding closes on its own, the dismissal falls away with it, and if it breaks again after that Rabbot tells you again.
One last thing: severity is Rabbot’s judgment about the state of the page, not about how hard the fix is. A critical finding is sometimes a single click in your theme settings. A warning sometimes takes an afternoon. Fix in severity order anyway, because a fresh break costs you for every day it stands.
Still stuck? Email support@rabbot.ai and a real person reads it.