Home › Guides › Wayback Change Monitor

Website history diff: when and what changed on any URL, from the Wayback Machine

The Wayback Change Monitor shows when any URL changed on the Internet Archive's Wayback Machine — and what changed. Not a raw snapshot dump: a dated change timeline per URL with classified change types, byte deltas, title and status transitions, meaningful text diffs (noise filtered), and an archived proof link for every change. No API key, no login.

Who it's for

• Competitive and sales intelligence — know the day a competitor changed pricing, product or positioning.
• SEO and content teams tracking the title, content and status history of any page.
• Legal, compliance and journalism — dated, archived proof of when terms or policy pages changed.
• Due-diligence teams gauging how often and how heavily a site changes over time.

What you get

Most Wayback "changes" are noise — dynamic tokens, timestamps and whitespace churn that flip the hash without changing anything a human sees. The Actor normalizes content and filters that out, so you get the handful that matter: a price edit, a removed page, a rewritten headline, a page gone dead.

Input

{ "urls": ["stripe.com/pricing", "competitor.com/product"], "from": "2023", "to": "2024", "deepDiff": true, "maxChangesPerUrl": 200 }

Honest limits

• History goes as far as the Wayback Machine captured the URL — thinly-archived pages yield few change points; heavily-archived pages give a dense timeline.
• Large domains are paginated — set date bounds to keep a run focused and affordable; maxDeepDiffsPerUrl bounds the work on noisy pages.
• Only archival metadata and already-public archived content are read — no personal data is collected.

Pricing

Pay per event: a url-lookup per URL checked, a change-event per delivered change row, and a deep-diff per computed content diff (only with deep diff on). Noise-only changes are not emitted and not billed as change events. Current prices are on the actor's Pricing tab on Apify.

Related

For competitor intelligence pair it with the company competitor analysis guide and the SEC filings & entity identity guide; for local-business monitoring, the Naver Place Scraper.

Frequently asked questions

Do I need an API key or a login?

No. You supply only the URLs to monitor. The Actor reads the Internet Archive's public, keyless Wayback Machine CDX API directly — no account, no key, no browser.

What does each change row contain?

A dated change on a URL: the change type (classified), the byte delta, title and HTTP status transitions, a meaningful text diff with boilerplate noise filtered out, and an archived proof link to the Wayback snapshot of that change.

How is this different from a raw snapshot dump?

A raw dump gives you every capture, most identical. This returns a change timeline: only the captures where something actually changed, classified and diffed, so you see signal instead of noise.

Can I monitor a whole domain?

Yes — use matchType: domain to cover a site's URLs (or prefix/host). Large domains are paginated, so set date bounds to keep a run focused and affordable.

How is noise handled?

With deep diff on, the Actor normalizes the content and compares archived bodies, filtering dynamic tokens, timestamps and whitespace churn so the diff reflects real content change. Noise-only changes are not emitted and not billed as change events.

Using the data lawfully

Data comes from the public Internet Archive Wayback Machine CDX API (keyless, documented). Only archival metadata and already-public archived page content are read; no personal data is collected. Use the output in line with applicable laws and the source's terms.