Staples Store Locator Scraper

Collect every Staples store page URL from the official Staples.com store locator in one run — no browser, no API key, and no start URLs to configure. This Actor walks the public directory hierarchy (US index → states → cities → stores) with plain HTTP requests and returns a clean, deduplicated list of store links ready to feed a downstream store-detail scraper or a location database.

What is Staples Store Locator Scraper?

Staples Store Locator Scraper is an Apify Actor that extracts Staples store page URLs by crawling stores.staples.com level by level: the national index page, every US state page, every city page, and finally each individual store page. Each result is a unique store link with a discovery label and an extraction timestamp, pushed straight to an Apify dataset. It's built for people who need a bulk list of Staples store URLs — for lead generation, market coverage analysis, or as the input to a Staples store-detail (address/phone/geo/hours) Actor — without writing or maintaining their own crawler.

What can Staples Store Locator Scraper do?

• 🧭 Zero-config crawl — click Run; no start URLs, search terms, or coordinates required.
• 🔗 Full US directory coverage — walks all 50 states + DC via the store-locator index, then every city and store beneath them.
• 🧹 Automatic deduplication — the same store URL is never saved twice, even across cities that link to a shared page.
• ⏱️ Extraction timestamps — every item includes a UTC ISO-8601 timestamp and a mm-dd-yyyy date, so you can track when each link was collected.
• 🔁 Resumable runs — if the run is migrated or restarted by the platform, already-pushed links and fully-crawled states are checkpointed and never re-emitted (and never re-billed under pay-per-result).
• ⏭️ Pay-per-result-safe pagination — startIndex and excludeUrls let you split the directory across multiple runs and skip links you already collected, so you're only charged for new data.
• 🚫 No browser, no API key — pure HTTP requests against public HTML pages, which makes runs fast and lightweight.
• 📤 Flexible export — download results as JSON, CSV, Excel, HTML, or XML directly from the dataset.
• ☁️ Full Apify platform integration — trigger runs via the API, schedule recurring crawls, monitor runs from the Apify Console, and connect to Zapier, Make, or webhooks for downstream automation.

What data does Staples Store Locator Scraper extract?

Each dataset item represents a single Staples store page URL discovered during the crawl:

Field	Type	Description	Example
url	string	Store page URL on stores.staples.com	https://stores.staples.com/al/athens/1036-highway-72-east
coordinate	string	Label for the source the link was found under (currently "static source", since the directory crawl doesn't require coordinates)	static source
extraction_datetime	string	UTC timestamp the link was extracted, ISO 8601	2026-07-21T14:30:00.123456+00:00
extraction_date	string	Extraction date only, mm-dd-yyyy	07-21-2026

How do I use Staples Store Locator Scraper to get Staples store links?

1. Open the Actor and go to the Input tab.
2. (Optional) Set Max store links (maxResults) if you only want a limited number of links — leave it at 0 to collect every store link in the directory.
3. (Optional) If you're paginating across multiple runs or already have some links, set Start index (startIndex) and/or Exclude URLs (excludeUrls) so you don't pay for links you already have — see the Input section below.
4. Click Start.
5. When the run finishes, open the Output tab (or the Dataset tab) to preview, filter, and export the collected store links.

Input

The Actor needs no required input — you can run it with the default settings and it will crawl the entire Staples store-locator directory. Three optional fields let you control how much is collected and avoid duplicate charges under pay-per-result:

• Max store links (maxResults, integer, default 0) — the maximum number of unique store links to collect before the run stops. 0 means unlimited (collect everything found). Free-plan runs are always capped at 10 links regardless of this setting.
• Start index (startIndex, integer, default 0) — skip this many links from the start of the directory walk (positionally) before saving any. Useful for paginating a large crawl across multiple runs — e.g. set it to 500 once you already have the first 500 links. Ignored (forced to 0) on the free plan.
• Exclude URLs (already collected) (excludeUrls, array of strings, default []) — a list of store URLs you already have; these are never saved again no matter where they fall in the crawl order. Capped to 1 URL on the free plan.

Example input:

{
    "maxResults": 0,
    "startIndex": 0,
    "excludeUrls": []
}

Output example

{
    "url": "https://stores.staples.com/al/athens/1036-highway-72-east",
    "coordinate": "static source",
    "extraction_datetime": "2026-07-21T14:30:00.123456+00:00",
    "extraction_date": "07-21-2026"
}

You can download the dataset in JSON, CSV, Excel, HTML, or XML format from the Apify Console, or fetch it programmatically via the Apify API or SDK.

Use cases

• Feed a store-detail scraper — pass the collected URLs into the companion Staples Store Details Scraper to enrich each link with address, phone number, geolocation, and hours.
• Build a location coverage map — get a full list of every physical Staples location in the US to analyze market density or plan territory coverage.
• Lead generation for B2B outreach — use store URLs and locations as a starting point for local-business outreach lists.
• Monitor directory changes over time — schedule recurring runs and diff the dataset to catch new store openings or removed locations.
• Populate a store-locator widget or internal dataset — keep an internal database of Staples store pages in sync without manually browsing the site.

Staples-related Actors

Actor	What it does
Staples Store Details Scraper	Takes store links (like the ones from this Actor) and extracts full store details — address, phone, geolocation, hours.

FAQ

Is it legal to scrape Staples store locator data?

This Actor only collects publicly available URLs from the same public directory pages stores.staples.com serves to any visitor's browser — no login, no private data, and no personal information. That said, scraping legality can depend on your jurisdiction and intended use, and you're responsible for complying with Staples' Terms of Service. Consult a legal professional if you're unsure about your specific use case.

Does this Actor need an API key or proxy configuration?

No. It crawls stores.staples.com with plain HTTP requests — no browser, no API key, and no proxy configuration required to run it.

Can I access the results via the Apify API?

Yes. Every dataset produced by this Actor is available through the Apify API, so you can fetch results, trigger runs, and integrate the Actor into your own pipelines, Zapier/Make scenarios, or scheduled jobs directly from the Apify Console.

What happens if a directory page is blocked?

If a request to a directory page (index, state, or city) is blocked by anti-bot protection, the crawl for that specific source stops and the event is logged — it does not fail the whole run, so links already collected are preserved.

How do I avoid getting duplicate links across multiple runs?

Use Start index (startIndex) to skip a fixed number of links positionally, and/or Exclude URLs (excludeUrls) to skip specific URLs you already have — both are pay-per-result-safe. The Actor also checkpoints its own progress internally, so a run that's migrated or resumed by the platform never re-pushes (or re-charges for) a link it already emitted.

Support

Found a bug or have a feature request? Open an issue on the Actor's Issues tab in Apify Console. For a tailored crawl (custom fields, different regions, or a fully custom scraper), reach out via the Actor's contact options for a custom solution.