Product Price and Offer Monitor for Public Product Pages

What this Actor does

Track public product pages and extract price, availability, discount, seller, and product metadata.

It processes user-provided public URLs, prioritizes JSON-LD/schema.org structured data, normalizes the useful fields, deduplicates rows, and saves structured records to the Apify dataset.

Why this Actor is useful

Teams pay for this kind of extraction when it saves manual research, creates repeatable monitoring, feeds spreadsheets or CRMs, and turns public pages into clean API-ready datasets.

Who this is for

• Ecommerce sellers
• D2C brands
• Price monitoring agencies
• Marketplace consultants
• Dropshipping researchers
• Retail analysts

Common use cases

• Monitor competitor product pages
• Track public price and availability changes
• Build product intelligence dashboards
• Export product metadata to spreadsheets
• Feed repricing or research workflows after source review

Input

• startUrls: Public URLs to extract from. Use only pages you are allowed to access without login or bypassing access controls.
• maxItems: Maximum number of rows to save.
• maxConcurrency: Number of pages processed in parallel. The default is intentionally conservative.
• includeRawStructuredData: Adds the original JSON-LD object for audit/debugging.
• proxyConfiguration: Optional Apify proxy configuration where permitted by your source review.

Output

• productName: Product name from public structured data.
• productUrl: Canonical product URL or source URL.
• currentPrice: Current public price when available.
• originalPrice: Original or comparison price when available.
• discount: Discount signal if present in structured data.
• currency: Currency code when available.
• availability: Public availability or stock status.
• seller: Seller name when listed publicly.
• rating: Aggregate rating when available.
• reviewCount: Public review count when available.
• imageUrl: Public product image URL.
• checkedAt: Timestamp when the product page was checked.
• sourceUrl: URL where the data was extracted.
• confidenceScore: Heuristic confidence score based on structured data availability.

Sample input

{
  "startUrls": [
    {
      "url": "https://example.com/"
    }
  ],
  "maxItems": 25,
  "maxConcurrency": 3,
  "includeRawStructuredData": false
}

Sample output

{
  "productName": "Example Noise Cancelling Headphones",
  "productUrl": "https://example.com/products/noise-cancelling-headphones",
  "currentPrice": "149.99",
  "originalPrice": "199.99",
  "discount": "25%",
  "currency": "USD",
  "availability": "https://schema.org/InStock",
  "seller": "Example Audio Store",
  "rating": "4.6",
  "reviewCount": 1284,
  "imageUrl": "https://example.com/images/headphones.jpg",
  "checkedAt": "2026-06-12T00:00:00.000Z",
  "sourceUrl": "https://example.com/",
  "confidenceScore": 0.9
}

How to use

Run this Actor on Apify with public URLs, export the dataset as JSON, CSV, Excel, or through the Apify API, then connect the output to Google Sheets, Make, Zapier, a webhook, your CRM, or an internal dashboard. For monitoring, save the input as an Apify task and schedule recurring runs.

Best practices

• Start with a small set of reviewed public URLs.
• Prefer pages with schema.org JSON-LD structured data.
• Keep maxConcurrency low for smaller websites.
• Review source website rules before scheduling recurring runs.
• Keep includeRawStructuredData off unless you need audit details.

Compliance and responsible use

This Actor is for public data only. It must not be used to bypass logins, paywalls, CAPTCHAs, or security systems, collect private data, gather sensitive personal data, or support spam or abuse. You are responsible for following applicable laws and source website rules.

Limitations

• Output quality depends on public structured data available on the source pages.
• Some fields may be empty when the source does not publish them.
• The Actor does not claim support for any specific third-party platform.
• Website markup and access policies can change.

Troubleshooting

• Empty output usually means the page has little or no JSON-LD/schema.org data.
• Invalid URL errors mean one or more input URLs are malformed.
• Slow runs can usually be improved by lowering maxConcurrency.
• Missing fields are source-data limitations, not inferred values.

Changelog

• v0.2.0: Production-readiness pass with improved positioning, samples, schema descriptions, and responsible-use notes.
• v0.1.0: Initial dry-run factory generated MVP.