Website change detection
Website change detection that tracks real content
Website change detection for docs, policies, landing pages, and competitor copy. Get webpage change alerts with text diffs, AI filtering, snapshots, and a website change detection API — powered by the same AnyCrawl scrape engines.
Opens the monitor wizard with your URL and frequency prefilled.
Track website changes without screenshot theatre
When you need to know what changed in the copy — not whether two pixels shifted.
Website change detection scrapes a URL on your schedule, normalizes the page content, and compares it to the last snapshot. If the text changed, you get a webpage change alert with a line-level unified diff you can read in the dashboard or push over webhook.
This is the right tool for API documentation, compliance pages, competitor messaging, and landing-page regressions. It is not uptime monitoring, and it does not ship visual screenshot diffs. For numeric pricing tables, use price monitoring instead — or run both.
How website change detection works
Paste a URL, choose a check frequency, and get notified when content meaningfully changes.
1. Choose a target
Paste a URL and pick webpage or price monitoring.
2. Set a frequency
From every 15 minutes to weekly — fixed presets, no cron editing.
3. Get notified
Email recipients and/or webhooks when a meaningful change is detected.
Built for content change workflows
Noise control and durable history so alerts stay actionable.
Text diffs that matter
Normalized page content with line-level unified diffs — ideal when you care about words, not pixels.
Noise control
Text-line exclusions, main-content mode, and AI goals cut false positives from banners and timestamps.
Snapshot history
Every check keeps a snapshot you can review later for compliance or regression audits.
JS-rendered pages
Use Playwright when the page needs a real browser; Cheerio for lighter static HTML.
AI meaningful alerts
Describe what matters in plain language so cosmetic edits do not page your team.
Email + webhooks
Per-monitor email chips and monitor.changed events into Slack, Discord, or your app.
Setup that cuts false positives
Most abandoned monitors die from alert fatigue — tune these before raising frequency.
- Step 1
Prefer main content
Enable only-main-content so nav, footer, and promo chrome do not dominate the diff.
- Step 2
Ignore noisy lines
Drop timers, live counters, and relative “posted 3 hours ago” labels by excluding the lines that contain them.
- Step 3
Write a goal
Example: “Alert when plan limits, pricing copy, or security advisories change.”
- Step 4
Right-size frequency
Start at 6 hours or daily; tighten only for high-stakes URLs.
Website change detection scope
Clear boundaries so you pick the right tool.
| Capability | AnyCrawl Monitors | Notes |
|---|---|---|
| Track website / webpage text changes | Yes | Primary job |
| Webpage change alerts (email / webhook) | Yes | Per-monitor notify options |
| Website change detection API | Yes | monitor_type: webpage |
| Structured price field extraction | No | Use price monitoring |
| Screenshot / visual diffs | No | Out of scope |
| Uptime / HTTP availability | No | Use an uptime product |
Website change detection API
Create a webpage monitor, then list changes and snapshots with the same API key.
curl -X POST https://api.anycrawl.dev/v1/monitors \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"name": "Docs homepage",
"monitor_type": "webpage",
"cron_expression": "0 */6 * * *",
"targets": [{ "url": "https://docs.example.com" }],
"goal": "Alert when documented API surface or limits change",
"notify_options": { "channels": ["email", "webhook"], "only_meaningful": true }
}'Common website change use cases
All of these use the webpage monitor type — configure goal and text exclusions per URL.
API documentation updates
Know when endpoints, limits, or auth docs change before customers file tickets.
Compliance and policy pages
Keep audit-friendly snapshots when terms, privacy, or regulatory text updates.
Competitor homepage messaging
Track positioning and feature claims without screenshot galleries.
Product changelog pages
Surface new release notes automatically into Slack via webhooks.
Landing page regressions
Catch accidental H1, CTA, or hero copy edits after CMS publishes.
Terms of service changes
Get a diff trail when legal pages ship updates overnight.
Part of the website monitoring tool
Webpage monitors sit next to price monitors in one dashboard.
Browse the website monitoring tool hub for the full picture, or jump straight to price monitoring when the signal you need is a number on a pricing page.
FAQ
What is website change detection?
Website change detection periodically scrapes a URL, normalizes the main content, and compares it to the previous snapshot. When text changes, you get a webpage change alert with a unified diff plus optional email or webhook delivery.
How do I track website changes without screenshot tools?
AnyCrawl tracks website changes with text normalization and line-level diffs — ideal when you care about copy, docs, and policies, not pixels. Pair it with an AI goal to filter cosmetic noise.
How do you reduce false positives in webpage change alerts?
Exclude text lines containing timer or banner phrases, only-main-content extraction, and an AI goal that describes what matters — for example “alert when plan limits or pricing copy change.”
Can I monitor JavaScript-heavy pages?
Yes. Webpage monitors use AnyCrawl scrape engines including Playwright when needed, so SPAs and dynamic pages are supported alongside lighter Cheerio scrapes.
Is there a website change detection API?
Yes. Call POST /v1/monitors with monitor_type set to webpage. Browse changes and snapshots via the REST API, or force a check from the dashboard or API.
What kinds of pages should I watch?
API docs and changelogs, terms and privacy policies, competitor messaging pages, marketing landings you own, and any HTML page where content drift creates risk or opportunity.
How often can checks run?
From every 15 minutes up to weekly using fixed presets. Higher frequency uses more scrape credits — start at 6 hours or daily unless the page changes often.
Does website change detection include price extraction?
Webpage monitors focus on text diffs. For structured price, currency, and stock fields, create a separate price monitor — or run both on the same URL if you need content and pricing signals.
Further reading
Start website change detection
Create a webpage monitor in the dashboard and get your first baseline snapshot.
Create webpage monitor