
Sitemap Change Orchestrator
Pricing
Pay per usage

Sitemap Change Orchestrator
Monitor website sitemaps for new, updated, or removed URLs. Integration with the Website Content Crawler (WCC) allows feeding only relevant URLs. This ensures your web crawls are efficient, targeted, and resource-optimized, keeping your datasets fresh for any application.
0.0 (0)
Pricing
Pay per usage
1
Total users
2
Monthly users
2
Runs succeeded
88%
Last modified
21 hours ago
Monitor sitemaps, detect changes, orchestrate content crawls, and merge results into a single dataset.
What is Sitemap Change Orchestrator?
This actor orchestrates running the Sitemap Change Detector to identify changed URLs in sitemaps and then triggers parallel Website Content Crawler runs to fetch page content. Finally, it merges and deduplicates all crawler outputs by URL into one unified dataset.
Key Features
- Detect sitemap changes (NEW, UPDATED, REMOVED, SAME)
- Orchestrate parallel crawl runs with configurable memory and timeout
- Merge and dedupe Website Content Crawler results into a single output
- Store and retrieve sitemap snapshots in a named key-value store
How it Works
- Run the Sitemap Change Detector with your settings
- Collect changed URLs and batch them into Website Content Crawler runs
- Trigger Website Content Crawler runs in parallel
- Merge and dedupe all crawler run datasets by URL
How to Use
- Open the Sitemap Change Orchestrator actor on the Apify Store.
- Configure memory, timeouts, and whether to skip crawling.
- Paste your Website Content Crawler JSON input.
- Set WCC batching options.
- Save and click Run.
- Review merged and deduplicated output in the default dataset.
Example Input
{"addRemovedUrlsToKvs": false,"addWccUrlsToScd": true,"changeTypes": ["NEW", "UPDATED"],"discoverSitemaps": true,"skipWcc": false,"snapshotKeyPrefix": "APIFY","wccInput": {"startUrls": [{"url": "https://www.apify.com","method": "GET"}]// ...}}
Output
- Merged and deduplicated output from all Website Content Crawler runs in the default dataset
- Additionally, sitemap snapshots and removed-URL lists are stored in a named key-value store under your prefix
FAQ
Can I export data using API?
Yes, you can access this actor using your own applications through the Apify API. Click on the API tab for code examples or check out the Apify API reference docs at https://docs.apify.com/api/v2 for full details.
Can I use Sitemap Change Orchestrator through an MCP Server?
This actor, like all Apify actors, works on the Apify MCP server. For more information and instructions, read the Apify MCP server integration guide at https://docs.apify.com/platform/integrations/mcp.
Can I integrate data from Sitemap Change Orchestrator with other apps?
Yes. Sitemap Change Orchestrator can be connected with almost any cloud service or web app. Read more about the possibilities on our integrations page at https://apify.com/integrations.
Is it legal to scrape data using Sitemap Change Orchestrator?
This actor only extracts publicly available data. It does not collect private user data. However, you should ensure your reason for scraping is legitimate. Consult legal counsel if unsure. For more on scraping legality and ethics, see:
- https://blog.apify.com/is-web-scraping-legal/
- https://blog.apify.com/what-is-ethical-web-scraping-and-how-do-you-do-it/
Your feedback
We welcome feedback to improve this actor. If you encounter issues or have suggestions, please create an issue on the actor’s Issues tab.
On this page
Share Actor: