Pro change watching compares text derived from a site’s home page with its previous scan. Use it to investigate unexpected changes while accounting for legitimate publishing.

Enable and establish a baseline

1. Confirm Pro is active.
2. Open PD Modules → Site Sentinel → Settings and review Pro: Tell me when a page changes.
3. In Sites, check that the intended row is not paused and is set to watch for changes.
4. Let that site complete a scan to establish its baseline.
5. Review later The page changed unexpectedly findings against your website publishing activity.

The comparison removes scripts, styles, comments, markup and runs of two or more digits, then normalises the remaining text. It can miss changes limited to those removed elements. Visible rotating text can still produce changes; the module does not know whether someone made an authorised deployment.

Stop only change alerts for a noisy site

Choose Stop change alerts on the site’s row if you intend to exclude it from that comparison. Other enabled checks can continue. To restore it, choose Watch for changes. That control resets the baseline, so the next relevant scan establishes a new comparison point.

Investigate before relying on a cleared warning

The stored baseline advances after a scan. A changed page that stays the same on the following scan can therefore stop producing the change finding without being restored to its earlier content. Preserve evidence and investigate the website itself. This feature is not a malware scan, change-history archive or automatic repair service. Page-change findings are warnings, not serious findings eligible for the module’s critical-only email alerts.

See the PD Site Sentinel Blesta guide for related tasks, or explore PD Site Sentinel.