Paste one complete object
Include the object or @graph that the rendered page actually publishes.
Paste the Product JSON-LD from your rendered page. See missing fields, then use Google's official validator for the authoritative result.
We show the result before we ask you to install anything.
Searchers often arrive with a markup error, but the practical question is whether the Product data is complete, current, and aligned with the visible offer. This pre-check prepares a cleaner official test.
Include the object or @graph that the rendered page actually publishes.
Price, currency, availability, and URL should match what the shopper can see.
Look for multiple Product entities or app-generated values that disagree.
Treat this tool as preparation, then confirm with Google's current Rich Results Test.
A Product object includes name and image but omits priceCurrency and availability.
Rendered Product JSON-LD.
A pre-check that identifies the missing Offer fields before official validation.
The official validator remains the authority for rich-result eligibility.
Use this when a merchant is about to validate product markup and wants to remove avoidable errors first.
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. This is a fast Pulse pre-check. Use Google's official Rich Results Test for the final eligibility and error report.
No. Structured data can create eligibility, but search engines decide what to show.