# Sitemap Indexability & Change Monitor (`produkdigitalali/sitemap-indexability-change-monitor`) Actor

Audit XML sitemap URLs for HTTP status, robots directives, canonical targets, indexability, and added, removed, or changed pages across repeat runs.

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

## Pricing

$2.00 / 1,000 page auditeds

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

## Sitemap Indexability & Change Monitor

Audit public XML sitemaps, check whether every listed page is indexable, and detect changes between scheduled runs.

### What it checks

For every discovered URL, the Actor returns:

- HTTP status
- robots and Googlebot meta directives
- canonical URL
- indexability status
- sitemap lastmod value
- issue codes
- ADDED, CHANGED, UNCHANGED, or REMOVED status compared with the previous snapshot

### Why use it

Use the Actor for SEO release checks, site migrations, ecommerce catalog monitoring, publishing workflows, and recurring sitemap hygiene. A stable named snapshot lets an Apify Task compare the same site each day or after every deployment.

### Input

Provide one to ten public sitemap or sitemap-index URLs. Start with a small maxUrls value. Keep comparePrevious enabled and reuse snapshotStoreName for recurring monitoring.

Example:

```
{
  "sitemapUrls": ["https://apify.com/sitemap.xml"],
  "maxUrls": 100,
  "comparePrevious": true,
  "snapshotStoreName": "my-site-sitemap-monitor",
  "requestTimeoutSeconds": 15,
  "maxUserChargeUsd": 1
}
```

### Output

Each dataset row represents one sitemap URL. SUMMARY contains discovered, audited, added, changed, removed, issue, failure, and charging counts.

Common issue codes include NON\_2XX\_STATUS, NOINDEX, MISSING\_CANONICAL, CANONICAL\_TO\_OTHER\_URL, NON\_HTML\_CONTENT, FETCH\_FAILED, and REMOVED\_FROM\_SITEMAP.

### Safety and limits

The Actor accepts public HTTP and HTTPS destinations only. It validates every redirect and blocks private, local, reserved, and special-use networks. It caps seed sitemaps, discovered URLs, sitemap documents, redirects, response size, request duration, and Actor charges. It never requires or logs third-party credentials or page response bodies.

### Pricing

The proposed pay-per-event price is $0.002 per successfully stored page audit. Set maxUserChargeUsd to control the maximum Actor event charge. Apify compute and storage usage may be billed separately according to the user's plan.

### Limitations

Indexability is inferred from the fetched HTTP response and HTML directives. It does not query Google Search Console or guarantee search-engine indexing. JavaScript-injected metadata is not rendered. Temporary network errors are reported as failures rather than treated as definitive SEO findings.

# Actor input Schema

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

Public XML sitemap or sitemap-index URLs.

## `maxUrls` (type: `integer`):

Hard cap across all sitemaps.

## `comparePrevious` (type: `boolean`):

Compare with a named previous snapshot.

## `snapshotStoreName` (type: `string`):

Stable key-value store name for repeat runs.

## `requestTimeoutSeconds` (type: `integer`):

Timeout for each public request.

## `maxUserChargeUsd` (type: `number`):

Stops before the estimated Actor event charge exceeds this amount.

## Actor input object example

```json
{
  "sitemapUrls": [
    "https://www.example.com/sitemap.xml"
  ],
  "maxUrls": 100,
  "comparePrevious": true,
  "snapshotStoreName": "sitemap-indexability-monitor",
  "requestTimeoutSeconds": 15,
  "maxUserChargeUsd": 1
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

## `summary` (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("produkdigitalali/sitemap-indexability-change-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("produkdigitalali/sitemap-indexability-change-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 produkdigitalali/sitemap-indexability-change-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,produkdigitalali/sitemap-indexability-change-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/NucqTZV2UPoWlmadm/builds/qErKQwWdeIKAc8u4y/openapi.json