Price monitoring starts with verifying the source.

1. Inspect structured product data

A publicly reachable e-commerce page may contain schema.org/Product with offers.price, offers.priceCurrency and offers.availability. Not every storefront provides these fields, and a price without a currency is unsafe for cross-site comparisons.

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Example Item",
  "offers": {
    "@type": "Offer",
    "price": "25.00",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock"
  }
}

This is a constructed format example, not real retailer evidence.

2. Distinguish price, stock and page content

Publisher-declared price events need two valid observations with comparable currency. Availability changes are separate. A changed SHA-256 digest proves that fetched content changed, not that price or inventory changed.

JavaScript-only pages, anti-bot responses, login-protected catalogs and missing or inconsistent data may not permit trustworthy price tracking. No value should be invented to fill the gaps.

3. Use a real source check before buying

The free compatibility audit reads a buyer-chosen public URL and reports which publisher fields are present. A snapshot is not real-time tracking, cannot promise uptime and may miss short-lived changes.

Only consider scheduled checks once that particular source has suitable metadata: 10 URLs/12 hours on Starter, 25 URLs/6 hours on Pro.

4. Evidence, privacy and sharing

Keep the source URL, UTC observation time and SHA-256 with the report. No private browsing or merchant credential data is needed. Share reports voluntarily, respect community rules, and do not publish another seller’s details without an appropriate reason or permission.

Compare the actual monitoring limitations and plans.