For teams watching something
Find out that a page changed before your customer tells you
Capture a page on a schedule, compare what it says rather than its markup, and get a signed webhook when it changes.
The problem
Something on the open web matters to your business and nobody owns watching it: a competitor's pricing page, a regulator's guidance note, a partner's API status page, your own checkout after a deploy. The usual answer is a cron job that diffs raw HTML, which means it fires every time a build hash or an ad slot changes, and everyone learns to ignore it.
How domscout handles it
A monitor captures the page on a schedule and keeps the history. It compares what the page says (the extracted text, the title, the links and the status code) rather than the raw markup, so a new build hash in a script or stylesheet URL is not a change and a reworded refund policy is. When it does change, a signed webhook names the run, the two captures and the fields that changed.
Where it shows up
- Competitive pricing alerts that go to a channel people still read.
- Compliance and policy watch on documents you do not control.
- Post-deploy checks on the handful of pages that must never break.
The request
POST /monitors. Monitors start at Pro: 10 monitors, checked as often as every 60 minutes. Business allows 100 every 15 minutes and Enterprise 500 every 5, subject to the service's launch controls.
Go further
More in Monitoring and alerts: A feed for a site without RSS · Competitor price tracking · Minimum advertised price checks · New job posting alerts · Vendor changelog watching · Tender, grant and notice alerts · All use cases
Give your product a browser.
Get clean web content and visual proof into your workflow in minutes.