# Website Change Diff Monitor (`junipr/website-change-diff-monitor`) Actor

Monitor public webpages for meaningful changes in title, headings, body sections, CTAs, links, schema, scripts, screenshots, and key selectors between...

- **URL**: https://apify.com/junipr/website-change-diff-monitor.md
- **Developed by:** [junipr](https://apify.com/junipr) (community)
- **Categories:** Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $11.50 / 1,000 target checkeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Website Change Diff Monitor

Monitor public webpages for meaningful changes in title, headings, body sections, CTAs, links, schema, scripts, screenshots, and key selectors between snapshots.

### What it does

Compares baseline and current public-page snapshots across titles, headings, body text, CTAs, links, schema, scripts, and watched selectors.

The actor emits one row per normalized change, or an honest baseline/no-change diagnostic. Dataset and report output is produced only after every applicable PPE charge is accepted.

### Common uses

- Monitor website page changes
- Track competitor homepage updates
- Detect CTA and offer changes
- Compare launch snapshots
- Export web change alerts

### Input

Supply public HTTP(S) URLs or deterministic `htmlInputs`. URL fetching rejects localhost and private-network destinations; `allowedDomains` can narrow access further.

- `startUrls`
- `sitemapUrls`
- `htmlInputs`
- `allowedDomains`
- `maxPages`
- `maxDepth`
- `includeEvidence`
- `includeRawSnapshots`
- `requestDelayMs`
- `timeoutMs`
- `userAgentMode`
- `watchUrls`
- `baselineSnapshots`
- `fetchCurrent`
- `changeRules`
- `selectorWatchlist`
- `ignorePatterns`
- `includeScreenshots`
- `maxTargets`
- `maxSnapshots`
- `maxChanges`
- `maxChargeUsd`
- `includeReport`

The caps in `maxTargets, maxPages, maxSnapshots, maxChanges, timeoutMs` and `maxChargeUsd` are enforced. A zero charge cap is a hard zero budget.

### Output

- `sourceUrl`
- `sourceType`
- `pageTitle`
- `recordType`
- `recordName`
- `issueCode`
- `severity`
- `evidenceSnippet`
- `recommendation`
- `canonicalUrl`
- `httpStatus`
- `scannedAt`
- `watchUrl`
- `changeType`
- `selector`
- `oldValue`
- `newValue`
- `changeMagnitude`
- `ignoredByRule`
- `screenshotKey`
- `diffSnippet`
- `alertPriority`

Reports:

- `website-change-diff-monitor-summary-report.md`
- `website-change-diff-monitor-records.csv`
- `website-change-diff-monitor-issues.json`
- `website-change-diff-monitor-evidence-samples.json`
- `website-change-diff-monitor-run-metadata.json`

### Pricing

Platform-usage pass-through is off. Locked fixed-inclusive events:

| Event | Price |
| --- | ---: |
| `actor-start` | $0.035 |
| `target-checked` | $0.0115 |
| `snapshot-compared` | $0.0115 |
| `change-detected` | $0.0225 |
| `digest-generated` | $0.09 |
| `executive-report-generated` | $0.18 |

The actor charges `actor-start` before fetching/rendering, deduplicates page events, charges record/finding events only for corresponding output, and stops before further output on partial, limited, or over-budget charges. Screenshot events fire only when a real browser PNG exists.

### Safety and limitations

- Public pages only; no authentication, CAPTCHA bypass, access-control evasion, or private data.
- Browser waits, pages, records, changes, forms, popups, and screenshots are bounded.
- Blocked, empty, and missing-baseline cases produce diagnostics instead of invented success.
- Results describe source evidence at scan time and may change later.
- Store discounts, icons, publication, and scheduler state are separate live configuration gates.

### Local validation

```bash
pnpm --filter @junipr/website-change-diff-monitor build
pnpm --filter @junipr/website-change-diff-monitor test
pnpm --filter @junipr/website-change-diff-monitor smoke
```

Fixtures cover success, weak/blocked evidence, comparison, no-result, and cap behavior. Tests also prove schema equality, pricing metadata, charge guards, zero budget, reports, and charge-before-output ordering.

# Actor input Schema

## `startUrls` (type: `array`):

startUrls for Website Change Diff Monitor.

## `sitemapUrls` (type: `array`):

sitemapUrls for Website Change Diff Monitor.

## `htmlInputs` (type: `array`):

htmlInputs for Website Change Diff Monitor.

## `allowedDomains` (type: `array`):

allowedDomains for Website Change Diff Monitor.

## `maxPages` (type: `integer`):

maxPages for Website Change Diff Monitor.

## `maxDepth` (type: `integer`):

maxDepth for Website Change Diff Monitor.

## `includeEvidence` (type: `boolean`):

includeEvidence for Website Change Diff Monitor.

## `includeRawSnapshots` (type: `boolean`):

includeRawSnapshots for Website Change Diff Monitor.

## `requestDelayMs` (type: `integer`):

requestDelayMs for Website Change Diff Monitor.

## `timeoutMs` (type: `integer`):

timeoutMs for Website Change Diff Monitor.

## `userAgentMode` (type: `string`):

userAgentMode for Website Change Diff Monitor.

## `watchUrls` (type: `array`):

watchUrls for Website Change Diff Monitor.

## `baselineSnapshots` (type: `array`):

baselineSnapshots for Website Change Diff Monitor.

## `fetchCurrent` (type: `boolean`):

fetchCurrent for Website Change Diff Monitor.

## `changeRules` (type: `array`):

changeRules for Website Change Diff Monitor.

## `selectorWatchlist` (type: `array`):

selectorWatchlist for Website Change Diff Monitor.

## `ignorePatterns` (type: `array`):

ignorePatterns for Website Change Diff Monitor.

## `includeScreenshots` (type: `boolean`):

includeScreenshots for Website Change Diff Monitor.

## `maxTargets` (type: `integer`):

maxTargets for Website Change Diff Monitor.

## `maxSnapshots` (type: `integer`):

maxSnapshots for Website Change Diff Monitor.

## `maxChanges` (type: `integer`):

maxChanges for Website Change Diff Monitor.

## `maxChargeUsd` (type: `number`):

maxChargeUsd for Website Change Diff Monitor.

## `includeReport` (type: `boolean`):

includeReport for Website Change Diff Monitor.

## Actor input object example

```json
{
  "startUrls": [],
  "sitemapUrls": [],
  "htmlInputs": [
    {
      "sourceUrl": "https://example.com/home",
      "previousHtml": "<title>Old</title><h1>Old offer</h1><a href='/trial'>Start trial</a>",
      "html": "<title>New</title><h1>New offer</h1><a href='/demo'>Book demo</a>"
    }
  ],
  "allowedDomains": [],
  "maxPages": 5,
  "maxDepth": 5,
  "includeEvidence": false,
  "includeRawSnapshots": false,
  "requestDelayMs": 5,
  "timeoutMs": 5,
  "userAgentMode": "",
  "watchUrls": [],
  "baselineSnapshots": [],
  "fetchCurrent": false,
  "changeRules": [],
  "selectorWatchlist": [],
  "ignorePatterns": [],
  "includeScreenshots": false,
  "maxTargets": 3,
  "maxSnapshots": 5,
  "maxChanges": 10,
  "maxChargeUsd": 35,
  "includeReport": true
}
```

# Actor output Schema

## `results` (type: `string`):

No description

## `report` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("junipr/website-change-diff-monitor").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("junipr/website-change-diff-monitor").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call junipr/website-change-diff-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,junipr/website-change-diff-monitor"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/2h2jOkk97rSr1fWok/builds/DcKtgCFeCQJ2gOH1r/openapi.json