Audit the site on a schedule
BetaHave Scout audit your site every night or every week, and see what changed since the previous audit.
Scout can audit your site on its own at a time you pick, every day or once a week. Each audit is compared with the previous one, so you see the problems that appeared and the ones that went away.
Before you begin
- You need the Editor, Admin or Owner role.
- Set the project's Site URL in Settings > Project settings. Scout audits that address.
Audits spend tokens
Set up a scheduled audit
Turn on the schedule
Open Flamio Scout. On the Release checks card, turn on Audit the site on a schedule.
Pick when
Select the Frequency — Daily or Weekly — then the Day of a weekly audit, the Time and the Time zone. The time zone starts as yours. The line under it reads "Next audit of" your site and when.
Check the monthly budget
Scheduled audits spend from the Monthly Scout budget (tokens) on the same card, together with release checks and pipeline checks. An audit the month has no room for is skipped, not started.
Follow each audit
Each scheduled time appears in the list under the schedule with what Scout did:
| Label | Meaning |
|---|---|
| Audited | Scout audited the site. |
| Skipped — monthly budget reached | The month's budget had no room for the audit. |
| Skipped — the previous audit was still running | An audit of the same site was still running. |
| Skipped — set the project's Site URL in Settings | The project has no site address to audit. |
| Could not start — check the token balance and the Site URL | The organization's balance could not cover the audit, or the site could not be reached. |
Click Open audit to open that audit's report.
Result
The audit's report opens with "Scheduled audit of" and the date, linked to the previous audit. Findings the previous audit did not report carry Not in the previous check. Two audits of an unchanged site can differ, so this label is a pointer, not proof that a change introduced the problem.
A scheduled audit does not mark earlier problems fixed: two audits of a site that did not change can differ, so a problem it does not find again is not proof of a fix. A release check marks the problems it no longer finds, and you can mark one fixed yourself.
The first audit has nothing to compare with. It is marked as the first in the list, and the next audit compares with it.
To stop, turn off Audit the site on a schedule.