# Get alerts when a blog's pages change content

**Use case:** 

Monitors a site's blog pages (here the Node.js blog, picked from the sitemap with an include pattern): each page is fetched, scoped to the main article, stripped of numbers and dates so counters do not trigger alerts, hashed and compared with the previous run. You get content-changed, status-changed, new-url and removed-url records with a word-level diff preview; the first run writes the baseline.

## Input

```json
{
  "sites": [
    "https://nodejs.org/sitemap.xml"
  ],
  "mode": "monitor",
  "checkContent": true,
  "contentSelector": "main, article, body",
  "ignoreNumbers": true,
  "maxPages": 30,
  "includePatterns": [
    "https://nodejs.org/en/blog/*"
  ],
  "maxConcurrency": 3,
  "stateStoreName": "website-change-monitor-nodejs-blog",
  "resetBaseline": false,
  "notifyOnlyOnChanges": true
}
```

## Output

```json
{
  "changeType": {
    "label": "Type",
    "format": "text"
  },
  "url": {
    "label": "URL",
    "format": "link"
  },
  "title": {
    "label": "Title",
    "format": "text"
  },
  "lastmod": {
    "label": "Last modified",
    "format": "text"
  },
  "status": {
    "label": "Status",
    "format": "text"
  },
  "changefreq": {
    "label": "Change freq",
    "format": "text"
  },
  "detectedAt": {
    "label": "Detected at",
    "format": "date"
  },
  "error": {
    "label": "Error",
    "format": "text"
  }
}
```

## How it works

### 1. Sign up on Apify or log in

The Website Change Monitor — Sitemap & Page Content Diff Actor is ready to run with the inputs already set for "Get alerts when a blog's pages change content". [Sign up or log in](https://console.apify.com/create-task-from-example/NlstA1Q35oaHGNmjY) and you'll land in Apify Console with a copy of this exact task.

### 2. Start the "Get alerts when a blog's pages change content" task

The Website Change Monitor — Sitemap & Page Content Diff Actor will start running based on the input automatically. You can also change all the input fields, like sites or sitemap urls, mode, and more, to match your specific use case.

### 3. Receive the "Get alerts when a blog's pages change content" output

Monitor the progress in real time. You will be notified as soon as your dataset is complete and ready for review. Each result includes data such as type, URL, title, and more.

### 4. Integrate into your workflow

The final output is delivered in JSON, CSV, or Excel format, ready to be plugged into your workflow. You can also [run the "Get alerts when a blog's pages change content" task via API](https://apify.com/owlabee/website-change-monitor.md).

## About this Actor

This example demonstrates how to use [Website Change Monitor — Sitemap & Page Content Diff](https://apify.com/owlabee/website-change-monitor.md) with a specific input configuration. Visit the [Actor detail page](https://apify.com/owlabee/website-change-monitor.md) to learn more, explore other use cases, and run it yourself.


## How to integrate an Actor?

This Task's input is already configured above. Use it as-is rather than inventing a new one.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For full API examples (JavaScript, Python, CLI, MCP, OpenAPI), see this Task's Actor page: https://apify.com/owlabee/website-change-monitor.md

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).