Chipotle Locations Scraper

Extract every Chipotle restaurant page URL in the US directly from Chipotle's public store locator sitemap — no browser, no login, no API key. This Chipotle scraper walks the sitemap index, filters out non-store pages, and returns one clean, deduplicated link per restaurant, ready to feed into further scraping, geocoding, or a metadata Actor.

Run it on demand or on a schedule, pull results through the Apify API, and connect it to Zapier, Make, or n8n for hands-off delivery of fresh Chipotle location data.

What can Chipotle Locations Scraper do?

• 🌮 Scrapes the full Chipotle store locator sitemap — every US restaurant page URL, filtered to real store pages (ordering pages excluded).
• 🔗 Deduplicates automatically — each restaurant URL appears once, even if the sitemap changes between requests.
• 🎯 Max results control — collect a quick sample (default 50) or set 0 to pull the entire catalog (~4,000+ links).
• ⏭️ Resumable pagination — startIndex and excludeUrls let you pick up where a previous run left off without re-collecting (or re-paying for) links you already have.
• 🔁 Crash-safe checkpointing — a migrated or restarted run resumes from where it stopped instead of starting over.
• 📤 Multiple export formats — download results as JSON, CSV, Excel, or HTML straight from the Output tab.
• ☁️ Built for the Apify platform — schedule recurring runs, trigger via the REST API, monitor run history, and integrate with Zapier/Make/n8n webhooks.
• 🤝 Pairs with the Chipotle Restaurant Metadata Actor to turn these links into full store details (address, phone, geolocation, hours).

What data does Chipotle Locations Scraper extract?

Each dataset item represents one Chipotle restaurant page link:

Field	Description
url	Full URL of the Chipotle restaurant location page
coordinate	Source label identifying where the link was discovered (currently static source)
extraction_datetime	UTC timestamp (ISO 8601) when the link was collected
extraction_date	Extraction date in mm-dd-yyyy format

How do I use Chipotle Locations Scraper to scrape Chipotle store URLs?

1. Click Try for free or open the Actor and go to the Input tab.
2. Optionally set Max results, Start index, and/or Exclude collected links — see Input below. The defaults work out of the box.
3. Click Start and wait for the run to finish.
4. Open the Output tab and export your Chipotle location links as JSON, CSV, Excel, or HTML.

Input

The Actor accepts three optional inputs — you can also just click Start and use the defaults:

• Max results — the maximum number of unique restaurant links to collect in this run. Default is 50. Set it to 0 to collect every Chipotle location in the sitemap (roughly 4,000+ links); since this Actor can be billed per result, raise it gradually rather than jumping straight to 0.
• Start index — skips this many links from the start before saving any, letting you paginate across multiple runs (e.g. set 500 to continue after already collecting the first 500) without paying again for links you already have.
• Exclude collected links — a list of restaurant URLs you already have. Any link on this list is never saved again, regardless of order — useful when you keep a running list and only want new locations.

Free-plan runs are capped at 10 links per run, and Start index / Exclude collected links are disabled on the free plan to prevent bypassing that cap.

Output example

{
  "url": "https://locations.chipotle.com/al/birmingham/300-20th-st-s",
  "coordinate": "static source",
  "extraction_datetime": "2026-07-21T14:30:00.123456+00:00",
  "extraction_date": "07-21-2026"
}

You can download the dataset in various formats such as JSON, HTML, CSV, or Excel.

Use cases

• Build a Chipotle store directory for a food-delivery, aggregator, or comparison app.
• Feed restaurant URLs into a metadata scraper (like the Chipotle Restaurant Metadata Actor) to pull addresses, phone numbers, hours, and geolocation for every store.
• Track new Chipotle store openings by scheduling recurring runs and comparing link counts over time.
• Power location-based search or store-locator features in an internal tool without hand-maintaining a URL list.
• Feed a market-research or site-expansion dataset with the full list of active Chipotle locations across the US.

Chipotle-related Actors

Actor	What it does
Chipotle Restaurant Metadata (placeholder)	Takes links from this Actor and extracts address, phone, geolocation, and hours for each store

FAQ

Is it legal to scrape Chipotle locations?

This Actor only collects publicly available data from Chipotle's public sitemap — the same URLs search engines index. It does not bypass logins, paywalls, or access any private data. That said, scraping is subject to the target site's Terms of Service; review Chipotle's terms and applicable law before using the extracted data commercially, and consult a legal professional if you're unsure.

Does this Actor extract store hours, phone numbers, or coordinates?

No — this Actor only collects restaurant page URLs. Pair it with the Chipotle Restaurant Metadata Actor to pull hours, phone numbers, addresses, and geolocation for each link.

What's the difference between the free and paid plan?

Free-plan runs are capped at 10 links, and both Start index and Exclude collected links are disabled (forced to their defaults) so a free run can't bypass the cap by paginating across multiple runs.

Can I resume a run without paying twice for the same links?

Yes. If a run is interrupted (e.g. platform migration), it resumes from its checkpoint instead of starting over, so already-collected links aren't re-pushed. Across separate runs, use Start index and Exclude collected links to avoid re-collecting links you already have.

Is there an API for this Actor?

Yes — every Apify Actor run can be triggered and its results retrieved via the Apify API, so you can integrate this scraper into your own app, script, or automation (Zapier, Make, n8n) without touching the Apify Console.

What if the sitemap request gets blocked?

If Chipotle's sitemap blocks the request (anti-bot protection), the affected request is logged and the run fails gracefully rather than returning partial or corrupted data.

Support

Found a bug or have a feature request? Open an issue on the Actor's Issues tab in Apify Console. Need a custom version of this scraper — different data fields, another region, or a fully managed pipeline? Reach out through the Actor's contact page for a custom solution.