🔍 Landing Page Change Monitor

Watch any list of public pages — competitor landing pages, pricing pages, product pages — and get told what changed between runs. Pure scheduled monitoring; pairs perfectly with n8n/Slack alerts.

⚡ What you get

Field	Description
url	Page checked
changed	Did visible content change since last run
firstSeen	First time this page was seen
previousHash / currentHash	Content fingerprints
diff	Added/removed lines (when changed)
checkedAt / textLength	Run metadata

🎯 Use cases

1. Competitive intel — track rival pricing & messaging changes
2. Sales/GTM — get alerted when a target changes positioning
3. Brand/compliance — monitor your own pages for unexpected edits
4. Product — watch partner/integration docs for changes

🚀 Sample inputs

{ "urls": ["https://competitor.com/pricing","https://rival.io/features"] }

{ "urls": ["https://example.com/"], "selector": "main" }

📦 Sample output

{ "url": "https://competitor.com/pricing", "changed": true, "firstSeen": false,
   "diff": { "added": ["New: Team plan $99/mo"], "removed": ["Team plan $79/mo"] }, "checkedAt": "2026-06-04T..." }

📊 Sample Output

🛠 How it works

1. Fetch — pulls each page with an identified User-Agent.
2. Extract — strips scripts/styles; optional CSS selector to focus a section.
3. Compare — hashes visible text and diffs against the previous run (snapshots persist in a named key-value store).
4. Report — one row per page with changed + added/removed lines.
5. Schedule — run hourly/daily; wire changed==true to Slack/email via n8n.

🔗 Related Actors

• Tech Stack Detector
• Page Speed Analyzer
• Google Search Scraper
• Website Content Crawler

💰 Pricing Example

Pay-per-event: $0.005 per run + $0.06 per page checked (page-check).

Pages	Cost
10	~$0.60
50	~$3.00
200	~$12.01
Apify's $5 free credit covers ~83 pages. Start free →

⚖️ Legal & data sources

Fetches publicly-accessible pages with an identified User-Agent, one request per URL. Respect each site's terms and robots posture for your use case.

❓ FAQ

How does it know what changed? It stores a snapshot per URL and diffs visible text on the next run. JS-heavy pages? Static fetch today; focus with a selector for reliability. Can I watch one section? Yes — pass a CSS selector. Does the first run show changes? No — it records a baseline (firstSeen: true). Alerting? Filter changed==true in n8n/Make and route to Slack/email. State retention? Snapshots persist in a named key-value store across runs.

🆘 Troubleshooting

• Always "changed" — the page has dynamic/randomized content; narrow with a selector.
• Never "changed" — content is JS-rendered and not in the static HTML.
• Blocked/empty — some sites block bots; use sparingly and respect terms.
• Too much diff noise — target a stable section via selector.

🏷️ About NexGenData

Structured public-data tools for analysts, developers, and operators. thenextgennexus.com.