Website Change Monitor — Page Diff, Content Change Detection & Alerts (No API Key)

Monitor any number of web pages for changes automatically and get detailed line-by-line diff reports showing exactly what was added, removed or modified since your last check. Run it on a daily or weekly schedule and receive actionable change alerts without refreshing pages by hand. It's the text-content counterpart to visual screenshot monitoring — faster, cheaper and easy to parse programmatically. No API key, no login.

🏆 Why this Website Change Monitor?

SHA-256 baseline + line-level diff (added/removed lines + % change) · CSS-selector targeting and ignore-lists to cut noise · stripNumbers to skip counter churn · machine-readable JSON diff (no computer vision needed) · schedule + Slack/email/webhook alerts · export to JSON / CSV / Excel. The lightweight website change-detection API alternative for price, regulation, stock and job-page monitoring.

---

✨ What this Actor does / Key features

• 🔔 Automatic change detection — fetches each URL, extracts the monitored content, hashes it (SHA-256) and compares against the stored baseline.
• 📝 Line-by-line diff — when content differs, reports added/removed lines, an approximate % change and a human-readable diff summary.
• 🎯 CSS-selector targeting — use cssSelectors to monitor only the sections that matter (price, stock status, job listings) and skip nav, ads and footers.
• 🧹 Ignore noisy elements — use ignoreSelectors to strip timestamps, ad containers, session IDs and rotating widgets before comparison.
• 🔢 Strip numbers — enable stripNumbers to ignore changes that only involve numbers (view counts, timers, dates).
• ♻️ Self-updating baselines — after each detected change the baseline is refreshed, so the next run compares against the latest version.
• ⏱️ Schedule-friendly — each run produces a structured dataset you can pipe to email, Slack or any webhook via Apify Integrations.
• ⚡ Lightweight — HTTP fetch only (~1–5 KB per URL), far cheaper than pixel-diff screenshot monitoring.

🚀 Quick start (3 steps)

1. Configure (baseline) — add your target URLs, optionally set cssSelectors / ignoreSelectors, and run once. Every URL returns "baseline saved".
2. Schedule (diff) — set a recurring run (daily, hourly, weekly) in Apify Console. Each subsequent run diffs against the baseline and flags hasChanged: true with the details.
3. Alert & export — connect the dataset to Make/Zapier/n8n to send Slack/email alerts on changes, or export to JSON, CSV or Excel.

📥 Input

Give the Actor a list of URLs to monitor. Selectors and toggles are optional.

Example — competitor pricing pages, price section only

{
  "urls": [
    "https://competitor-a.com/pricing",
    "https://competitor-b.com/pricing"
  ],
  "cssSelectors": ["h1", ".price-value", ".plan-name"],
  "ignoreSelectors": [".timestamp", "#dynamic-ad"]
}

Example — job board, ignoring counters & timestamps

{
  "urls": ["https://company.com/careers"],
  "cssSelectors": ["#job-listings"],
  "stripNumbers": true
}

Example — regulation page, whole-page monitoring

{
  "urls": ["https://regulator.gov/updates"],
  "ignoreSelectors": [".recommendations-carousel", ".live-counter"]
}

