Use visible facts
Enter the name, brand, offer, URL, and image the page really shows.
Enter the visible product facts and get a draft you can inspect. Keep the values aligned with the page before publishing any markup.
We show the result before we ask you to install anything.
JSON-LD is easy to generate and easy to make stale. This draft starts from visible facts, then reminds the operator to check existing theme and app output before adding anything.
Enter the name, brand, offer, URL, and image the page really shows.
Inspect existing JSON-LD before creating a second Product entity.
Price, currency, availability, and URL must follow the live offer.
Test after publishing and after theme or app changes.
A product page needs a draft, but the merchant has not checked whether the theme already emits Product data.
Visible Product and Offer facts.
Editable Product JSON-LD with a validation checklist.
The draft is not guaranteed to be complete for every use case.
Use this when you need a transparent Product JSON-LD starting point before 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.
Not safely without checking how your theme or apps already emit Product markup. Duplicate or conflicting entities can make debugging harder.
It is a draft based on your inputs. Validate it and make sure every value is visible and truthful.