Paste the rendered block
Use the JSON-LD from the page source, not a remembered template.
Paste the structured data you can see in the rendered page. This checker catches common missing fields and tells you what to inspect next.
We show the result before we ask you to install anything.
Structured data is useful only when it describes the page a shopper sees. This checker makes the Product entity, Offer fields, and visible-content relationship explicit.
Use the JSON-LD from the page source, not a remembered template.
Check that name, image, offer, price, currency, and availability belong to the product on this URL.
A valid value that is stale or hidden is still a review problem.
Use Google's current validator after this quick structural pass.
A Product block has price and currency but no availability, while a second app block has a different price.
The rendered JSON-LD object or @graph.
A focused list of missing fields and a duplicate-entity warning path.
This is not Google's Rich Results Test and does not decide eligibility.
Use this when the question is whether the markup is structurally worth taking to an official validator.
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 rendered JSON-LD yourself. This keeps the tool fast and avoids asking for store access or crawling a URL.
No. Valid structured data can create eligibility, but search engines decide whether to display a rich result. It also does not guarantee AI visibility.