WooCommerce Products Scraper — Catalog and Price Evidence
Pricing
from $0.50 / 1,000 delivered products
Scrape public WooCommerce product catalogs with exact minor-unit prices, coverage evidence, additional existing Dataset append and sequential multi-store collection. Use a finite run charge limit; support for uncapped runs is being repaired.
Public store root domains/homepages only, including bare domains, scheme, www and trailing slash. No product/category URLs. No runtime default: supply a nonempty list.
Limit acknowledged unique products separately for each store. Zero sets no product/page count limit. Prefill 5 is a bounded sample, not the runtime default.
Direct by default. Explicit Apify pool or HTTP(S) custom proxies are supported and never fall back to direct. Hosted Apify proxy needs injected credentials. Custom proxies and all target DNS stay strictly public.
{ "useApifyProxy": false}Optional existing caller-owned Apify Dataset ID. Default Dataset is retained; append a copy after the default row and its one custom fee are confirmed. No create, foreign write or permission change. Any unconfirmed append stops without replay.
Optional previous run identifier recorded as associatedRunId in rows and reports for chaining. Does not fetch or inherit that run input or Dataset.
Extra control: pass an explicit search term to the public Store API. Empty means no search filter. The bounded example uses WordPress.
Extra control; primary mode requests 100 products/page. The saved real replay/example uses 5.
Minimum interval between source attempts on an origin, increased by robots Crawl-delay. No source retries.
Includes robots, DNS and redirects for a single fetch. Storage/fee operations have separate 15-second acknowledgement deadlines.
Source work time limit; exhaustion reports partial and retains confirmed products. Platform hard kill can interrupt final reports or leave unknown writes.
Includes robots, redirects, diagnostics and fake-IP-only DoH. Count zero imposes no transport count cap.
Streaming bound on both compressed and decoded response. Oversize stops the affected store without truncation-success. Use maxRecordBytes to separately bound product/report plain JSON delivery bytes.
Optional storage control, measured on plain UTF-8 JSON before a write or product fee. Default 8 MiB preserves the original limit. Oversize products are skipped and coverage is partial; no field is truncated. Oversize evidence or reports fail the run.