A check found something. Now you want to know within a minute whether it is a real problem or just a banner that rotates. It does not matter where the check came from: an On-Demand Check, Monitoring and an Auto Update Check all end up in the same place, the Checks tab of the Web App. This guide shows how to read the list, the comparison and the verdict of our AI, and how to set a status so nobody looks at the same check twice.
The Checks Tab
Everything you review lives on the Checks tab. Each entry is one check: one page on one device, compared with its earlier screenshot.
Two Views: Batch and Flat
Batch View groups the checks by run. Each run shows when it ran, what started it (Monitoring, an On-Demand Check or an Auto Update Check) and how many pages were checked. Expand a run to see its checks. This is the better view when you want to review one update session as a whole.
Flat view lists all checks in order of time, no matter which run they belong to. This is the better view when you look for one page or want to go through everything in a period.
Filter the List
The filters at the top narrow the list down, so you only see what needs you:
- Period: the last day for changes from overnight, or a longer range for a full review.
- Status: New, OK, To Fix or False positive. Filter for New to see what nobody has looked at yet.
- Type: only the checks of Monitoring, of On-Demand Checks or of Auto Update Checks.
- Website: only the checks of one website.
- Visual: choose With changes only to hide every page where nothing changed. On large sites this is the fastest way to the pages that matter.
What Each Row Shows
- Status: New until you set another one.
- Page and device: the title and address of the page, with a desktop or mobile icon.
- Difference: how much of the page changed, in percent.
- Browser console: how many console entries were added or removed, on plans with console tracking.
- AI verdict and summary: Alert, Unsure or OK, with one short sentence about what changed.
The Comparison Popup
Click a row to open the check. This is where the actual review happens: you see the page before and after, and what our AI makes of the difference.
Before and After Slider
The left side shows both screenshots in one slider. Drag the handle to compare them. Two buttons above the slider decide what you compare:
- Before ↔ Change: the earlier screenshot against the new one with every changed area highlighted. You see at a glance where on the page something moved.
- Before ↔ After: the earlier screenshot against the clean new one, without highlights.
The Panel on the Right
- AI change analysis: one card per changed area with a verdict and a description (more on that below).
- Visual changes: how much of the page changed overall.
- Browser console: console entries that were added or removed, on plans with console tracking.
The status and the Public link of the check sit at the top of the popup.
AI Change Analysis
Every check with a difference is looked at by our AI. It goes through the changed areas, works out what actually changed and gives a verdict, so you do not have to squint at highlighted pixels yourself.
The Three Verdicts
- OK (green): content that changes by itself or as expected, such as a rotating banner, an ad slot or a live widget. No alert is sent for it.
- Alert (red): a real change in text, layout, navigation or images. You get an alert.
- Unsure (yellow): the AI cannot tell. It is shown to you like an alert, so you decide.
A check with several changed areas gets one overall verdict. Alert wins over Unsure, and Unsure wins over OK, so one glance tells you whether the check needs you.
One Card per Changed Area
Each changed area has a numbered card with its verdict and a plain description of what changed. Hover over a card to see the area on the screenshot, or click it to jump there. That helps when a page changed in several places and you want to go through them one by one.
The AI Summary of a Run
When a run is finished, our AI also sums up all its changes in two or three sentences. You find this summary in the alert email and next to the run in the Checks tab, so you know what happened before you open a single check.
How the AI decides, and what it never waves through, is explained in Teach the AI What to Ignore.
Browser Console Changes
Some updates break a page without moving a single pixel: a form that no longer sends, a checkout script that throws an error. On plans with console tracking, the Browser console section of a check lists the console entries that were added or removed between the two screenshots, so you catch these too.
What is recorded, how our AI judges it and what to do with a new error: Catch Broken JavaScript, Not Only Broken Layouts.
Setting a Status
A status records your decision, so you and your team know which checks are dealt with. Every check starts as New. After looking at it, set one of these:
- OK: the change is expected or fine. Nothing to do.
- To Fix: something broke and needs work. Filter for this status later to get your to-do list.
- False positive: not a real change, for example a date or a counter. If the same one keeps coming back, create a feedback rule (next section).
On a large run, filter by status to find what is still New or what still waits for a fix.
The Same Harmless Change Again? Create a Feedback Rule
A rotating hero banner, a live price widget, a “last updated” date: some things change on every run and you already know they are fine. Click Ignore in future on the card of that change, choose whether the rule applies to this page only or to all pages of the website, and our AI marks that change as OK from then on.
The full walkthrough, with the clip, the scope options and how to manage your rules: Create a rule from a check.
Sharing a Check
When a client asks “what changed?”, show them. Every check has a Public link at the top that opens the before and after view without a login. How to copy it and what your client sees: Share a check with your client.
Review Checks in the plugin for WordPress
Looking after one site from wp-admin? You can review right there, without logging in to the dashboard. The plugin shows the same checks, the same AI analysis and the same statuses.
- In WordPress, open WebChange Detector → Checks. Batch View groups the checks by run, List View shows one flat list of pages.
- Set the Status filter to New to see what nobody has looked at yet.
- Open a run and click a check. It opens on its own page.
- Drag the slider to compare the before and after screenshots, then read AI Change Analysis: every changed area has a verdict and a short reason.
- Decide and set the status with Change Status to: to OK, To Fix or False positive. The check then drops out of the New filter.
- Use Previous and Next to go through the remaining checks without going back to the list.
In the screenshot: the status 1, the Public link 2 you can send to a client, and AI Change Analysis 3.
The same harmless change keeps coming back? Create a rule from the check: Create a Rule in wp-admin. Every control of this page is explained in the plugin reference.
Review Best Practices
- Start with the AI verdict. OK means you can most likely move on. Alert or Unsure means look closer.
- Filter for “With changes only”. On large sites this hides everything where nothing happened.
- Create feedback rules as you go. After each review, create a rule for the false positives that keep coming back. After a few runs your alerts are mostly real ones.
- Look at the Browser console section even when the page looks fine. A JavaScript error can break a function without any visible change.
- Set a status on every check. It keeps the list clean and makes unreviewed checks easy to find.
What’s Next
Checks come from three places. Each one has its own guide:
- On-Demand Checks: before and after comparisons for updates you run yourself
- Monitoring: scheduled screenshots that catch changes nobody planned
- Auto Update Checks: comparisons around the automatic updates of WordPress
- Manage multiple client sites: review the checks of all your client sites from one dashboard