SiteWatch can scan your site every day and email the report, send alerts when something important happens and keep events for the period you choose.
Where to find it: ARN SiteWatch → Settings → General & Report SMTP for the report and its transport, Reports & Events → Notifications for alerts and retention, Reports & Events → Delivery History for sent notifications.
Set up the report transport
Reports use their own mail connection, so they still arrive when the site's normal mail settings fail.
- Open Settings → General & Report SMTP.
- Under Independent report transport, choose the Sending method. Independent SMTP (recommended) uses a separate SMTP account; Existing WordPress mail (depends on customer settings) uses the site's normal mail.
- For independent SMTP, enter the SMTP hostname, Port (587 by default), Encryption (STARTTLS or Implicit TLS), From address, SMTP username and SMTP password. A saved password is kept when you leave the field blank.
- Click Save settings.
The password is stored encrypted with a key based on your WordPress salts; if the salts change, enter it again. Server certificates are always checked. If the independent SMTP connection fails, SiteWatch does not fall back to WordPress mail; the failure is shown on the Dashboard and in the delivery history.
Test the connection with Check report SMTP in Forms & Email → Mail Diagnostics, then send a real report with Email this report on the Dashboard and check the inbox.
Turn on the daily report
In Settings → General & Report SMTP, under Daily report delivery:
| Setting | Default |
|---|---|
| Report recipient | The WordPress administrator email |
| Enable a daily full scan and email its report | Off |
| Daily scan start hour (site timezone) | 09:00 |
| Send a separate alert when a completed scan detects new high priority findings | Off |
- Confirm the Report recipient.
- Tick Enable a daily full scan and email its report and choose the Daily scan start hour (site timezone).
- Optionally tick Send a separate alert when a completed scan detects new high priority findings.
- Click Save settings.
The chosen hour starts the full scan; the email follows when the scan has finished. Check that the site timezone in Settings → General is correct. The daily report has the subject "Security Report for:" followed by your site title; alerts add "[High priority alert]". The same high-priority findings do not trigger a second alert.
The daily full scan is separate from the scheduled file inspection, which runs daily at 01:00 by default and sends no email.
Alerts, maintenance and retention
Open Reports & Events → Notifications. Under Notifications & retention:
| Setting | Default | What it does |
|---|---|---|
| Event and connection retention (days) | 30 | How long events and outgoing connection records are kept, from 7 to 365 days |
| Scheduled file inspection | Daily | A changed-files scan at 01:00 site time without email; can be Off, Hourly or Daily |
| Queue immediate alerts for critical changes and failures | Off | Sends an email soon after a critical change or failure |
| Record newly observed producer/destination pairs | Off | Records each new combination of plugin and outgoing destination as an event |
| Mute immediate alerts for planned maintenance (minutes) | 0 | Pauses immediate alerts for up to 1440 minutes |
Click Save alert policy after a change.
- During maintenance, events are still recorded; only the immediate alerts wait.
- Identical alert messages are grouped into 15-minute windows.
- Shortening the retention also removes older records from later history and reports. Export what you need for an ongoing investigation first.
- On a multisite network, only the main site runs the scheduled file inspection; other sites show that instead of the choice.
Check delivery
Reports & Events → Delivery History lists recent notifications with their kind, status and number of attempts. Failed sends are retried up to five times; you can also click Retry delivery.
Immediate alerts for critical events use the site's standard WordPress mail. Report emails use the report transport.
"Accepted by service" means the mail server accepted the message. It does not prove that the message reached the inbox. Check the recipient's inbox and spam folder.
All schedules depend on WordPress scheduled tasks. If the site is down, SiteWatch cannot send a missing-report alert; see SiteWatch requirements for a reliable hosting scheduler.