Monitor Company Contact Page Changes at Scale

A company contact page changes for ordinary reasons: a new office opens, the press alias changes, or a social account moves. Scheduled snapshots can catch those changes, but only if the comparison ignores formatting noise.

Run the Website Contact Scraper from a saved Apify Task:

{
  "domains": ["basecamp.com", "zapier.com", "stripe.com"],
  "maxPagesPerDomain": 10,
  "useBrowser": false
}

Build a canonical snapshot

Lowercase emails, normalize telephone spacing when country context is known, remove social-link tracking parameters, and sort each list. Keep raw values separately for display.

snapshot = {
    "domain": row["domain"].lower(),
    "emails": sorted({x.lower() for x in row.get("emails", [])}),
    "phones": sorted(set(row.get("phones", []))),
    "socials": row.get("socials", {}),
    "address": " ".join(row.get("address", "").split()),
}

Compare the canonical snapshot with the last successful one. Do not replace a good prior snapshot after a failed crawl.

Alert on semantic changes

Useful events include a new email, removed phone number, changed registered address, or a new official social profile. A reordered array is not a change. Neither is a utm_source parameter appearing on the same LinkedIn URL.

Send a compact diff with the old value, new value, source page, and observation time. This gives sales operations or vendor management enough context to decide whether the change matters.

Set a sensible schedule

Weekly checks are enough for most company lists. Run high-value counterparties more often only if someone owns the review queue. A monitor that produces more alerts than the team can inspect is just an expensive archive.

The Website Contact Scraper page provides the current-state collection layer. Apify schedules and your snapshot store provide the history.