Product Schema Generator (JSON-LD)

No. Structured data is not a direct ranking signal. What Product schema does is unlock SERP features - star snippets, price tags, free merchant listings - that substantially raise click-through rate. Higher CTR on the same position is the indirect benefit. If your product page is currently at position 6 without schema and gets 2% CTR, adding valid Product + Offer + AggregateRating can push it to 3-4% CTR at the same position, which often correlates with a position improvement over weeks.

Price must be a decimal number encoded as a string or number, without currency symbols or thousands separators. <code>"19.99"</code> is valid, <code>"$19.99"</code> is not, <code>19,99</code> is not. priceCurrency must be an ISO 4217 code in quotes: <code>"USD"</code>, <code>"EUR"</code>, <code>"GBP"</code>. priceValidUntil is optional but recommended for sale prices - Google omits the price tag in snippets after that date.

Yes, if your page lists multiple merchants, sizes, or colours of the same product with different prices. AggregateOffer needs <code>lowPrice</code>, <code>highPrice</code>, <code>priceCurrency</code>, and <code>offerCount</code>. Google will show a "from $19" style range snippet. For a single SKU at a single price, Offer is simpler and more common. The generator produces Offer; add an AggregateOffer manually if needed.

Emit valid Product + Offer on the page AND connect a Merchant Center account AND opt into the "surfaces across Google" program. On-page structured data alone is not sufficient for free merchant listings - the listings come from your Merchant Center feed and the schema just corroborates it. For independent e-commerce without Merchant Center, you still get product snippets (stars, price), just not the standalone shopping listings.

Both patterns are valid. The review-count snippet comes from <code>aggregateRating</code> nested inside Product; individual Review objects can also be nested (<code>"review": [...]</code>) for richer attribution. If your CMS stores reviews on a separate page, point to them via <code>@id</code>. Do not fabricate reviews to trigger stars - Google's review policies require reviews to be from real customers, accessible on the page, and not incentivised by the seller.

Use <code>ProductGroup</code> with an array of <code>hasVariant</code> child Products, each with its own <code>offers</code>, <code>color</code>, <code>size</code>, and <code>sku</code>. This is newer schema (added in 2022) and fully supported by Google for apparel. The generator produces a flat Product by default; for ProductGroup structure, hand-edit the output. For pages with a size selector and per-size price, variants are the right modelling choice.

Most often: (1) Google is still re-crawling the page - give it 24-72 hours after deployment; (2) the AggregateRating fields are technically valid but below Google's threshold (needs at least one review visible on the page); (3) the Product itself is not eligible (digital gift cards, services, accommodations, and software applications have different rules); (4) a manual action has been triggered by prior policy violations. Start with Search Console's URL Inspection to confirm Google parsed the structured data correctly.

No. The generator builds the JSON-LD block entirely in your browser with pure JavaScript. Your product name, price, description, and review data live only in the browser tab and are discarded when you close it. There is no telemetry, no analytics beacon per input keystroke, and no remote API. You can verify this in the Network tab of DevTools - zero outbound requests during generation.