Catch regressions and fix at scale Pro
Compare scans
See what is new, what was fixed and what is still there between two scans, by check and by site part, with the likely cause marked.
Updated for Lumtera 1.2.2 and Lumtera Pro 1.1.1.
Overview
Compare scans is under Lumtera → Checks → Compare scans. Scans of chooses what to compare: Full scans of your content, Site parts (menus, template parts, patterns, widgets), or Scheduled page checks. Pick an Older scan and a Newer scan, each labelled with its date, how it was started and its number of findings, then press Compare. Since the last scan compares the latest two, and Since a date compares the latest scan with the last one before the day you choose.
The result opens with three numbers: new, with how many of them are errors, fixed, and still there. New since the older scan follows, one line per source, such as "12 new errors, all from template part Header". When that part was edited between the two scans, the line says how long ago and is marked (likely cause), with a link to edit it. A By check table and lists of the pages or parts with the most new and fixed findings follow.
Scans are kept for you: every full content check started with Check all content or WP-CLI, every site parts check and every scheduled page check. When the two scans were made with different versions of Lumtera's checks, a note says that some differences may come from checks that were added or changed.
Why does it matter?
A total that stays the same can hide ten new errors and ten fixes. To know whether the site got better, and what broke it when it did not, you need to compare one scan with another finding by finding.
What do you get?
- New, fixed and still there, with new errors counted separately.
- New findings grouped by where they come from: page content or a shared part such as a template part, synced pattern or menu.
- A shared part edited between the two scans is marked as the likely cause, with a link to edit it; WordPress, theme or plugin updates between the scans are shown as a possible cause.
- A breakdown by check, and the pages or parts with the most new and fixed findings.
- Compare any two scans, the last two, or everything since a date.
How does it work?
-
Scan as usual
Each full content check, site parts check and scheduled page check is kept.
-
Pick two scans
Under Lumtera → Checks → Compare scans, choose an older and a newer scan, or a date.
-
Start with what is new
Regressions come first, grouped by source, so one edited header explains many new errors at once.
Who is it for?
-
After a redesign or an edit to the header
See straight away whether the change added errors, and which shared part they come from.
-
Showing progress to a client
Compare this month with last month and quote how many findings were fixed and how many are new.
-
Checking a remediation sprint
Pick the scan from before the sprint and the one after it, and read the fixed list by check.
Good to know
How it behaves, what it needs, and where its limits are.
- Plans and access
- Included in every Pro plan with an active license. The screen needs an administrator.
- Like with like
- A scan is only compared with scans of the same kind. A finding is the same in both when it is on the same page or part and has the same fingerprint.
- How many scans are kept
- The last 12 scans of each kind, plus the first scan of each month for 24 months.
- Where the numbers also appear
- Client reports say how many findings are new and fixed since the last report, and each full scan adds an entry to the evidence log.
- For AI assistants
- The lumtera/compare-scans ability gives the same comparison to an AI assistant connected to your site, for administrators.
Questions
Something else on your mind? Contact support
What if Lumtera itself was updated between the scans?
A note says the scans were made with different versions of the checks, so some differences may come from new or changed checks rather than from your site.
Why does it say there is nothing to compare?
Comparing needs two scans of the same kind. Run Check all content again, or wait for the next scheduled check.
Does it tell me a theme update caused the problem?
It marks a shared part as the likely cause when that part, such as a customized template part or a synced pattern, was edited between the two scans. It cannot see changes inside theme files that were never edited in WordPress.
More in “Catch regressions and fix at scale”
-
Pro
Email and Slack alerts
Hear about it when a publish adds new errors or feedback goes past its target, never twice for the same one, plus a Monday summary and a score history.
-
Pro
Fixes queue: bulk fixes you review and approve
Propose the same fix on many pages at once — built-in fixes or text you write (and AI drafts, only if you connect an AI provider) — review every change, then apply and undo them in the background.
-
Pro
Fix tracking
Turn issues into tasks, assign them, and let Lumtera close each task when a re-scan confirms the fix.
Compare scans
Get it with Lumtera Pro
In every Pro plan. Personal is $149 a year. Pro installs alongside the free plugin, and your settings and results stay.
14-day refund (opens in a new tab)Keeps working if you don't renew