Visual website monitoring tools look alike. They all take a screenshot, diff it, and email you. That is why the choice feels hard: they appear to do the same thing.
They do not do the same thing. The difference is in what they miss.
The seven questions below are designed to show you where a tool falls silent, rather than what it advertises. And because switching is expensive — you lose history, the reports you have sent clients, and everyone's habits — these are the questions to ask before you commit, not after.
1. How far back does the history go?
The most important question on this list, and the one most often skipped.
When a client says "it was like this last month", the answer comes from how much history your tool keeps. Some keep a few days. You can then be right and still lose the conversation, because you cannot show the evidence.
So ask for a number, not an adjective. "How many days?" The answer must be a figure. Most tools keep the free tier deliberately short.
A warning: the difference in history between a free plan and a paid one is usually the largest single difference between the tiers. What you tested on the free tier may not exist on the tier you would actually buy.
2. Can you send reports under your own brand?
For agencies, this is the item that decides the comparison.
A report that says "detected by Visualping" tells the client who to thank. A report with your own logo says the service is yours.
In practice this means: no tool name in the corner of the screenshot, your logo instead. Many tools do not support it at all. Those that do usually put it on a paid plan.
This alone can decide it, because the report is your justification for the invoice.
3. How many sites can you actually monitor?
"Unlimited sites" is the most misleading answer on this page.
The limit is somewhere else. "Unlimited" may mean the number of sites is unbounded while scan frequency, evidence history, or per-site page depth is capped.
If you run forty sites, ask these four separately: scan frequency, total URLs, evidence history, notification limit. If one of them caps you at twenty, the unlimited claim is advertising.
4. Are notifications filtered?
Any tool that emails on every change will be ignored within six weeks. That is not a matter of discipline — it is arithmetic. Once a channel is unread, it is unread.
What to ask for: it should not alert on a hundred-pixel colour shift in one region. Configurable thresholds are not enough; the threshold has to be meaningful.
Practical test: run it on your own site for a week and look at what arrives. What percentage is genuinely interesting? A low rate means the tool is producing noise. Alert fatigue covers why that rate falls and what to do about it.
5. Does it explain the change, or just report one?
Most tools send you two screenshots and the words "something changed".
That is not sendable to a client. "Something changed" is not an answer; the client asks "changed to what?", and you are back where you started.
A good tool separates:
- Visual change — did the page actually render differently?
- Technical change — which element, which text, in the DOM?
- Business context — is this on a conversion path, or somewhere nobody looks?
The third is the one that matters. A small shift in the footer and a one-word change to a price are technically identical "diffs". One needs no action. The other needs an email.
6. Where is the data stored?
Screenshots of client sites are your clients' business data. For an agency, that means it is your responsibility.
Ask: which country is it stored in, how does a deletion request work, and is the data actually removed on cancellation. None of these are standard, so none of them have standard answers.
If you make commitments to clients, this answer is yours to give — not your vendor's. You should be able to say where your clients' data lives.
7. How long does setup actually take?
This is the most written-about and least discussed question.
The shape of it is always the same: add the site (a minute), choose the pages to watch (ten minutes), set the threshold (unknown). The last step has no known duration, because getting the threshold right requires understanding what the tool counts as a change — and that is something you learn by running it for a few days.
Practical advice: trial it on the free plan against your own site for two weeks. Two weeks is the minimum needed to answer "which changes are actually important". Decide sooner and you will set the threshold wrong, then conclude the tool is noisy.
Comparison table
The rows below are what to check, not a filled-in comparison. Fill in each column for the tool you are evaluating, because these values change between versions and between plans.
| Criterion | Why it matters |
|---|---|
| History depth | Lose the conversation without evidence when a client disputes a change |
| White label | The report is your service, or your vendor's |
| Site limits | Whether the portfolio fits, or the advertising says it does |
| Notification thresholds | Weekly noise, or a signal you can read |
| Change classification | Visual, technical and business context, separated |
| Data location | What you will tell your clients |
| Setup duration | Whether you can find the right threshold in week one |
Summary
The differences between visual monitoring tools are not in the feature lists. They are in the defaults: how far back it looks, which changes it ignores silently, whose brand the report carries. Ask all three before you trial anything, and pick a tool you can live with rather than one you have not read.
For the full set of questions, see the seven things to check when choosing a tool — and for the technical side of the comparison, see what visual regression testing is.
Setup steps are in the documentation; plans and pricing are on the pricing page.
Read next
The comparison table
Competitor prices are not a hand-typed table: they carry the date they were verified and the page each figure was read from.
If you want the same comparison on one page with current prices, see the Visualping alternative.