Sitemap New Page Monitor — competitor content radar

Watch any website's sitemap on a schedule and get only the NEW and UPDATED pages since your last run. Every page a competitor publishes shows up in their sitemap — this Actor turns that into a live feed of their content strategy.

SEO teams pay serious money for "competitor content monitoring". The raw signal is free and sitting in sitemap.xml: what they published, what they refreshed, what they deleted. What's missing is the memory and the diff — that's what this Actor adds.

What it does

1. Auto-discovers each site's sitemap: direct .xml/.xml.gz URL, robots.txt Sitemap: declaration, or the conventional /sitemap.xml — with sitemap-index recursion and gzip support.
2. Reads every page URL and its <lastmod>.
3. Compares against the previous run and outputs:
   • changeType: "new" — pages that didn't exist before (their new content),
   • changeType: "updated" — pages whose lastmod changed (their content refreshes),
   • removed-page counts in the run summary.

Input example

{
  "siteUrls": [
    "https://competitor-a.com",
    "https://competitor-b.com/sitemap.xml"
  ]
}

The defaults work as-is.

Output example

{
  "siteUrl": "https://competitor-a.com",
  "pageUrl": "https://competitor-a.com/blog/new-feature-announcement",
  "lastmod": "2026-07-06T08:00:00.000Z",
  "changeType": "new",
  "isBaseline": false,
  "detectedAt": "2026-07-07T06:00:00.000Z"
}

A SUMMARY record in the run's key-value store gives the per-site picture: pages in sitemap, new/updated/removed counts, which sitemap was used, truncation flags.

How to use it

• Competitor content watch: weekly schedule on your competitors → every new blog post, landing page or product page they ship, in your inbox before it ranks.
• SEO agencies: one monitor per client vertical; new competitor pages = fresh brief opportunities for your client.
• Your own site: catch pages accidentally dropped from your sitemap (removedPages in the summary) — a classic silent SEO regression.

Fair use & data

• Reads only robots.txt and sitemap files — the two files websites publish specifically for automated readers.
• No page content is fetched, no personal data collected.
• Hard caps (10 sites, 50 sitemap files, 20k pages per site) keep runs bounded; truncation is always flagged, never silent.

FAQ

A site has no sitemap? The run summary reports the error for that site and the others still work.

Huge site (100k+ pages)? Raise maxUrlsPerSite up to 20k, or point siteUrls at the specific sub-sitemap you care about (e.g. sitemap-blog.xml).

First run floods me. That's the baseline (flagged isBaseline: true); disable includeBaselineInOutput to start silent.

How do I reset the memory? Set a new monitorId.