Lookit Page Watch – WordPress Plugin

Download Lookit Page Watch

WordPress plugin that photographs the pages you choose on a schedule, compares each capture against a locked baseline image, and emails the two side by side so a change is spotted by eye

Lookit Page Watch for WordPress Free
Version 0.8.0
Format .zip
Requires WordPress 6.4+
Tested up to the latest WordPress
Requires PHP 8.1+
Capture workflow included

Download Link
How to install
  1. Download the .zip file using the button above
  2. Go to your WordPress admin and navigate to Plugins → Add New
  3. Click Upload Plugin and select the downloaded .zip file
  4. Click Install Now, then Activate
  5. Import n8n/lookit-page-watch-capture-v2.json from the zip into n8n, set a shared token in the Config node, activate the workflow and copy its production webhook URL
  6. In WordPress, go to Page Watch → Schedule and email, paste the webhook URL and the same shared token, then save
  7. Use Test the capture service to confirm the connection
  8. Add pages to the watchlist and run a capture. The first capture of each page becomes its baseline

See How It Works

Try It Yourself

Click on the actual Handicap Icon located in the upper right corner, and the accessibility options menu will appear.

Try It Yourself

Click on the actual Handicap Icon located in the lower right corner, and the accessibility options menu will appear.

Request Website Audit

What You Can Do With It

Use Case User Type Key Benefit
Scheduled page screenshots Site owners Capture any page every 1, 6, 12 or 24 hours, anchored to a time you choose, on this site or anywhere else
Locked baseline images Agencies The first capture of a page becomes its baseline and is never overwritten by a scheduled run or removed by cleanup
Side-by-side comparison Account managers See the baseline and the newest capture together in wp-admin, with the full capture history for each page
Email digest of changes Client teams An HTML digest at a set time, or after every run, so a change is noticed without anyone logging in
No third-party API keys Developers Capture runs through a workflow you host, so no screenshot provider credentials are stored in WordPress

A Baseline That Stays Put

Add the pages you care about to a watchlist and Page Watch photographs them on a schedule you set. The first successful capture of each page becomes its baseline, and from then on nothing changes it automatically. Scheduled runs never overwrite it and the retention cleanup never deletes it. It is replaced only when you choose Set as new baseline.

That is the point of the plugin. You are always comparing today against a version you approved, not against yesterday, so a change that creeps in over a fortnight is still visible rather than absorbed one small step at a time.

Two Ways to Score a Change

Every new capture is scored against the baseline twice: once across the whole page, and once by grid square to find the worst affected area. Each score has its own threshold and either one can flag a page.

The second score is what catches real edits. A rewritten paragraph might move the whole-page figure by one percent and still be sixty percent of its own square. Sliders, ad slots and randomised content will trip a low threshold, so both numbers are adjustable and the worst area percentage is shown in the watchlist, in the capture history and in the digest email.

The Report Arrives by Email

When something looks different you get an email with the baseline and the new capture next to each other, so a person makes the judgement rather than a score deciding for you. Send it at a set time each day, or after every capture run, scheduled or manual.

Delivery is handed to WordPress itself. If the site already runs FluentSMTP the message goes out over whichever connection is configured there, so there is nothing to set up in this plugin. The settings screen records what happened on the most recent attempt, so an email that was never sent can be told apart from one that went missing.

Storage You Control

Captures are saved as real Media Library attachments by default, so WordPress handles thumbnails and file types properly and the images open from the Media screen. On a long watchlist with a frequent schedule that adds up, so storage can be switched to a private, randomly named folder inside uploads instead. A retention window prunes old captures, and baselines are always exempt.

Deleting the plugin no longer wipes the setup. The watchlist, webhook URL, shared token, recipients and baselines are kept by default, so a reinstall picks up where it left off. There is a setting under Storage for when a clean removal is genuinely wanted.

Share This