Product Image Gallery Extractor avatar

Product Image Gallery Extractor

Pricing

$3.00 / 1,000 results

Go to Apify Store
Product Image Gallery Extractor

Product Image Gallery Extractor

Pricing

$3.00 / 1,000 results

Rating

0.0

(0)

Developer

Eichan Jolly

Eichan Jolly

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

4 days ago

Last modified

Categories

Features

Limited permissions

Share

Extract the product image links that one public product page actually declares in its schema.org Product JSON-LD and og:image meta tags. No browser, proxy, login, guessing filenames, or image downloads.

Who is this for?

Merchants auditing product image metadata, catalogue QA analysts, and developers preparing image lists for a product import. One product page per run; it is not a full-site scraper.

Quick start / real prefilled demonstration

The Apify input form is prefilled with a publicly reachable Cancork product page whose og:image URL was independently observed on 2026-11-01. The page may change after that date.

{
"productUrl": "https://www.cancork.com/store/wood-bricks-9mm-cork-wall-panels/"
}

Expected at least one result from its currently published og:image tag, provided the website still exposes it:

{
"productUrl": "https://www.cancork.com/store/wood-bricks-9mm-cork-wall-panels/",
"imageUrl": "https://www.cancork.com/product-images/wood-bricks-9mm-cork-wall-panels-wall-interior-ge.webp",
"source": "og_image",
"position": 1,
"status": "ok",
"error": null
}

A different page with explicit JSON-LD product images emits source: "jsonld". One clean dataset item is emitted for each unique URL. Results use 1-based position, with JSON-LD images before Open Graph images. If the same URL appears in both, only the first JSON-LD occurrence is retained.

Output fields

  • productUrl (string): exact validated page URL provided, normalized with a / if path omitted.
  • imageUrl (string or null): image URL explicitly referenced on the page.
  • source (jsonld, og_image, or null): where that particular URL was found.
  • position (positive integer or null): order within this run's deduplicated results.
  • status (ok, not_found, or error).
  • error (string or null): plain-language reason if no data is available.

If neither source declares an image, the Actor emits one honest not-found item rather than inventing an image:

{
"productUrl": "https://example.org/public-product",
"imageUrl": null,
"source": null,
"position": null,
"status": "not_found",
"error": "No product JSON-LD images or og:image tags were found."
}

The URL above is an illustrative output shape only, not the prefilled demo URL.

Data sources and limits

  • Fetches only the one product URL supplied, no sitemap crawling and no additional image requests.
  • Parses application/ld+json blocks and image strings, arrays, or ImageObject url/contentUrl values within objects of type Product, including @graph entries. Non-Product structured data images are ignored.
  • Parses standard <meta property="og:image" content="..."> tags even when JSON-LD is absent.
  • URL references declared as relative paths are resolved against the supplied page URL. This is normal URL resolution of an explicit reference, not an image-name guess.
  • Only http(s) image references are emitted. Does not validate whether the images remain reachable or whether they are licensed for reuse.
  • HTML-only extraction; dynamic JavaScript-generated JSON-LD and image tags may not be present in fetched HTML.
  • 15-second network timeout, 2 MB HTML response size limit, same-host redirects only, public network addresses only. No retry storm.
  • Do not enter login-only, anti-bot-restricted, or disallowed-to-scrape pages. A 403/404 or timeout results in a readable error dataset item.

Run locally (Python 3.12+; zero dependencies)

From this Actor folder:

$ACTOR_INPUT_JSON='{"productUrl":"https://www.cancork.com/store/wood-bricks-9mm-cork-wall-panels/"}' python src/main.py

The generated local dataset goes into storage/datasets/default/000000001.json (and subsequent numbered JSON files). You may also create storage/key_value_stores/default/INPUT.json. On Apify, the Actor reads INPUT from the run's key-value store by REST and appends records to the default dataset by REST. The platform provides the storage IDs and APIFY_TOKEN. No SDK is used.

Reproduce verification

python -m unittest discover -s tests -p 'test_*.py' -v
python tests/run_smoke.py

tests/run_smoke.py launches python src/main.py as a separate process in a temporary stdlib-only virtual environment and captures the real exit code, stdout, stderr, and saved dataset. The supplied test-only HTTP fixture is substituted using a Python startup hook; the production src/main.py is not changed. Thus this is a script-mode test with simulated HTTP, not a claim of a live Apify run or live website fetch from Python. See tests/smoke_evidence.txt and tests/smoke_dataset.json.

Suggested Apify Store details (not activated)

  • Category: ECOMMERCE (E-commerce).
  • Suggested price: USD $3 per 1,000 successful image results ($0.003/result). Do not charge for error/not-found rows when implementing billing.
  • store_metadata.json contains a proposal, not billing configuration.

Not published; no billing setup or Apify platform run has been performed.