Evidence Sources
Compare external checks, browser beacon evidence, and WordPress plugin evidence.
Evidence Sources
MetricPoints combines several evidence sources into one site-assurance model. The source affects confidence, privacy handling, and the kinds of issues MetricPoints can detect.
External checks
MetricPoints checks the public website from outside the site. This covers reachability, error documents that still return 200, DNS, TLS, domains, redirects, indexability, security headers, public assets, browser render, journey controls, search, booking embeds, analytics collect requests, important pages, reputation signals, and configured journeys.
Browser beacon
The optional JavaScript beacon reports browser errors, failed network requests, performance sessions, session context, optional replay allowance, and custom client-side events from real visitor sessions.
WordPress plugin
The optional WordPress plugin adds WordPress-side evidence such as application health, search visibility context, form and mail signals, cron health, cache/optimization details, plugin/theme/core versions, safe diagnostics, and change events.
How MetricPoints uses evidence
- Multiple observations can be grouped into one incident when they appear related.
- Technical proof stays available beneath plain-language summaries.
- Signals from the beacon and WordPress plugin should support the same dashboard, All Sites, Site Health, notification, and report workflows as external checks.
- Missing optional evidence is treated as a coverage difference unless it blocks assurance for an area you chose to monitor.
- In Site Health → Settings → Evidence sources, choose whether browser beacon and WordPress plugin signals are expected. External-only sites can leave both optional.
- Missing or stale expected signals are shown as critical monitoring gaps, separately from confirmed website failures. Signals that arrive while optional remain available as evidence and are marked as unexpected; they do not change the expectation automatically.