Schema / JSON-LD Generator

A product page sells the Acme Travel Mug for 24.99 USD, rated 4.6 from 213 reviews. Choose Product and fill in name, description, image, brand, price, currency, rating and review count. The brand becomes a nested Brand, price and currency become an Offer, and the rating and count become an AggregateRating:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Acme Travel Mug",
  "description": "16 oz stainless steel travel mug with a leak-proof lid.",
  "image": "https://example.com/mug.jpg",
  "brand": {
    "@type": "Brand",
    "name": "Acme"
  },
  "offers": {
    "@type": "Offer",
    "price": "24.99",
    "priceCurrency": "USD"
  },
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "4.6",
    "reviewCount": "213"
  }
}
</script>

The checklist shows 6 properties, the required name and offers present, all three recommended properties (image, description, brand) present, 0 missing and 0 warnings.

The common mistake: typing the price the way the page shows it, "price": "$24.99". The dollar sign makes the price unreadable, so the offer is ignored even though the JSON itself is valid. The currency belongs in priceCurrency and the price must be the plain number 24.99. Try the “Mistake: $ in price” preset: the output is still produced, but the checklist raises a warning on the price and lists image, description and brand as missing recommended properties.

Google announced rich snippets in May 2009, reading star ratings and prices from microformats and RDFa written into a page’s HTML. Each search engine had its own preferred markup until June 2011, when Google, Microsoft’s Bing and Yahoo launched Schema.org as one shared vocabulary; Yandex joined that November. The vocabulary now defines hundreds of types, from Product and Event to MedicalCondition.

Schema.org launched with Microdata, and RDFa Lite followed: both are attributes woven through the visible HTML, so any redesign could break them. JSON-LD (JSON for Linked Data) became a W3C Recommendation in January 2014, and version 1.1 followed in July 2020. It keeps the data in one separate script block, which is why Google now recommends it. In August 2023 Google limited FAQ rich results to well-known government and health sites and dropped HowTo rich results soon after, a reminder that eligibility rules change while the markup itself stays valid.

This generator writes Schema.org JSON-LD for the seven types most sites need: Organization, LocalBusiness, Article, Product, Person, FAQPage and WebSite. Empty fields are left out, nested objects are built for you, and the result is a complete script block ready to paste.

Unlike a plain form, it checks what it writes. The checklist compares the block with the properties Google documents as required and recommended for that type, and flags values that would make it unreadable: a currency symbol in the price, a relative URL, a date that is not ISO 8601, a rating off the 1–5 scale or opening hours in the wrong pattern. Show Work lists every property, where it was placed and why. Everything runs in your browser; nothing you type is uploaded.

It is meant for site owners, developers and SEO work where the markup has to be right first time. Check the live page with Google’s Rich Results Test afterwards.

Related tools: Meta Tag Generator, robots.txt Generator, and JSON Validator.