VizProof Timeline connects WordPress to VizProof, a visual regression testing service, so every WordPress update can be followed by an automated visual check of your key pages.

Why

Plugin, theme, and core updates rarely throw PHP errors when they break something visual: a shifted button, a collapsed layout, a missing hero image. Your monitoring stays green while your pages degrade. VizProof Timeline catches those regressions right from wp-admin, before your visitors do.

How it works

Connect the plugin to your VizProof account (free plan available) with an API token.
Link a VizProof project and select the pages to monitor.
Run updates as usual: the plugin queues a visual scan right after each plugin, theme, or core update and shows live progress on the Updates screen.
Review the verdict (OK, changes to review, or regressions) and pixel-level diffs without leaving WordPress.

Key features

Post-update scans after plugin, theme, or core updates, with live step-by-step progress and elapsed time
Optional baseline scan before running updates
Scan status directly on the WordPress Updates screen
Run history and visual diff summaries in wp-admin
Scheduled checks with WP-Cron (Action Scheduler fallback)
Plugin rollback with local backups when an update causes regressions
Multisite support in per-site and network-wide modes
WP-CLI compatible: scans also hook into CLI-triggered updates

Requirements

A VizProof account and API token are required. The free plan is enough to get started: sign up at vizproof.com/register. See the Installation section for the step-by-step setup.

External services

This plugin connects to VizProof APIs hosted at https://vizproof.com (or a custom VizProof API URL configured by the site administrator).

It sends requests only when plugin features are used (project/page loading, scan launches, run history refresh, post-update workflows, scheduled scans).

Data that may be sent includes:

API token entered by an administrator
Linked VizProof site/project ID
Page IDs or URLs used for scans
Run trigger metadata required by update workflows

Service documentation and policies: