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.