Ecommerce Product Page Scraper

Extract structured product snapshots from public ecommerce product page URLs. Get titles, prices, availability, identifiers, images and ratings for catalog enrichment, competitor comparisons and metadata audits.

Supply direct product links rather than search pages. Missing or unavailable pages return no product rows and include reasons in a separate run summary. Unresolved extraction and system failures remain visible. Fields vary by store.

Quick start

Start with the small input below, run the Actor and inspect its results.

{
  "urls": [
    "https://books.toscrape.com/catalogue/a-light-in-the-attic_1000/index.html",
    "https://books.toscrape.com/catalogue/tipping-the-velvet_999/index.html"
  ],
  "maxItems": 2,
  "includeRawMetadata": false
}

Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.

What you get

Field	Description
url	Original product URL from your input.
finalUrl	Final URL after redirects.
statusCode	HTTP status code returned by the product page.
title	Product title/name when visible.
price	Price text or structured price value.
currency	Currency from structured product metadata or product meta tags.
availability	Stock/availability text or structured availability value.
sku	SKU when published on the page.
upc	UPC/GTIN identifier when published on the page.
brand	Product brand when available.
description	Product description or page meta description.
ratingValue	Aggregate rating value when available.
reviewCount	Aggregate review/rating count when available.
images	Product image URLs found in structured data, social meta tags, or product image markup.
breadcrumbs	Category/breadcrumb trail when visible.
structuredDataTypes	Structured data types detected on the page.
sourceMethod	Main extraction source: jsonLd, meta, dom, shopifyJson, embeddedData, or error.
renderModeUsed	Successful route: fast HTTP, browser rendering, or same-origin Shopify product JSON.
attemptedRenderModes	Ordered routes attempted for this URL.
warnings	Non-fatal fallback or completeness notes.
error	null on current product rows. Per-URL diagnostics and empty-result reasons are in RUN_SUMMARY, not product rows. Older datasets may contain error records.
fetchedAt	ISO timestamp when the URL was processed.
rawMetadata	Optional parsed metadata snippets when includeRawMetadata is enabled.

Who is it for?

• Catalog teams adding visible product fields to known product URLs.
• Retail researchers comparing displayed product snapshots across supported public stores.
• Data-quality teams investigating missing metadata and outdated catalog links.
• Data engineers joining exported product records to an existing catalog.

How you can use the data

• Inspect a first product snapshot. Use the existing Books to Scrape product URL with a one-page cap. Review the title, price, availability and optional identifiers before processing your own list.
• Compare a small set of known products. Supply direct public product links and a matching page cap. Keep url, finalUrl, price, currency and fetchedAt in your own comparison sheet. The Actor does not calculate cross-run price changes.
• Enrich an existing catalog. Export known product URLs from your catalog, collect their available metadata, then join results by url or finalUrl. Keep missing brand, SKU, rating and image fields unknown rather than assuming universal store coverage.
• Audit old catalog links. Include known old URLs and review RUN_SUMMARY.emptyReasons and RUN_SUMMARY.errors alongside product rows. A missing product row needs its recorded reason, rather than an automatic conclusion that the item was discontinued.

Input settings

Paste a small set of public product links, start the Actor, then export the dataset as JSON, CSV or Excel. Compare snapshots in your own spreadsheet or application. This Actor does not calculate cross-run price changes.

{
  "urls": [
    "https://books.toscrape.com/catalogue/a-light-in-the-attic_1000/index.html",
    "https://books.toscrape.com/catalogue/tipping-the-velvet_999/index.html"
  ],
  "maxItems": 2,
  "includeRawMetadata": false
}

More input configuration

Setting	JSON key	Use it for	Default
Product page URLs	urls	Direct public product detail page URLs to process.	Supply urls or startUrls
Legacy product page URLs	startUrls	Alternative product URL list.	Optional
Maximum product pages	maxItems	Cap processed URLs and control spend.	10
Include raw metadata	includeRawMetadata	Debug custom mappings or inspect structured metadata.	false
Start with browser rendering	renderJavascript	Start in a browser for pages known to require client-side rendering.	false
Automatic browser fallback	autoBrowserFallback	Allow additional supported attempts when the initial page is blocked or incomplete.	true
Request timeout seconds	requestTimeoutSecs	Adjust timeout for slow stores.	30
Proxy configuration	proxyConfiguration	Optional managed or customer-supplied proxies. Leaving it empty uses direct access. No automatic paid proxy fallback.	Empty

Output data

A shortened product record from the public test store. Optional fields vary by store.

