Dismiss as intentional: telling Rabbot a change was on purpose
How to stop Rabbot alerting on a change you made deliberately, what dismissal does and does not do, and which findings refuse it.
Why this exists
Some findings are not mistakes. You rewrote a meta description on purpose, or you swapped a canonical tag as part of a redesign. Rabbot cannot always tell a deliberate change from an accidental one, so it flags both the same way. Dismiss as intentional is how you tell it which is which, without Rabbot forgetting to watch the page.
How to dismiss a finding
Open the finding card and choose Show affected pages. Each row lists the URL and the raw detail of what changed. Choose Dismiss as intentional on the row that matches what you meant to do. Rabbot stops alerting on that specific change and keeps checking the page as normal.
What dismissal actually does
Dismissing a finding mutes the alert. It does not close the finding and it does not fake a fix. The underlying state stays exactly as it was, Rabbot just stops repeating itself about something you already know. If you later repair the thing properly, so it matches what Rabbot expects, the finding closes on its own and the dismissal falls away with it. If the same problem comes back after that, a fresh change on a page that was fine, Rabbot alerts you again. Dismissal never turns off watching, only the noise on one already-known change.
What cannot be dismissed
Rabbot keeps a small set of sale-blocking findings out of reach of the dismiss button. A page answering with an error, or a storefront that is down, refuses dismissal by design. Rabbot will not let you silence something a shopper is hitting right now. Fix these rather than mute them; there is no button that makes them go away without the page actually working again.
Two of that set are documented exceptions, because both are things a merchant does on purpose. A storefront sitting behind a password is often a deliberate pre-launch gate. A product page with no standard add-to-cart form is sometimes a custom purchase flow you built in JavaScript yourself. Rabbot accepts a dismissal on those two. Dismiss one and it drops out of the Blocking sales now area of your dashboard, and out of the answer an agent gets back when it asks what is blocking sales. A dismissal on a single finding clears itself when the problem is repaired, so if the same thing breaks again later, Rabbot alerts you as normal. A store-wide dismissal is different: it stays in force until you re-enable that change type from the Dismissed change types card in Settings.
Where dismissals are listed
The Dismissed change types card in Settings lists store-wide dismissals, the kind an agent makes through Rabbot’s MCP server to mute a change type across your whole store. A dismissal you make on a single row from the dashboard is not listed there. Either way, a dismissal only covers the change you dismissed, not every future change on that page, so if that page breaks in a new way Rabbot still tells you.
A common mix-up
Dismissing is not the same as fixing. A dismissed finding drops off your dashboard and stops sending alerts, but the state you dismissed is untouched: the card going away is your own instruction, not a repair. Dismissal is for keeping your dashboard honest about deliberate choices, not for clearing a backlog you have not actually worked through.
Still stuck? Email support@rabbot.ai and a real person reads it.