Monitoring
Scan it once, then keep scanning
A one-off audit tells you where a site stood on a Tuesday. What you usually want to know is whether it is getting worse - which needs the same scan, repeated, and something to compare it against.
An alert for a regression, not for a scan
A monitor that mails you every time it finishes teaches you to filter it out within a fortnight. Ours compares the run that just completed against the one before it and sends nothing unless something got worse - a new finding, a severity that climbed, a score that dropped.
Which means a quiet inbox is information: it says the last run found nothing new, not that the schedule stopped.
What a comparison refuses
Two runs are only comparable if they covered comparable ground. A scan that crawled 40 pages and one that crawled 400 would show a wall of “new” findings that are not new at all, so the comparison is refused rather than drawn.
The crawl is level-synchronous and deterministic - the same site scanned twice returns the same pages in the same order - which is what makes the comparison worth anything in the first place.
Cadence
How often a plan can schedule
Read from the same table the scheduler enforces, so this page cannot advertise an interval the engine refuses to run.
As often as weekly
weekly, monthly - and 90 days of history, which is what a regression is measured against.
As often as daily
daily, weekly, monthly - and 12 months of history on Pro, 24 months of history on Super and Agency, Custom of history on Enterprise, which is what a regression is measured against.
On demand
Scans run when you start them and their history is kept; the scheduler is not part of the free tier.
Retention matters here as much as the interval: a run that has aged out of the window cannot be the thing the next one is compared against, which is why the two move together on the pricing table.
What you get back
What appeared
Findings present in the new run and absent from the last one, with the evidence that produced each.
What went away
Findings the previous run raised that this one did not - the half of a comparison most tools drop.
What got worse
A severity that climbed or a category score that fell, which is the only condition that sends mail.
What was not measured
Categories the run could not measure are reported as unmeasured rather than scored clean, in the comparison too.
Related guide
The website audit checklist, in the order that actually pays
What to check on a website and in what order: what decides whether it is secure, fast, indexable and usable - and the questions no external scan can answer.
Read the guide →Start
Run one audit first
A schedule is worth setting once you have seen what the first run says. The first one is free and needs no account.