Website Change Monitor

Website Change Monitor creates stable text snapshots and SHA-256 fingerprints from public web pages for recurring change detection. It is useful when a page has no RSS feed or changelog and you want a simple structured way to see whether its text has changed over time.

What it does

The Actor fetches configured public URLs, normalizes relevant page text, creates deterministic fingerprints, and writes structured snapshot records to the default Apify dataset. Repeated runs can then be compared by fingerprint or consumed by downstream automations that react when content changes.

Typical use cases include:

• monitoring public policy, pricing, documentation, or product pages;
• detecting changes on competitor or vendor websites;
• tracking pages that do not provide their own update feed;
• feeding detected changes into review or alert workflows;
• scheduling recurring checks through Apify.

Quick start

1. Add one or more public URLs to the Actor input.
2. Start with conservative request and result limits.
3. Run the Actor and inspect the default dataset.
4. Confirm that the extracted text represents the page content you want to monitor.
5. Run the same input again later and compare the fingerprint and normalized text.
6. Once the source behaves as expected, schedule recurring runs or trigger the Actor through the Apify API.

The Input tab also includes shared crawler controls for retries, concurrency, request limits, timeouts, and networking configuration, together with any Actor-specific snapshot options.

Output

Each dataset item represents a normalized page snapshot with source metadata, scrape time, and a SHA-256 fingerprint derived from the monitored text. The Actor dataset schema defines the exact field contract. Results can be exported as JSON, CSV, or Excel or consumed through the Apify dataset API.

Scheduling and integrations

For continuous monitoring, create an Apify schedule and compare new snapshots with previous results in your workflow. Results can feed webhooks, automation platforms, databases, notification services, or other Actors.

Limitations

Pages can change for harmless reasons such as timestamps, rotating content, localization, or layout updates. Some highly dynamic pages may also produce noisy snapshots. A changed fingerprint means the monitored text changed; it does not by itself determine whether the change is important.

Pricing

See the Actor's Apify Store Pricing tab for the currently configured pricing model and rates. Platform usage depends on page count, page size, retries, and monitoring frequency. Test a representative set of URLs before configuring frequent recurring runs.