{
  "url": "https://books.toscrape.com/catalogue/a-light-in-the-attic_1000/index.html",
  "finalUrl": "https://books.toscrape.com/catalogue/a-light-in-the-attic_1000/index.html",
  "statusCode": 200,
  "title": "A Light in the Attic",
  "price": "£51.77",
  "currency": null,
  "availability": "In stock (22 available)",
  "sku": null,
  "upc": "a897fe39b1053632",
  "brand": null,
  "description": "It's hard to imagine a world without A Light in the Attic...",
  "ratingValue": null,
  "reviewCount": null,
  "images": [],
  "breadcrumbs": ["Home", "Books", "Poetry", "A Light in the Attic"],
  "structuredDataTypes": [],
  "sourceMethod": "dom",
  "renderModeUsed": "http",
  "attemptedRenderModes": ["http"],
  "warnings": [],
  "error": null,
  "fetchedAt": "2026-07-12T15:44:45.332Z"
}

Download your results

Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.

See Apify's download and export guide for the available formats and field options.

Pricing

The start event is charged once after at least one URL passes preflight validation. A batch containing only rejected Meesho, Mercado Livre Brazil, Jiji and/or SHEIN URLs has no start or product charges. An empty run can still incur the start fee when a URL has passed preflight.

The primary item event is charged only after a verifiable product row has been saved. Missing, unavailable, unsafe or unsupported targets are not charged as product results. A buyer charge limit can stop processing before all URLs are attempted, and the summary records this explicitly.

Start with a small run to inspect output completeness for your target stores. See the Actor's live Pricing tab for current rates and Store discounts.

Tips for best results

• Use direct public product-detail URLs. Category, search, cart and checkout URLs are outside this product-page workflow.
• Inspect optional fields before comparing stores. An empty field means the page did not expose that value clearly.
• Choose connection settings only for supported stores. Explicit optional proxy settings can be used where supported, but browser or proxy settings cannot enable Meesho, Mercado Livre Brazil, Jiji or SHEIN. A store can still deny access.
• Keep automatic browser fallback enabled for mixed-store lists. Start with browser rendering only when every URL in the run is known to require it.
• Inspect the extraction source when a field looks incomplete. sourceMethod distinguishes structured metadata, meta tags and page-content extraction.
• Enable raw metadata only when needed for mapping checks. It can make rows larger.

Limits and caveats

Known Noon search-results routes and bare Zara homepage URLs without query parameters are rejected before target requests and the start charge when no valid URLs remain. In mixed batches they produce uncharged summary diagnostics while valid product links continue. Private-network addresses, credentials and non-standard ports are rejected before the run starts. This does not add category or search discovery support.

• Meesho and Mercado Livre Brazil are not supported. URLs on meesho.com, mercadolivre.com.br and their subdomains are rejected before scraping. This does not exclude other Mercado Libre regional domains. Batches containing only excluded URLs fail validation without start or product charges. Mixed batches continue with supported stores and retain clear, uncharged per-URL diagnostics in RUN_SUMMARY. The normal start fee and successful-product charges apply to mixed batches. Platform startup compute may still cost money. Browser or proxy settings do not enable these excluded sites.
• Jiji is not supported. Recognized country hosts (jiji.ng, jiji.co.ke, jiji.ug, jiji.co.ug, jiji.co.tz, jiji.com.gh, jiji.com.et, jiji.sn) and their subdomains are rejected before target requests, browser rendering, or proxy work. Jiji-only batches fail validation without start or product charges. Mixed batches retain other stores and uncharged Jiji summary diagnostics. Normal start and successful-product charges apply. Platform startup compute may still cost money. Browser/proxy settings do not enable Jiji support.
• SHEIN is not supported. Recognized SHEIN storefront hosts (including regional subdomains) are rejected before target requests, browser rendering, or proxy work. SHEIN-only batches fail validation without start or product charges. Mixed batches continue with other stores and save uncharged SHEIN summary diagnostics. The normal run-start fee and successful-product charges still apply. Platform startup compute may still cost money even when all URLs are rejected. Browser/proxy settings do not enable SHEIN support.
• This Actor extracts public page data only. It does not log in, solve CAPTCHAs, add items to cart, or access account-specific prices.
• A store can still deny access with every supported setting. Unavailable pages produce no product rows. Inspect the run summary for reasons.
• Each run processes at most 500 unique URLs, subject to maxItems, a four-minute processing limit and your charge limit. Larger lists may remain unfinished. Inspect RUN_SUMMARY and PENDING_WORK before continuing.
• Walmart product pages can include availability, UPC, brand, ratings, review counts, descriptions, and images when supplied by the store. Unavailable fields remain empty.
• Proxy use is optional and explicit through proxyConfiguration. Browser fallback does not select a proxy for you.
• RUN_SUMMARY contains empty-result reasons and extraction diagnostics. PENDING_WORK identifies unfinished and settled URLs.
• Universal product extraction is best-effort. Store-specific scrapers may be better for high-volume extraction from a single marketplace.

Automation and integrations

