# Sitemap URL Extractor: All Pages, lastmod & hreflang (`iveeeeeen/sitemap-url-extractor-pro`) Actor

Extract every URL from a website's XML sitemaps: auto-discovers sitemaps via robots.txt and common paths, follows sitemap indexes, handles .gz and text sitemaps. Returns lastmod, changefreq, priority, hreflang, images, video. Filter by regex or date.

- **URL**: https://apify.com/iveeeeeen/sitemap-url-extractor-pro.md
- **Developed by:** [Ivan Alvarado](https://apify.com/iveeeeeen) (community)
- **Categories:** SEO tools, Developer tools, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$0.30 / 1,000 url extracteds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Sitemap URL Extractor: Get Every Page URL with lastmod, hreflang & Images

**Extract all URLs from any website's XML sitemaps in seconds.** Give it a domain and it finds the sitemaps for you (robots.txt `Sitemap:` lines, `/sitemap.xml`, `/sitemap_index.xml`, `/wp-sitemap.xml`), follows sitemap indexes recursively, and reads **gzip (.xml.gz)** and **plain-text** sitemaps.

### What you get for each URL

`url`, `lastmod`, `changefreq`, `priority`, **hreflang alternates**, **image count**, **video flag**, news title, and the source sitemap. A per-site summary records how the sitemaps were discovered, how many were read, and any errors.

### Filters

- `includePattern` / `excludePattern`: regex filters (for example, only `/blog/` or `/products/`)
- `modifiedAfter`: only pages changed since a date, which is great for **monitoring new or updated content** on a schedule
- `maxUrlsPerSite`: cap the volume and the cost

### Use cases

Crawl planning (feed URLs into other Actors), SEO audits and indexation checks, competitor content monitoring, migration URL inventories, finding all product or blog pages, and building RAG and LLM ingestion lists.

### Input example

```json
{ "startUrls": ["https://crawlee.dev", "https://apify.com/sitemap.xml"], "maxUrlsPerSite": 1000, "includePattern": "/blog/", "modifiedAfter": "2026-01-01" }
```

### Output example

```json
{ "site": "https://crawlee.dev", "url": "https://crawlee.dev/blog", "lastmod": null, "changefreq": "weekly", "priority": 0.5, "alternates": [], "imageCount": 0, "hasVideo": false, "sitemap": "https://crawlee.dev/sitemap.xml" }
```

### Pricing (pay per event)

**$0.0003 per URL extracted** ($0.30 per 1,000 URLs). You pay only for URLs saved after your filters, and duplicates are removed for free.

### FAQ

**The site has no sitemap?** You get zero results and pay nothing. The run log and the `SUMMARY-<host>` record say so.
**Does it crawl pages?** No. It only reads the sitemap files the site publishes for crawlers.

# Actor input Schema

## `startUrls` (type: `array`):

A domain/homepage (sitemaps auto-discovered from robots.txt and common paths) or a direct sitemap URL (.xml, .xml.gz, .txt).

## `maxUrlsPerSite` (type: `integer`):

Stop after this many URLs per site. This also caps cost (one url-extracted event per URL).

## `includePattern` (type: `string`):

Only output URLs matching this regex, e.g. /blog/ or /products/.

## `excludePattern` (type: `string`):

Skip URLs matching this regex, e.g. /tag/|/page/

## `modifiedAfter` (type: `string`):

Only URLs whose <lastmod> is on/after this date (YYYY-MM-DD). URLs without lastmod are skipped when set.

## `maxSitemapsPerSite` (type: `integer`):

Safety cap on how many sitemap files are read per site.

## Actor input object example

```json
{
  "startUrls": [
    "https://crawlee.dev"
  ],
  "maxUrlsPerSite": 1000,
  "maxSitemapsPerSite": 200
}
```

# Actor output Schema

## `urls` (type: `string`):

All URLs with lastmod, changefreq, priority, images, video and source sitemap.

## `hreflang` (type: `string`):

Language alternates per URL.

## `summaries` (type: `string`):

Key-value store records SUMMARY-<host>.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "startUrls": [
        "https://crawlee.dev"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("iveeeeeen/sitemap-url-extractor-pro").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "startUrls": ["https://crawlee.dev"] }

# Run the Actor and wait for it to finish
run = client.actor("iveeeeeen/sitemap-url-extractor-pro").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "startUrls": [
    "https://crawlee.dev"
  ]
}' |
apify call iveeeeeen/sitemap-url-extractor-pro --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,iveeeeeen/sitemap-url-extractor-pro"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/K0k5QGMc8euyZU7lf/builds/puxPM9yy4HdyRbPDL/openapi.json