Match the right product.
Exact SKU or normalized GTIN matching. Ambiguous variants and offers stay unresolved.
FOR ECOMMERCE TEAMS & FEED AGENCIES
Find price and stock differences before your next catalog update. Match by SKU or GTIN, compare published structured data, and get a report you can act on.
$0.004 per parsed product page · no separate AI API key
Exact SKU or normalized GTIN matching. Ambiguous variants and offers stay unresolved.
Missing data gets its own verdict. A blocked page never becomes a false match.
Expected and observed values, a timestamp and a source pointer, together in a flat CSV.
TRY THE COMPARISON
This demo uses illustrative data in your browser. It does not check a website or send your inputs to us.
Your result will appear here.
The same comparison code powers this demo and the Apify audit. Live extraction depends on what each page publishes.
FROM EXAMPLE TO YOUR CATALOG
Use a product URL, SKU or GTIN, and your current price or availability. The sample input uses a public demo store.
Up to 100 catalog rows across 30 unique pages per run. Several rows sharing a page incur one page event charge.
Download AUDIT.csv from the run's Output tab. Save an Apify Task and Schedule to repeat. Update the saved input when your catalog changes.
A PRICE YOU CAN CALCULATE
1,000 successful page parses = $4 in Actor event charges. A 30-page audit = $0.12 in event charges. Apify platform charges may apply; check your plan's price in Console.
A page with at least one extracted Product record. An unresolved audit can still be charged when Product data was extracted. Empty, blocked and failed fetches carry no Actor event charge.
BEFORE YOU USE IT
No. It compares your supplied catalog values with server-delivered Product JSON-LD. It does not inspect the rendered page, checkout, Google account, shipping or taxes. Google describes the underlying price mismatch problem here. We are independent of Google.
The page must publish Product JSON-LD in its initial HTML. Try one page first. SKU matching is case-sensitive; GTINs use normalized leading-zero padding. Multiple matching products, multiple offers and price ranges are unresolved. JavaScript-only data, login and anti-bot bypass are not supported.
Yes. Pass a urls array to get normalized names, brands, SKU/GTIN and offers. Existing extraction inputs continue to work. Add catalog to compare expected values.
All the fields you requested match the selected offer in the page's JSON-LD. Structured data can itself be stale. MISMATCH means at least one confirmed difference; check field statuses for anything still unknown. A match is not a store-wide health certificate.
Use the Actor's Issues tab with a public URL and redacted input and output. Never post API keys or private catalog data. There is no promised response-time SLA.
ALSO IN THE TOOLKIT
HTTP status, redirects and failure categories for public URLs. Check whether a URL responds before an automation relies on it.
Public RSS, Atom and JSON Feed metadata with date filters and ID deduplication. Full article bodies stay out of the result.