Website change monitoring: tools, free options and catching defacement
How website change monitoring works, the free and paid tools for tracking page changes, and how to get alerted when your own site is defaced or injected with code.
· 4 min read · By the Spot Downtime team
Website change monitoring alerts you when a page is different from last time. People use it for two quite different jobs: watching other sites (a competitor's prices, a government notice, a product coming back in stock) and watching their own, to catch SEO regressions or someone tampering with the page. The tools overlap, but the setup differs.
How change monitoring works
The tool loads the page on a schedule, keeps a copy, and compares each new load with the last. The comparison is where tools differ:
| Comparison | Good at | Watch out for |
|---|---|---|
| Text | Wording, prices, new list items | Dates, counters and rotating content trigger it constantly |
| Visual (screenshots) | Layout and image changes | Ads, carousels and cookie banners shift the picture |
| A selected element | One price or one paragraph | Breaks when the page's structure changes |
| Source or files | Injected scripts, changed code | Noisy on pages built fresh for each visit |
In every case, the trick is to watch the smallest part of the page that matters. Watching a whole news home page means an alert every check.
Website change monitoring tools
- Visualping and Distill.io: hosted, with visual and text comparison and a point-and-click way to pick the part of the page to watch. Both have free tiers with limited checks.
- changedetection.io: open source and self-hosted, so free if you run it yourself, with text, element and JSON filters.
- Conductor Website Monitoring (formerly ContentKing): change monitoring for SEO, tracking titles, meta descriptions, robots directives and redirects across your own site.
For free website change monitoring of a handful of pages, a free tier or self-hosted changedetection.io is enough. For a whole site's SEO, a dedicated SEO tool is worth it.
Website defacement monitoring
Defacement is the change you most need to hear about fast: a page replaced with an attacker's message, spam links added to the footer, or a script injected to skim card details. Visitors and search engines see it before you do. Several checks catch it, each at a different layer.
1. A keyword that must be there
A website monitor with Page must contain set to text from your page, such as your company name in the footer, fails as soon as the page is replaced. It runs every few minutes on every Spot Downtime plan. It won't notice content added to an otherwise intact page, which is what the next check is for.
2. A script that checks for what shouldn't be there
Card skimmers and spam injections usually add a script or link from a domain you don't use. A short scheduled script can look for those and ping a heartbeat only while the page is clean. If the page changes, the pings stop and you get an alert:
#!/bin/sh
# Pings the heartbeat only while every <script src> comes from a domain we use.
page=$(curl -fsS -m 20 https://example.com/checkout) || exit 1
if echo "$page" | grep -Eo '<script[^>]+src="https?://[^/"]+' \
| grep -Ev 'src="https?://(example\.com|js\.stripe\.com)' | grep -q .; then
exit 1 # an unknown script host: don't ping
fi
curl -fsS -m 10 --retry 3 https://YOUR-HEARTBEAT-URL > /dev/nullNo heartbeat ping: alert when the deadline passes
Run it from cron every few minutes, and list every host your pages legitimately load scripts from. For static sites you can go further and compare a sha256sum of the files with a known-good copy.
3. DNS and certificates
Some attacks never touch your server: they change your DNS so visitors reach someone else's. A DNS monitor with your expected A, CNAME and NS values alerts the moment they change, and SSL monitoring shows when the certificate is no longer yours.
4. Security headers
A Content-Security-Policy that only allows your own script hosts stops many injected scripts from running even if they get onto the page. The security headers checker grades what your site sends now.
Uptime and change monitoring are different tools
Get new guides by email
Practical posts on monitoring, outages, error fixes and on-call, when they're published. No spam.
Keep reading
- Monitoring · How-toHow to verify your site after every deploy (before customers tell you)A deploy can succeed and still break the site. A short post-deploy checklist, a smoke-test script and the monitor settings that catch what a green pipeline misses.November 4, 2026 · 7 min read
- Monitoring · How-toFree website monitoring: a complete setup that costs $0Uptime, SSL, DNS, speed, broken links, changes and a status page: how to monitor a website properly for free, which free tools to use for each, and what you give up.November 3, 2026 · 3 min read