Sitemap URL Inventory - New, Changed & Removed URLs

Sitemap URL Inventory — a dependable feed of published URL changes

Find newly listed product pages, documentation URLs and competitor content from XML sitemaps. Re-run the same scope to see additions, metadata changes and URLs absent from the next complete inventory.

For SEO agencies, content researchers and AI ingestion teams. Each observation keeps the exact URL, sitemap evidence, publisher-supplied metadata and comparison status. A removal means absent from these sitemaps; it does not prove the web page was deleted.

Try it

Empty input reads the official sitemaps.org XML sitemap. A smaller first run:

{"sitemapUrls":["https://www.sitemaps.org/sitemap.xml"],"urlPrefixes":["https://www.sitemaps.org/protocol.html","https://www.sitemaps.org/faq.html","https://www.sitemaps.org/terms.html"],"maxResults":10}

1. Paste your XML sitemap URLs or sitemap-index URLs.
2. Start with a small scope. Open the dataset and the readable run report.
3. For recurring monitoring, save the input as an Apify task, enable comparison and reuse the snapshot name. Run a snapshot sequentially.

What makes the changes usable

• Follows bounded same-origin sitemap indexes and supports gzip sitemap files.
• Deduplicates page URLs across maps while retaining every source map.
• Saves one URL observation per result, with no fabricated page titles or dates.
• Emits removals only after a complete inventory. A network error, truncated map, output cap or spending stop leaves the previous baseline intact.
• Supplies the same structured output to the Apify API, MCP tools, scheduled tasks and spreadsheet exports.

Three input recipes

English documentation pages: the first-run input above.

German documentation inventory:

{"sitemapUrls":["https://www.sitemaps.org/sitemap.xml"],"urlPrefixes":["https://www.sitemaps.org/de/"],"maxResults":20}

Full official sitemap:

{"sitemapUrls":["https://www.sitemaps.org/sitemap.xml"],"maxResults":100}

Inputs

Input	Default	Purpose
sitemapUrls	Official sitemaps.org map	Up to10 public XML maps or indexes
urlPrefixes	none	Select output by absolute URL prefix; all maps still read
maxSitemaps	20	Root and child sitemap request cap, up to100
maxUrls	5000	Unique URLs inventoried before filters, up to10000
maxResults	100	Saved output rows including removals, up to10000
comparePrevious	false	Compare only complete inventories
onlyChanges	false	Implies comparison; unchanged repeats can return zero rows
snapshotName	default	Independent history scope; letters/numbers/underscore/hyphen
maxRunSeconds	90	Shared deadline,30–900seconds, also limited by the platform

Output

One saved row is one URL observation. Fields: url, title (the URL itself), recordId, lastmod, changefreq, priority, sitemapUrls, sourceUrl, observedAt, presence, inventoryComplete, comparisonStatus, changedFields, previousObservedAt and previous. Optional metadata is null when absent. Publisher metadata is kept as text, without inventing a date, priority or page title.

Comparison statuses: not_requested, baseline, added, changed, unchanged, removed, or not_compared_incomplete. The SUMMARY record reports exact coverage, failures, limits and whether history was updated. RUN_REPORT is a self-contained HTML view. JSON preserves nested evidence; CSV is useful for flat URL inventories.

Pricing

Base price: $0.50 per1,000 saved URL observations, plus the configured $0.00005 Actor Start event. Saved removal observations have the same price. An unchanged row is charged when saved; onlyChanges skips it. Failed source requests and summary/report records are not dataset result events. Check the Pricing tab for your plan's discounts. Use the run maximum-charge control to bound spending.

Coverage and limits

XML urlset and sitemapindex, optionally gzip, only. RSS/Atom/text feeds, images/video extension extraction and cross-origin child maps are unsupported. Each response has a4MiB wire and decoded body cap; one XML map supports at most10000 entries. Public HTTP(S) only with robots.txt, DNS and redirect validation. No login, proxies or browser rendering. The Actor reads maps; it never visits every listed web page or claims to know Google indexing. lastmod, changefreq and priority are publisher statements, not verified changes or ranking scores. The same root-map and prefix scope identifies a saved baseline; changing it starts independent history. Concurrent writes are checked but the platform store is not transactional: run a snapshot sequentially.

Use in workflows

Schedule the saved task, read SUMMARY after success, then route complete added/changed rows into your crawler, research queue or AI index. Route removed rows for review before deleting downstream content. Partial source observations remain explicitly marked. Use the Apify REST API or the Actor's MCP integration with your own Apify authentication.

Independent tool by May'd It. Source format: https://www.sitemaps.org/protocol.html . Support: open an issue with the sitemap URL, relevant input and expected result; omit credentials.