VizProof Timeline

Yes. The free plan is enough to get started. The easiest path is the "Connecter à VizProof" button on the plugin Configuration page: it signs you in on vizproof.com and configures the token and project automatically. A manual API token (Account → API Tokens) also works; see the Installation section.

Not anymore: one-click connect creates and configures a dedicated, revocable token for the site. Manual tokens remain supported (useful for self-hosted VizProof servers).

If post-update scan is enabled, VizProof Timeline queues a scan after the update completes and exposes status/results in wp-admin.

Yes, in two ways. WP-CLI update commands run through the same updater hooks as an update started from wp-admin. And seven dedicated commands are available: wp vizproof connect links the site to a project without wp-admin. Pass the project with --site-id=<id> and the token with --token-stdin (one line on STDIN), the VIZPROOF_API_TOKEN environment variable, or --code=<code> for a one-time connect code, which also supplies the project when the authorisation designated one. The token is never accepted as an argument, so it stays out of ps and of shell history. --api-base=<url> and --scope=site|selected_pages are optional. wp vizproof disconnect erases the stored token and project. wp vizproof status reports the connection, the selected project, the scan scope, how many pages it covers, and the last scan. wp vizproof pages lists the published pages of the site with the current selection, and wp vizproof pages set --ids=12,34 chooses the pages to watch, with optional --critical=<ids> and --scope=site|selected_pages. --ids= on its own clears the selection, so --ids= --scope=site switches back to a whole-site scan. wp vizproof baseline --wait captures a reference and promotes it, to run before a deployment. wp vizproof scan --wait runs a scan and returns the visual verdict. Exit code 2 means anomalies were found, which lets a pipeline stop on a visual regression. wp vizproof report details a run: FAIL/WARN/OK counts, pages scanned, pages with a diff, most impacted page, then one line per page with its screen, its gap, and, when the line is not clean, its cause (pixel, seo, a11y, or a combination such as pixel+seo) and the SEO fields that moved (seo_changes, each with its before/after value). It reads the last scan by default, or --run=<id>, and takes --limit=<n> (50 by default, 200 at most) and --status=fail|warn|ok. A scan narrowed to selected pages launches one run per page: the report merges them all and lists them in run_ids. Exit code 2 means the run contains failures, like scan. Add --format=json to any of them for a parsable output. status, baseline, scan and report read the token and the project from the site configuration, so connect the site first, either from wp-admin or with wp vizproof connect. pages works before the site is connected, since choosing what to watch does not need the API.

Yes. Per-site: each subsite keeps its own configuration. Network-wide: one shared network-level configuration.