Why your website monitor stayed silent
By Peekivo
Last reviewed
Silence from a change monitor has two very different meanings: it checked the page and nothing you care about changed, or it could not check the page properly at all. Many tools show both the same way. The causes below are the usual reasons a real change produced no alert, with how to tell and what to do.
Eight common causes
1. The site blocked the check
- What happened: the site answered with a bot wall, a CAPTCHA or an access-denied page instead of the content.
- How to tell: open the monitor's latest saved copy or screenshot. If it shows a challenge or an error page, the monitor never saw the real page.
- What to do: lower the check frequency, use the site's official feed or email list if it has one, or accept that this page cannot be watched automatically. Getting around a block is not a fix.
2. The content needs JavaScript
- What happened: the page loads its prices, lists or stock status with JavaScript after the first response, and the monitor read the page without running it.
- How to tell: the saved copy has the page frame but the part you watch is empty or shows a loading message.
- What to do: switch the watch to a mode that renders the page in a browser, if your tool has one.
3. The page changed shape
- What happened: the site redesigned the page or renamed an element, so the selector or region you picked no longer matches anything.
- How to tell: the monitor reports an empty value, a missing element or a sudden drop in the amount of text it reads.
- What to do: pick the region again on the current page, and prefer tools that tell you when a watched element disappears.
4. The change happened outside the watched part
- What happened: you watch one region, and the news appeared somewhere else on the page or on another page.
- How to tell: compare the whole page by hand with the monitor's saved copy.
- What to do: widen the region, watch the list page where new items appear, or add a second watch for the other page.
5. The rule did not match
- What happened: the page changed, but not in the way your rule asks for. A threshold was not crossed, an exact word was spelled differently, or a minimum-change setting ignored a small edit.
- How to tell: the monitor's history shows the change, but no alert was sent for it.
- What to do: test the rule against the current page and against an earlier version, and loosen exact-match wording where the site varies it.
6. The change came and went between checks
- What happened: something appeared and disappeared again between two checks, such as a short restock or a flash price.
- How to tell: other people saw it, but none of the monitor's saved copies contains it.
- What to do: check more often if your plan allows it, and use the seller's own alerts for very short-lived events. No interval catches everything.
7. The monitor saw a different version
- What happened: the site serves different content by country, currency, language or experiment, and the monitor's version did not change while yours did.
- How to tell: the saved copy shows a different currency, language or layout from the one you see.
- What to do: watch the page version for your region where the site offers a fixed address for it, and check which region your monitor reads from.
8. The alert was sent but did not reach you
- What happened: the monitor detected the change, but the email landed in spam, the chat integration was disconnected or the webhook failed.
- How to tell: the monitor's history shows the change, and its delivery log, if it has one, shows a failure or nothing at all.
- What to do: add the sender to your contacts, reconnect the integration, and send a test alert after any change to your setup.
The opposite problem: alerts for nothing
A monitor that compares the whole page alerts on every date, ad, rotating offer, cookie banner and A/B test. After enough of those, people stop reading alerts and miss the real one. Watch the one region or value you care about, and ignore parts that change on every visit.
A checklist for any monitor
- Can you see when the page was last read successfully, not only when it was last checked?
- Can you open what the monitor actually saw on its latest check?
- Does a failed or blocked read show up as a problem rather than as no change?
- Are you told when the watched part of the page disappears?
- Have you sent a test alert to every destination since you set it up?
How Peekivo is built to show it
- Each watch keeps its last attempt and its last successful read apart, so a page that could not be read never looks like a page that did not change.
- A bot wall, CAPTCHA or block page is reported as its own health state. Peekivo does not get around it.
- Peekivo is built to record whether each notification reached each destination, and says so when delivery is uncertain.
Questions
Why didn't my website monitor detect the change?
Usually because it could not read the page properly, it watched a different part of the page, its rule did not match the change, or the change came and went between checks. The causes above show how to tell which.
Why do I get false change alerts?
Because the monitor compares parts of the page that change on every visit, such as dates, ads and rotating offers. Watching one region or one value removes most of them.
How do I know my monitor is still working?
Look for the time of the last successful read, not the last check, and open the copy the monitor saved. If your tool shows neither, send yourself a test alert and compare its saved copy with the live page.
Can a website block change monitoring?
Yes. Sites can refuse automated visits with bot walls, CAPTCHAs or access rules. A careful monitor reports the block instead of treating it as no change.
Related
Want to be told when a page changes?
Join the waitlist