Save your settings for next time

Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.

Run on a schedule

Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.

Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.

Send results to your other tools

Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.

For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.

API usage

Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.

The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.

For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.

cURL

curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~ecommerce-product-page-scraper/runs' \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  --data @- <<'JSON'
{
  "urls": [
    "https://books.toscrape.com/catalogue/a-light-in-the-attic_1000/index.html",
    "https://books.toscrape.com/catalogue/tipping-the-velvet_999/index.html"
  ],
  "maxItems": 2,
  "includeRawMetadata": false
}
JSON

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/ecommerce-product-page-scraper').call({
  "urls": [
    "https://books.toscrape.com/catalogue/a-light-in-the-attic_1000/index.html",
    "https://books.toscrape.com/catalogue/tipping-the-velvet_999/index.html"
  ],
  "maxItems": 2,
  "includeRawMetadata": false
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

import os
from apify_client import ApifyClient

client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('fetch_cat/ecommerce-product-page-scraper').call(run_input={'urls': ['https://books.toscrape.com/catalogue/a-light-in-the-attic_1000/index.html', 'https://books.toscrape.com/catalogue/tipping-the-velvet_999/index.html'], 'maxItems': 2, 'includeRawMetadata': False})
print(client.dataset(run['defaultDatasetId']).list_items().items)

MCP and AI agents notes

Use this Actor from MCP-compatible tools through the official Apify MCP Server. The focused URL below selects this Actor. The general server can discover other Actors. Provide a small urls list and maxItems, then retrieve results from the run's defaultDatasetId. Empty optional fields are not evidence that a product lacks that attribute.

MCP and AI agents

You can ask your AI assistant to collect data with Ecommerce Product Page Scraper and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.

Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.

Easier setup with an Apify plugin

If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.

Use Apify AI in Console

Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's Ecommerce Product Page Scraper. You can describe the data you want and ask questions about the results.

Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.

Choose your assistant

• Claude and Claude Code (Anthropic): Apify setup guide.
• ChatGPT and Codex (OpenAI): Apify setup guides.
• Grok Bot (xAI): Apify plugin guide.
• Gemini CLI (Google): MCP server setup guide. Use the server URL below with the HTTP configuration supported by Gemini CLI.

Connect just this scraper

To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=fetch_cat/ecommerce-product-page-scraper"
    }
  }
}

Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.

Use Apify's general server

Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use Ecommerce Product Page Scraper by Fetch Cat, or give it the identifier fetch_cat/ecommerce-product-page-scraper.

Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.

Example requests

• “Use Fetch Cat’s Ecommerce Product Page Scraper to retrieve one product snapshot from https://books.toscrape.com/catalogue/a-light-in-the-attic_1000/index.html. Show the available title, price, stock text and identifiers, marking missing fields.”
• “Collect product snapshots from the 3 direct public product URLs I provide, with a maximum of 3 pages and raw metadata off. Keep original and final URLs so I can join the available fields to my catalog.”
• “Retrieve snapshots for these 2 known old product URLs and explain their recorded empty-result reasons or extraction errors alongside any saved products. Do not treat a missing row as proof of discontinuation or use search or checkout pages.”

Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.

Pay with x402

If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.

Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.

Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.

Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.

Other ways for agents to pay

Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.

FAQ

Can I export results?

Yes. Apify datasets support JSON, CSV, Excel, XML, RSS, and API access.

Why are some fields empty?

Stores expose different metadata. The Actor leaves unavailable fields empty instead of guessing.

Does it work for login-only or cart prices?

No. It only processes public product pages visible without private credentials.

What happens if a URL is invalid, missing or blocked?

Malformed input and an all-rejected URL batch fail before target requests and run-start billing. In mixed batches, rejected URLs do not discard useful product rows. Missing pages, unavailable targets and completed lookups with no usable product data produce no dataset rows and include truthful reasons in RUN_SUMMARY. Access failure alone does not prove a page is private or deleted. Suspected blocking defects retain separate diagnostics. Storage, billing, configuration and systemic extraction failures still fail visibly.

Related Actors

• Shopify Products Scraper — Collect product catalog records from readable public Shopify storefronts, including available titles, vendors, variants and images.
• Amazon Products & Search Scraper — Collect Amazon search results or look up known ASINs and product URLs, with available listing fields for product research.
• Google Shopping Results Scraper — Collect Google Shopping result cards with available prices, merchant details and ratings for retail comparisons.
• Website Content Crawler Lite — Collect text, Markdown, HTML and links from public website pages when you need content beyond product fields.
• Etsy Scraper — Collect public Etsy listings from searches or listing URLs, including titles, displayed prices and available seller details.

Support and feedback

For custom additions or integrations, email hello@fetchcat.dev.

Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.

Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.

Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.

Made with care for curious people, AI agents and the possibilities in data. ♥