Schema.org JSON-LD Generator

Generate schema.org JSON-LD structured data for Article, Organization, Person, Product, FAQPage, Event, LocalBusiness and WebSite from a simple form.

Absolute URL of an image that represents the item.

ISO 8601, e.g. 2026-03-01 or 2026-03-01T09:00+07:00

JSON-LD
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "How to Brew Cold Brew Coffee",
  "image": "https://example.com/cold-brew.jpg",
  "author": {
    "@type": "Person",
    "name": "Jane Doe"
  },
  "publisher": {
    "@type": "Organization",
    "name": "Example Coffee"
  },
  "datePublished": "2026-03-01",
  "mainEntityOfPage": {
    "@type": "WebPage",
    "@id": "https://example.com/cold-brew"
  }
}
</script>
Paste the <script type="application/ld+json"> block into the page’s HTML. Valid markup does not guarantee rich results; check eligibility with Google’s Rich Results Test and only describe content that is visible on the page.

What is Schema Markup Generator?

This tool creates schema.org structured data in JSON-LD format, the format Google recommends for rich results. Pick a type – Article, Organization, Person, Product, FAQPage, Event, LocalBusiness or WebSite – fill in the form and copy the <script type="application/ld+json"> block into your page.

How to use Schema Markup Generator

  1. Choose the schema type; the form is pre-filled with an example.
  2. Replace the example values; fields marked * are recommended for that type.
  3. For FAQPage write "Q: question" and "A: answer" on separate lines.
  4. Copy the JSON-LD block into the page's HTML and test it in Google's Rich Results Test.

When to use Schema Markup Generator

Use it to add structured data to pages that don't get it from a CMS plugin. Markup must describe content visible on the page; valid JSON-LD does not guarantee rich results – eligibility and display are up to Google. For complex catalogues, generate markup from your data automatically.

How Schema Markup Generator works

Form values are mapped to schema.org properties and nested types: an Article's author becomes a Person, a publisher an Organization with an ImageObject logo, a Product's price an Offer with currency and an availability URL, an Event's venue a Place (or a VirtualLocation for online events), a LocalBusiness address a PostalAddress, and a WebSite search URL a SearchAction. Empty fields are omitted, multi-line fields become arrays, and < is escaped as \u003c so the JSON cannot close the script tag.

Common Use Cases

  • Add FAQPage markup to a support page.
  • Describe a product's price and availability.
  • Publish Organization markup with logo and social profiles.
  • Mark up an event with date, venue and status.

FAQs

JSON-LD, Microdata or RDFa?

Google supports all three but recommends JSON-LD because it is separate from the HTML and easier to maintain.

Where should the script go?

Anywhere in the <head> or <body> of the page it describes.

Why don't my FAQ rich results show?

Since 2023 Google shows FAQ rich results only for a limited set of authoritative government and health sites; the markup is still valid.

Explore more categories