Mumzworld Baby & Family Product Scraper

Production-oriented Apify Actor for extracting public Mumzworld baby, kids, motherhood, toy and family catalog pages. It uses the rendered storefront only: there is no login, private API, CAPTCHA bypass, or access-control bypass.

What it collects

One product record can include title, product ID, SKU, brand, category, age range, current/list/sale price, currency, availability and stock state, rating, review count, description, visible attributes, public image URLs and optionally up to 10 visible review snippets. Listing pages are paginated within the configured bound and product URLs are deduplicated.

Input

{
  "startUrls": [{ "url": "https://www.mumzworld.com/en-ae/baby" }],
  "searchQueries": ["baby bottles"],
  "maxProducts": 50,
  "maxPages": 3,
  "includeReviews": false,
  "minDelayMs": 1200
}

startUrls accepts public Mumzworld listing/category/search/product URLs. If omitted, the baby catalog is used. searchQueries creates public-site search URLs. maxProducts (1–500), maxPages (1–20), concurrency (1–3), retries (0–3), and request delay (250–10,000 ms) are bounded to control traffic and cost. Proxy configuration is optional and must be authorized for the traffic.

Output and failure semantics

The dataset contains recordType: "product" records plus one recordType: "runSummary" record. Product status is:

• ok: core product fields were publicly available.
• partial: the page rendered but fields such as title, price or ID were missing; warnings explains the gap.
• blocked: a public challenge/access-denied page was returned.
• error: the request failed after bounded retries.

An empty listing, blocked page, or source markup change is represented explicitly. A run with no usable product or partial records exits unsuccessfully so monitoring does not mistake an empty crawl for success. Inspect RUN-SUMMARY, dataset records, logs, and the exit status together.

Limits, cost and safe use

Runtime and cost are driven mainly by product-page count, browser startup, pagination and proxy usage. A practical run of 50 products across three pages usually makes roughly 51–60 navigations; a one-product smoke run is much cheaper. Apify compute, proxy traffic and storage are billed according to your Apify plan; this Actor does not add a separate fee.

Use conservative limits and schedules, respect Mumzworld terms, robots guidance, rate limits and applicable law, and collect only information exposed to an unauthenticated visitor. Do not use the Actor to bypass challenges, authentication, geographic controls or other access restrictions. Store outputs securely and honor deletion/opt-out requests where applicable.

Local quality gate

npm ci
npm test
npm run build

Tests cover defaults, invalid input, empty listings, pagination URL handling, partial extraction, retry/failure-shaped records and blocked/source-change fixtures without making network requests.