Tool
What the Product Schema Generator does
Product Schema Generator: generates JSON-LD only from Product name, Image URL and Description. Example: product name Blue Widget, image URL https://example.com/widget.jpg and price 29.99 gives JSON-LD only { "@context": "https://schema.org", "@type": "Product", "name": "Blue Widget", "image": [ "https….
This generator reads Product name, Image URL, Description and Price and produces JSON-LD only. Values update as you type, so comparing options is a matter of editing one field.
Typical users are anyone tuning a snippet. What Google displays is rarely exactly what you wrote, and the difference costs clicks.
There is no back end here. The calculation runs where you are sitting, not on a server somewhere.
Each field is explained further down, along with the method and a worked example that uses the default values.
What do the Product Schema Generator fields mean?
The Product Schema Generator uses 8 inputs. Sensible defaults are loaded up front, which means you can change one number at a time instead of filling the whole form first.
| Field | What to enter | Default |
|---|---|---|
| Product name | required | Blue Widget |
| Image URL | required | https://example.com/widget.jpg |
| Description | paste or type any amount of text | A hard-wearing blue widget with a five-year guarantee. |
| Price | required | 29.99 |
| Currency code | required | GBP |
| Availability | choose from In stock, Out of stock or Pre-order | In stock |
| Brand | optional | Example |
| SKU | optional | none |
How does the Product Schema Generator work?
Each output is derived from the inputs above in a single pass; there is no hidden state carried between runs, so the same inputs always give the same generated output.
Bad input produces a message, not a silently incorrect figure.
Worked example
These are the values the Product Schema Generator loads by default, and the result it produces from them. These are the exact values loaded when the page opens, and the answer they produce.
| Product name | Blue Widget |
|---|---|
| Image URL | https://example.com/widget.jpg |
| Description | A hard-wearing blue widget with a five-year guarantee. |
| Price | 29.99 |
| Currency code | GBP |
| Availability | In stock |
| Brand | Example |
| SKU | (empty) |
| JSON-LD only | { "@context": "https://schema.org", "@type": "Product", "name": "Blue Widget", "image": [ "https… |
|---|
Price, availability, and at least one signal of trust
Google requires a Product’s offers to include price and priceCurrency, and effectively requires either an offer, a review, or an aggregateRating for the type to be eligible for rich results at all: a Product with none of the three has nothing beyond a bare name and image for Google to show.
Worth knowing
- A common validation mistake is providing a price without a matching priceCurrency, or vice versa. Google requires them as a pair, since "29.99" alone is not a price without a currency attached.
- Google has pushed harder in recent policy updates on merchant-specific requirements (GTIN, MPN, or brand, alongside the core Product fields) for listings meant to be Shopping-eligible, beyond the baseline Product rich-result requirements. Check current Merchant Center requirements separately if that is the goal.
- A self-authored aggregateRating, or one padded with fabricated reviews, violates Google’s structured-data content policies even where every required field validates. The schema check and the content-integrity check are different bars, and only the first is something a syntax validator can see.
How to use it
- Set Product name.
- Put Image URL.
- Paste your content into Description.
- Fill in Price.
- Type Currency code.
- Pick a value for Availability: the options are In stock, Out of stock or Pre-order.
- Set Brand.
- Put SKU.
- Results update continuously rather than on submit.
- Check JSON-LD only on the right.
- Print gives a tidy version without the navigation, which is handy for attaching to a file.
What this tool does not do
- This inspects the markup you supply; it cannot see server headers or your live rankings.
- Search engines weigh hundreds of signals. No single on-page check predicts position.
- Edge cases at the very limits of the accepted range are handled, but rarely worth relying on.
Frequently asked questions
The form asks for Product name, Image URL, Description, Price, Currency code, Availability, Brand and SKU. Nothing starts empty, so the quickest approach is to replace the one number you actually care about.
With the values loaded when the page opens, JSON-LD only comes out as { "@context": "https://schema.org", "@type": "Product", "name": "Blue Widget", "image": [ "https…. Overwrite any of the starting values and the result follows.
No. Disconnect from the internet and it still works; that is the simplest proof there is no server call.
No payment and no login. Advertising covers the running costs.
As accurate as the inputs allow. The arithmetic itself introduces no error beyond display rounding.