Page Change Monitor avatar

Page Change Monitor

Pricing

from $1.50 / 1,000 results

Go to Apify Store
Page Change Monitor

Page Change Monitor

Monitor web pages for content changes. Diffs each run against the previous snapshot and emits structured change records with added/removed lines — ideal for price, job, docs, and competitor monitoring.

Pricing

from $1.50 / 1,000 results

Rating

0.0

(0)

Developer

Cynix Dev

Cynix Dev

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

a day ago

Last modified

Categories

Share

Watch any set of public web pages for content changes. Every run compares each page against its previous snapshot and emits a structured change record — including added/removed lines — so you know exactly what changed, not just that something changed.

Schedule it hourly or daily on Apify, wire the dataset into a webhook, Slack, or your own pipeline, and you have a monitoring SaaS in one Actor.

Use cases

  • Price monitoring — watch competitor pricing pages (use cssSelector: ".price").
  • Job monitoring — get diffs when a careers page changes.
  • Competitor intel — track feature pages, changelogs, terms of service.
  • Docs/compliance — know when a policy or API doc is edited.
  • Content QA — detect unexpected changes on your own pages.

How it works

  1. Fetches each URL and extracts content (readability main-content by default, or a specific CSS selector).
  2. Normalizes to Markdown and hashes it.
  3. Compares against the snapshot stored in a named key-value store.
  4. Emits one record per URL: first_snapshot, unchanged, or changed (with +/- line counts and the actual diff text).
  5. Stores the new snapshot for the next run.

Output record

FieldDescription
url, titleMonitored page
statusfirst_snapshot / unchanged / changed / error
diffSummaryHuman-readable summary, e.g. +12 / -3 lines vs 2026-07-26T…
addedLines / removedLinesChange magnitude
diffAdded / diffRemovedThe actual changed lines (capped by maxDiffLines)
contentHash, previousHashFor your own dedup logic
checkedAt, previousCheckedAtTimestamps

Tips

  • Keep mainContentOnly: true to avoid false positives from rotating ads/nav.
  • Use separate snapshotStoreName values for independent monitors.
  • Chain with Apify Schedules + webhooks for real-time alerting.

Compliance

Public pages only. No logins, no paywall bypass, no personal-data collection.