Your first check

When the first check runs

Your first check runs the same day you install Rabbot. It works through the pages on your monitored list: the 20 Rabbot starts you with on Free, or, on a paid plan, whatever automatic discovery has found so far, so a large store may see that list still filling in while the check is under way. You do not need to trigger anything: it starts on its own.

What Rabbot looks at

Rabbot compares each page against what it expects a healthy page to look like: page headings, meta descriptions, canonical tags, product data, the add-to-cart button, and whether the storefront itself is reachable, among other checks. It is not grading your writing or your design. It is looking for the kind of change that quietly stops a page from selling or from being found: a heading that vanished, a canonical tag pointing at the wrong page, product data gone missing.

Reading the result

When the first check finishes, the top of the dashboard shows a status word (for example AT RISK), a score, and a line stating how many URLs are guarded, how often they are checked, and when the last full check ran.

Below that is one card per problem Rabbot found. Each card carries:

• A plain name for the change, such as Canonical tag changed or Meta description changed.
• A severity chip: critical, warning, or info.
• How many pages the change affects.
• A short explanation of what it means for your sales, in plain words rather than SEO jargon.

Choose Show affected pages on any card to see the exact URLs and the raw detail behind the finding.

A first check is not a verdict on your store

Stores that have never been monitored often show more findings on day one than they will see again. Some of it will be real: an old canonical tag, a heading a theme change wiped out months ago. Some of it will be deliberate, a page you meant to keep out of search. What critical, warning, and info mean and Dismiss as intentional cover how to sort the two apart and quiet the ones that are on purpose.

What alarms on day one, and what does not

Some checks watch for change by definition; their first visit just learns what your store looks like.

If your store is already broken when Rabbot arrives, day one’s findings say so in the dashboard, quietly. Alarms are reserved for things that change on your watch. The install-day feed audit works the same way: its findings land in the dashboard, in MCP, and in the weekly digest, never in an alert email.

A dead store, a page Google is told not to index, or a price that disagrees with your catalogue is urgent whether it broke today or last month: those alert from the very first check.

What happens next

After the first check, Rabbot settles into its normal cadence. On a paid plan it picks up a product change in your store and re-checks that page shortly after, sweeps your full catalogue daily, and runs its channel checks daily, so you hear the same day a change causes a problem. On Free, checks run weekly.