Field	Type	Description
urls	array	Web-page URLs to monitor for content changes. Required.
cssSelectors	array	Only monitor content inside these selectors (e.g. .price-value, #job-listings). Empty = whole page.
ignoreSelectors	array	Strip these elements before comparison (e.g. .timestamp, #dynamic-ad).
stripNumbers	boolean	Ignore changes that only involve numbers (counters, dates, view counts).
proxyConfiguration	object	Optional Apify Proxy settings for the HTTP fetch.

Baselines are stored in Apify's key-value store under the Actor's namespace; they persist across runs and refresh automatically after each detected change. Reset them by deleting the KV-store records in the Storage tab.

📤 Output

One row per URL per check — exportable to JSON, CSV, Excel or XML. Here is a trimmed sample record (a diff run):

{
  "url": "https://competitor-a.com/pricing",
  "hasChanged": true,
  "changePercent": 8,
  "addedLines": 3,
  "removedLines": 1,
  "currentContentHash": "9f2b1c4e…",
  "previousContentHash": "3a7d0e51…",
  "diffSummary": "+ Pro plan now $49/mo\n+ New: unlimited seats\n- Team plan $39/mo",
  "checkedAt": "2026-07-06T09:00:00.000Z"
}

🆚 Screenshot monitoring vs. change monitoring

Feature	Screenshot Capture	Change Monitor
Detection method	Visual (pixel comparison)	Text (content diff)
File size	~1–5 MB per URL	~1–5 KB per URL
Cost per check	Higher (rendering overhead)	Lower (HTTP fetch only)
Best for	Visual regression, design QA	Text content, pricing, availability
Machine-readable diff	❌	✅ (added/removed lines, %)
Parse with scripts	Hard (requires CV)	Easy (JSON diff report)

Use both together — screenshots for visual changes, this monitor for content changes.

💡 Use cases

• Competitor price tracking — monitor /pricing pages and get alerted when tiers, features or plan names change.
• Regulation & legal compliance — track government/regulatory pages that publish updates without RSS and get diffs of exactly what changed.
• Job board monitoring — watch company career pages for new postings by targeting the listings selector.
• E-commerce stock & price alerts — detect "Out of Stock" → "In Stock" transitions on product pages.
• News & blog monitoring — see when competitors publish new articles and what their headlines are.
• Content-integrity checks — catch unexpected edits or defacement on pages you own.

👥 Who uses it

Competitive-intelligence & pricing teams · compliance & legal analysts · recruiters tracking career pages · e-commerce & availability watchers · growth & marketing teams · site owners running content-integrity checks.

💰 Pricing

This Actor runs on a pay-per-result model — you pay only for the checks performed during each monitoring run, with no monthly subscription and no minimum usage. Each URL check is lightweight (HTTP fetch only), so large monitoring lists stay cheap and scale linearly. Try it on the free tier first. See the Pricing tab on this page for the current rate.

❓ Frequently Asked Questions

How is "change" detected? The Actor computes a SHA-256 hash of the extracted text content. If the hash differs from the stored baseline, a change is detected; it then does a line-by-line comparison to produce the diff summary.

Where are baselines stored? In Apify's key-value store under the Actor's namespace. They persist across runs and are automatically updated after each detected change.

Can I reset baselines? Yes — delete the key-value store records via Apify Console's Storage tab, or run once with different input fields to create fresh baselines.

Does it handle JavaScript-rendered pages? This Actor uses HTTP fetch (got-scraping), which handles server-rendered content. For JavaScript-heavy SPAs, use a screenshot-capture Actor or a Playwright-based monitor.

How do I get alerted when a competitor changes their pricing page?

Add the pricing-page URLs and target the price section with cssSelectors. On each scheduled run the monitor diffs the text and flags exactly what changed, so you can alert via Slack or email.

How do I monitor a page while ignoring ads and timestamps?

Use ignoreSelectors to strip ad, nav and timestamp elements before comparison, or enable stripNumbers to skip numeric-only changes, so you only get alerts on meaningful content edits.

Is this a website change-detection API alternative?

Yes. It replaces paid change-detection services with a schedulable Actor that returns a machine-readable JSON diff — added/removed lines and % change — that you can wire straight into your own alerts and workflows.

How do I export change reports to CSV or JSON?

Every run writes to an Apify dataset you can export to CSV, JSON, Excel or XML, or pull via the Apify API and webhooks.

🔗 More website & monitoring tools by logiover

Building a full site-monitoring and web-data stack? Pair the Change Monitor with the rest of the suite:

Actor	What it does
Bulk Website Screenshot Capture	Visual snapshots of many URLs
Bulk URL Status Checker	HTTP status & uptime checks in bulk
Broken Link Checker	Find dead links across a site
Website SEO Audit Crawler	On-page SEO issues at scale
Bulk SSL Certificate Checker	SSL expiry & chain validation
Bulk HTTP Security Headers	Audit security headers across URLs
URL to Markdown	Clean Markdown from any page
Website Text & Markdown Crawler	Full-site text extraction
Sitemap to URL Crawler	Expand sitemaps into URL lists
Certificate Transparency Monitor	New-certificate & subdomain alerts
Website Contact Scraper	Emails, phones & socials from any site

👉 Browse all logiover scrapers on Apify Store — 180+ actors across real estate, jobs, crypto, social media & B2B data.

⏰ Scheduling & integration

Run once to establish baselines, then set a recurring schedule (daily at 9 AM, hourly, etc.) in Apify Console. Connect the dataset to Make, Zapier or n8n to send email/Slack alerts whenever hasChanged: true, or pull results via the Apify API and webhooks.

⭐ Support & feedback

Found a bug or need an extra field? Open an issue on the Issues tab — response is usually fast. If this Actor saves you time, a ★★★★★ review on the Store page genuinely helps and is hugely appreciated. 🙏

⚖️ Legal

This Actor fetches only publicly accessible page content and is intended for legitimate monitoring, competitive-intelligence and compliance use. You are responsible for complying with the target sites' terms and any applicable laws.

---

Keywords: website change monitor, page change detection, website diff tool, content change alert, web page monitoring, competitor price tracker, regulation change monitor, automated website monitoring, page diff api, url change detection, website change alert api, recurring website checker.

---

📝 Changelog

2026-07-06

• ✨ README overhaul: shields badge row, green highlight callout, trimmed diff output sample, collapsible full field reference, ready-to-run example scenarios, website/monitoring suite cross-links and clearer quick-start.

2026-07-01

• Maintenance pass: re-verified end-to-end on live data and confirmed successful runs within the 5-minute quality window on the default input.
• Sharpened Store metadata (SEO title & description) and expanded the FAQ with high-intent, long-tail questions for easier discovery in Google and Apify Store search.
• Added ready-to-run example tasks that cover common real-world use cases.