Sitemap URL Inventory & Change Monitor
Pricing
from $2.80 / 1,000 results
Sitemap URL Inventory & Change Monitor
A direct sitemap inventory utility: sitemap URLs in, normalized URL inventory and changes out, with freshness and removal-risk signals.
Pricing
from $2.80 / 1,000 results
Rating
0.0
(0)
Developer
Rafael Barreto Haddad
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
11 days ago
Last modified
Categories
Features
Share
A direct sitemap inventory utility: sitemap URLs in, normalized URL inventory and changes out, with freshness and removal-risk signals.
Why use this Actor
SEO teams need to know which site sections gained or lost indexed inventory and whether sitemap changes correlate with canonical, noindex, lastmod or availability regressions before traffic is affected.
Key features
- Buyer-native inputs aligned to seo monitoring.
- Predictable structured output in the default Apify Dataset.
- Pay Per Event pricing tied to measurable result rows or reports.
- Optional MCP connector delivery for downstream automation and AI agents.
Quick start
Start with this working example and replace the target values with your own:
{"currentSitemapUrl": "https://www.djangoproject.com/sitemap.xml","pageAuditSample": 2}
The Actor writes structured results to the default Apify Dataset and can be used from the Store, API, schedules, Tasks, automations and MCP-compatible AI workflows.
Input
previousSitemapUrl— Previous sitemap URL: Optional previous public sitemap URL.currentSitemapUrl— Current sitemap URL: Current public sitemap.xml or sitemap index URL.previousUrls— Previous URLs: Optional explicit baseline URL list.currentUrls— Current URLs: Optional explicit current URL list.maxSitemapFiles— Maximum sitemap files: Maximum recursively followed sitemap files.maxUrls— Maximum URLs: Maximum URLs read from the sitemap.
All integration and advanced analysis fields are optional. The default example is intentionally runnable without configuring MCP or a previous-run baseline.
Output
The Dataset exposes predictable machine-readable output. Representative fields include results.
Pricing
This Actor uses Pay Per Event. The current factory base price is $0.004000 per result event. The Apify Store remains the source of truth for the price and plan/tier details shown to the buyer.
Use cases
- Run the buyer-ready workflows exposed as Apify Tasks without preparing a custom integration first.
- Use the Actor from API or schedules for recurring collection, comparison or monitoring.
- Feed the structured Dataset output into spreadsheets, databases, automations or AI agents.
- Compare repeat runs when the product supports snapshots or previous-run inputs.
Automation and AI
Use the same Actor through Apify API, schedules, public Tasks and the Apify MCP server. Outputs are structured for downstream workflows and AI agents rather than requiring manual copy/paste.
Limitations
- Public websites and upstream APIs can change markup, access rules, rate limits or field availability without notice.
- Fields that are not publicly available are returned as unavailable or omitted rather than fabricated.
- Analytical outputs depend on the quality and coverage of the supplied or collected source data.
- Treat marketplace, reputation, workforce, safety or commercial signals as decision support and validate material decisions against the underlying source evidence.
Detailed documentation
Give sitemap URLs or URL lists. Compare inventories, detect additions and removals, and return structured sitemap change and freshness issues.
Why use this Actor
A sitemap can look valid while hiding commercially important problems: mass removals, stale or fake lastmod dates, noindex pages still advertised to crawlers, canonical drift, or URLs that now fail. Traditional sitemap extractors stop at the XML. This Actor connects sitemap change evidence with sampled live-page evidence so monitoring can focus on what deserves action.
Key features
- Recursive sitemap and sitemap-index parsing, including gzip.
- Added and removed URL detection with deterministic inventory fingerprints.
- Missing, invalid, future and stale lastmod diagnostics.
- Sampled live-page checks for HTTP failures, robots noindex and canonical mismatches.
- Reusable content fingerprints to verify whether a page actually changed between runs.
seoRiskScore,agentAction,agentReasonand structured issues for automation.- Lean HTTP-first 256 MB runtime with bounded page sampling.
Input
Provide a current sitemap URL, optional previous sitemap URL, or explicit previous/current URL inventories. pageAuditSample controls how many live pages receive deeper checks. Previous page fingerprints can be fed back into a later run to verify content change.
Output
One structured intelligence report containing inventory counts and diffs, lastmod diagnostics, sampled page audit evidence, SEO risk, recommended action, fingerprints, and issue codes.
Example
Use currentSitemapUrl: https://www.djangoproject.com/sitemap.xml with pageAuditSample: 5 to create a current inventory and audit a bounded set of pages for canonical, noindex and availability issues. Save currentPageFingerprints and reuse them on the next run.
Use cases
Technical SEO monitoring, migration QA, ecommerce catalog governance, publisher freshness monitoring, competitor content expansion analysis, RAG ingestion freshness, release gates, and AI-agent workflows that need compact SEO evidence.
Pricing
Pay per completed intelligence report. The design intentionally avoids browser-heavy crawling by default and keeps live page checks bounded, preserving predictable cost.
Limitations
This is public-web evidence, not access to Google Search Console or a guarantee of indexing. Page-level checks are sampled unless the user raises the sample size. Some sites block automated requests or return region-specific responses.
Real-data first-run guide
This Actor operates on real public URLs, DNS records, API documentation or official feeds supplied in the input. It does not manufacture externally observed records. Use only destinations you are authorized to inspect and stay within endpoint rate limits.
Suggested live test input:
{"currentSitemapUrl": "https://www.djangoproject.com/sitemap.xml","pageAuditSample": 2}
If the source is inaccessible or incomplete, verify the returned error or limited-coverage indicators. No real customer use or performance claim can be inferred from synthetic local fixtures. Existing Pay Per Event price and product ID are preserved.