Monitoring schedules per plan
Each project has monitors; the Monitoring tab shows them with their next run.
| Monitor | What it does | How often |
|---|---|---|
| Light scan | a quick look for new problems: headers, certificate, email DNS, the riskiest files and scripts that changed | daily (Agency every 6 hours), and after each deploy with the deploy hook |
| Full scan | every check and a new score | your plan's full-scan interval (see Plans and limits) |
| Secrets | re-checks the JavaScript for keys | daily |
| Certificate | certificate expiry | daily |
| Backup health | missing or failed backups | hourly (plans with backups) |
| WordPress heartbeat | the plugin reported in | daily (with the plugin) |
Daily and weekly scans start at night in your account's time zone (between 01:00 and 05:00, at a fixed time per project), so they never load your site during the day. The score and grade change only after a full scan; light scans alert you at once about new problems but leave the score as it is.
Vigavo is gentle with your server: about 3 requests per second (light scans at most 2), it waits when your server asks it to, and it stops a scan early ("Stopped early") when your server answers "too busy" too often, then goes slower next time. You can change the speed on the project's Settings tab.
Scheduled scans run only for sites you have proven are yours. You can make a monitor run less often or turn it off, but not more often than your plan allows.
Plan limits: Plans and limits. Alerts: Alert channels.
Last reviewed Oct 7, 2026, 12:00:00 AM