Your client's site changed. You already know.
Crawlens scans the sites you manage on a schedule and records what changed, when, and by how much — the last good state, the new scan, and the difference between them, documented so you can show your client.
- Review: 09:42:11 hero heading shifted +18px right
- Critical: 09:42:12 CTA color #111 → #FF5A1F
- No change: 09:42:12 checkout form no change
- Critical: 09:42:14 console 1 new error
Not just a change — enough evidence to decide.
The last good state, the new scan and the meaningful difference meet in one event record. See what changed without losing context.
Rather than describe it: open a real sample change report
Have the incident explained before the client writes in.
Scanning, visual regression detection, parsing, evidence and notification move along one operational line. The 24 seconds below show a sample event record.
Silence the noise. Make the decision visible.
Every difference is scored by visual impact, technical signal and business context. Pick an event to see why it is critical or silent.
Critical change
The main CTA is not visible in the current scan and could not be found in the DOM. The user's primary conversion path is affected.
It reads the evidence. It cannot invent it.
Every statement the interpretation layer makes has to point at a piece of your evidence, and anything it cannot match is dropped before you see it. When the evidence is thin, it stays silent instead of guessing.
Real text, not a hash
Added and removed words are extracted from the stored page and pinned to their place on it, so a claim about a price or a headline can be checked by reading.
Claims that must cite evidence
Every fact it reports carries the identifier of the region or text block it came from. A claim that matches nothing is removed, not softened.
It is allowed to say nothing
A page whose change is too small or too ambiguous produces no interpretation at all. Silence is a valid answer, and it is counted.
Your importance policy
Write what matters to you in your own words, per organization or per project. Each edit is versioned, so a past decision stays readable.
Silence a real alarm
A wrong interpretation costs you a sentence you can correct, and your correction is recorded. A missed alarm would cost you a customer, so the layer is not allowed to make that trade — and the counters above are shown to you rather than kept in a log.
- 0Critical or high-severity events withheld
- 0Structural signals withheld
- 0Withheld without verified grounding
After a change, everyone looks at the same record.
From notification to decision, “who saw what, and when?” never stays open.
Open the evidence
Review before, after and the difference on one screen.
Read the context
See the visual difference together with technical signals.
Record the decision
Approve, mute or hand it to the team.
Keep the history
Every decision and piece of evidence stays in one archive.
Running an agency? work out what Crawlens earns you, with your own numbers
Start monitoring your sites.
Add your first site. When something changes, have the evidence ready before your client asks.
Start free ↗