18 / Automate
Put your sites in a text file, pick a daily or weekly time, and SiteAuditLint audits them in the background, saves each audit to History and posts the results to Slack.
Regressions happen between audits. Scheduled audits turn SiteAuditLint into monitoring: every run is saved, compared with the previous audit, and reported to your team without anyone opening the app.
1. Setting up a schedule on Windows
- List your sitesAdd one URL per line to scheduled_sites.txt.
- Open Schedule audits.batDouble-click it in the app folder.
- Create the taskChoose daily or weekly and a time.
- Test it nowOption 2 runs every site immediately, which is a good test.
2. Headless command line
python run_app.py --crawl https://example.com --notify
python run_app.py --sites-file scheduled_sites.txt --notify --export reports| Exit code | Meaning |
|---|---|
| 0 | Finished |
| 1 | An audit failed |
| 2 | No sites or bad arguments |
| 3 | Finished, but Slack or Linear failed |
3. What each scheduled run does
- Audits each site with your saved crawl settings.
- Saves the audit to History, ready for comparison.
- Syncs Linear tickets when switched on.
- Posts to Slack with the change since the last audit.
- Runs an AI visibility check if the last one is older than your chosen number of days.
- Logs to scheduled-audits.log in the app data folder.
Frequently asked questions
Does the computer need to be on?
Yes. Scheduled tasks run while you are logged in, so a computer that is off or signed out at that time skips the run.
Which settings do scheduled audits use?
The crawl settings saved in the app and your edition's page limit.
What happens if an audit fails?
A failure message is posted to Slack, the failure is logged, and the exit code is 1.
Want the background first? Browse the SiteAuditLint Academy, or see all features.