DHGate Products Scraper

This Actor extracts source-backed product data from public DHgate product and category pages. It can emit product identity, structured offer prices and tiers, MOQ, specifications, images, shipping summaries, seller-store references, and aggregate review fields when DHgate exposes them publicly.

The Actor uses direct public HTTPS requests to DHgate only. It does not log in, use private APIs, rotate proxies, solve CAPTCHAs, or bypass access controls. Robots.txt is checked before a live page request, redirects stay within the DHgate boundary, and challenge or blocked responses are emitted as diagnostics rather than being treated as products.

Input

Provide one or more public DHgate product or category URLs in startUrls. When the field is omitted, the default public DHgate homepage is checked. Invalid explicit URLs are reported and never replaced with a default URL. maxItems bounds product records, timeoutSecs bounds each request, maxRetries bounds retryable failures, requestDelayMs spaces retries, and maxBytes limits one response.

For deterministic local validation, set sourceMode to fixture and provide fixtureHtml or a local fixtureFile inside the Actor directory. Fixture mode never falls back to the network.

Example:

{
  "startUrls": ["https://www.dhgate.com/product/example-wireless-earbuds/123456789.html"],
  "maxItems": 10,
  "timeoutSecs": 30,
  "maxRetries": 2
}

Output

Normal records contain only documented public source and business fields: source URLs, product identity, pricing, public supplier/store signals, images, specifications, reviews, and scrapedAt. They intentionally omit transport, request, extraction, quality, and other operational instrumentation. Diagnostics are separate minimal rows with exactly recordType: "diagnostic", url, errorCode, error, and scrapedAt.

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

The default key-value store contains OUTPUT, OUTPUT_SUMMARY, RUN_SUMMARY, and SUMMARY aliases plus SOURCE_METADATA and DIAGNOSTICS.

Limits and responsible use

Only public product and aggregate seller signals are emitted. Contact details, account data, credentials, cookies, private supplier fields, and challenge state are excluded. DHgate may return Cloudflare or other access-control pages depending on region and request conditions; the truthful local result in that case is a blocked diagnostic and not a publishable product dataset.

For local development, run npm run check and validate an isolated Actor run with npm run validate plus ACTOR_DATASET_DIR pointing to that run's dataset directory. Cloud builds, remote runs, deployment, and publication are separate release gates.