Skip to main content
Map quickly discovers URLs from sitemaps and sitemap indexes. It does not fetch discovered pages, recursively traverse links, index content, or use cached crawl data. For recursive discovery and content, use Deep Crawl. In the dashboard, open Playground → Map, enter a website, and select Map now. The run page updates automatically. It shows discovered URLs and discovery warnings. The result card always displays the complete array of discovered URLs, with copy and download actions. Use Runs → Maps to find previous map runs. Cancellation, retry, and deletion work like crawl.

Create a map

The endpoint requires runs:write and returns a pending run. Poll GET /api/v1/runs/{id} with runs:read. When status is completed, read result_data.links. The same request can be sent to POST /api/v1/runs.
The Python SDK supports both synchronous and asynchronous clients:

Options

Coverage is approximate. Sitemap discovery is bounded to 100 documents and 5 MiB per decoded document. Maps may be empty or include stale sitemap URLs; check result_data.warnings. The search option filters sitemap URLs by case-insensitive keyword matches, including decoded URL text. URLs matching at least one word are ordered by relevance before applying the limit. No matches returns an empty array. It does not call a web-search provider. Map runs consume execution capacity but no processed-page quota. Results live on the run; /runs/{id}/results remains the endpoint for ingestion results from crawl and extract.

Local crawler library and CLI

Library and local CLI calls return the result directly and do not create a server run.