Health Watch is PageLens AI's recurring monitoring layer for verified sites. It is designed to catch changes over time: score drops, broken links, downtime, security-header regressions, sitemap changes and verified badge drift.
Use it when a site is live, important, or changing often. A Health Watch scan gives you a consistent comparison point so you can see whether the site has improved, drifted, or picked up new issues since the last completed scan.
Plan availability
Health Watch is included on paid account plans for covered verified domains. It is part of the ongoing plan value: instead of remembering to manually rescan every important site, PageLens AI keeps a focused watch on the domains your plan covers.
Free accounts can run manual scans and a limited monthly Deep AI Audit allowance, but Health Watch is designed for Solo, Pro and Agency workflows where sites need recurring coverage.
Page coverage
Health Watch is intentionally focused. It currently checks up to 5 pages per recurring run so the results stay comparable over time.
That page cap is separate from deeper one-off Deep AI Audits. Use a Deep AI Audit when you want broader page coverage, screenshots, narrative review and a full repair plan. Use Health Watch when you want consistent recurring evidence for the most important pages.
Health Watch vs Deep AI Audit
Health Watch is for ongoing regression monitoring. It focuses on repeatable checks that are easy to compare from scan to scan.
Deep AI Audits are for richer review work. They include the broader narrative, persona-style review, screenshots, evidence panels, prioritised fixes and agent-ready exports you use when you want the full report experience.
In practice:
- use Health Watch to keep a verified site watched over time
- use Deep AI Audit when you want a detailed review, handoff, client report or repair plan
- use both when a site matters: Health Watch tracks drift, Deep AI Audit gives the richer investigation
What Health Watch checks
Health Watch looks for meaningful changes such as:
- health score movement
- newly broken or redirected URLs
- homepage downtime or failed responses
- new critical or high-impact findings
- security-header changes
- sitemap and crawl inventory changes
- verified badge drift when the site fingerprint has changed
The aim is not to email you for every tiny difference. Alerts are reserved for changes that deserve attention.
Accepted risks and intentional trade-offs
Health Watch uses the same finding-decision memory as manual reports. If you mark a finding as an accepted risk, intentional trade-off, acknowledged item, or "won't fix now", matching future scans can show that context as Previously acknowledged.
That context keeps the action plan useful for real teams. The technical finding and score remain honest, but the recurring work list no longer treats every known business trade-off as a brand-new task.
Badge freshness and site changes
A PageLens AI verified badge points visitors to public audit evidence for a claimed domain. Badge freshness is about whether that public proof is still anchored to recent, representative evidence.
If the site changes materially after verification, PageLens AI may ask you to re-confirm the badge. Re-scanning updates the audit score and evidence. Re-verifying proves you still control the domain and re-anchors the public badge to the current site.
Recurring scans
Recurring scans are scheduled Health Watch checks for covered domains. They help you catch regressions after launches, CMS edits, dependency updates, design changes, plugin installs or client handoffs.
If you need a deeper one-off review, run an included Deep AI Audit from the report or new scan flow. If you need ongoing confidence, keep Health Watch enabled for the domain.
When to run each scan
Run a free preview when you want to test PageLens AI on one page.
Run a Deep AI Audit before launch, before a client handoff, before paid traffic, or when you want a full repair plan.
Use Health Watch after the site is verified and live, so you can keep an eye on regressions without manually checking the domain every week.