Identify the entity
Confirm that the object includes the type the page is meant to describe.
Paste one JSON-LD object or an @graph. This tool checks structure and highlights where markup must match the visible product page.
We show the result before we ask you to install anything.
Structured data errors are easier to fix when the test tells you which entity and field failed. This tool keeps the check centered on common Product and Offer data.
Confirm that the object includes the type the page is meant to describe.
Product name, image, Offer, price, currency, and availability are a useful first pass.
Make sure the data belongs to the current URL and visible offer.
Re-run after a theme or app change because markup can be emitted in more than one place.
An @graph contains Organization and Product data, but the Product has no Offer object.
One JSON-LD object or @graph.
Entity-level checks that show which Product fields need review.
This focused tool does not implement every Schema.org type.
Use this when you need a readable structured-data triage before a full implementation review.
See whether the inputs give a useful starting point.
Know which evidence is present and which needs work.
Leave with a practical edit or measurement plan.
Pulse's free tools are deliberately narrow. They do not pretend to replace a live crawl, a provider's answer, or an experienced Shopify operator.
They help you identify the next question worth asking. If you want the recurring workflow—tracked questions, store context, reviewable fixes, and measurement—that is where Pulse fits.
No. Paste the JSON-LD from the rendered page. The result is intentionally limited to the data you provide.
Structured data should describe the page shoppers see. A technically valid block can still be misleading if its facts disagree with the page.