Schema Markup Generator

Build JSON-LD for Article, Product, Organization, Person and LocalBusiness from a form, with nested offers, authors and safe script escaping.

The interactive tool loads here when JavaScript runs.

About this tool

What is the Schema Markup Generator?

The Schema Markup Generator builds JSON-LD structured data from a short form. Pick one of five templates (Article, Organization, Product, Person or Local Business), fill in the fields, click Generate Schema Markup, and copy or download the result.

It does more than copy fields into JSON. An Article's author becomes a Person and its publisher an Organization, a Product's price, currency and availability are moved into an Offer, a brand becomes a Brand, a Person's company becomes an Organization, and a Local Business address becomes a PostalAddress. Any "</" sequence in your text is written as "<\/" so the JSON can be pasted inside a script tag without closing it early.

The generator runs entirely in your browser. It covers one item per page type and a handful of common properties; for reviews, ratings, opening hours specifications or @graph documents you will need to edit the JSON by hand.

  • Five templates: Article, Organization, Product, Person, Local Business
  • Nested Person, Organization, Brand, Offer and PostalAddress objects
  • Availability normalised to schema.org enumeration URLs
  • Output escaped for safe use inside a script tag
  • Copy or download as JSON; nothing leaves your browser
Read the guide: JSON-LD Structured Data: What Still Earns Rich Results

Updated

How to use the Schema Markup Generator

  1. Choose a template from the Schema Type dropdown.
  2. Fill in the fields under Schema Fields. Starred fields are the ones the template treats as essential; leave optional ones empty and they are omitted.
  3. Click Generate Schema Markup to see the JSON-LD on the right.
  4. Click Copy or Download, then paste the JSON inside <script type="application/ld+json"> ... </script> in the page's head or body.
  5. Test the live page with Google's Rich Results Test, or paste the JSON into the Structured Data Validator.

Worked examples

Product with an offer

Input

Product Name: Ceramic Mug, Brand: Acme, Price: 12.50, Currency: eur, Availability: In Stock

Output

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Ceramic Mug",
  "brand": { "@type": "Brand", "name": "Acme" },
  "offers": {
    "@type": "Offer",
    "price": "12.50",
    "priceCurrency": "EUR",
    "availability": "https://schema.org/InStock"
  }
}

Price, currency and availability belong to the Offer, not the Product. "In Stock" is normalised to the schema.org enumeration URL and the currency is upper-cased to an ISO 4217 code.

Article author and publisher

Input

Headline: Shipping JSON-LD, Author: Ada Lovelace, Publisher: Acme Blog

Output

"author": { "@type": "Person", "name": "Ada Lovelace" },
"publisher": { "@type": "Organization", "name": "Acme Blog" }

Google's Article documentation recommends author as a Person or Organization object rather than a bare string.

Background and insight

Schema.org was launched in 2011 by Google, Bing and Yahoo (Yandex joined soon after) as a shared vocabulary for describing things on web pages. JSON-LD, a W3C Recommendation since 2014 with version 1.1 in 2020, is the format Google recommends because it sits in its own script element instead of being woven through the visible HTML like Microdata or RDFa.

Valid schema.org is not the same as a rich result. Schema.org itself has no required properties, but each Google search feature does: a Product snippet needs a name plus offers, review or aggregateRating; a Recipe needs a name and image; an Event needs a name, startDate and location. Google also changes which types earn visual treatment. In 2023 it limited FAQ rich results to well-known government and health sites and dropped HowTo rich results altogether.

Structured data has to describe content that is visible on the page. Marking up a price, rating or author that users cannot see is against Google's structured data policies and can lead to a manual action, so treat the generator's output as a description of the page you already have.

Common use cases

  • Product pages

    Add name, brand, price and availability so the product is eligible for product snippets.

  • Company home page

    Describe the organization's name, logo, URL and contact details for knowledge panels.

  • Blog posts

    Mark up headline, author, publisher, date and image on articles.

  • Local shops and offices

    Publish name, address, phone and opening hours for a LocalBusiness.

Tips and limitations

  • Mark up only what is visible on the page. Hidden prices or ratings break Google's structured data guidelines.
  • Use absolute https URLs for image, logo and url values.
  • Dates should be ISO 8601, such as 2026-10-24 or 2026-10-24T09:30:00+01:00. The date picker produces the first form.
  • One page can carry several JSON-LD blocks, or one block with an @graph array; Google reads both.
  • FAQPage and HowTo markup are still valid schema.org but no longer produce rich results for most sites, so they are not offered here.

Sources and further reading

  1. Introducing schema.org: Search engines come together for a richer web, Google Search Central Blog. The 2011 launch announcement
  2. JSON-LD 1.1, W3C. The W3C Recommendation for the format
  3. General structured data guidelines, Google Search Central. The rule that markup must describe visible content
  4. Structured data markup that Google Search supports, Google Search Central. Required properties for each rich result type
  5. Changes to HowTo and FAQ rich results, Google Search Central Blog. The 2023 limits on FAQ and HowTo results

Frequently asked questions

Where do I put JSON-LD schema markup on a page?

Paste it inside a <script type="application/ld+json"> element. Google reads it in the head or the body, so put it wherever your template makes it easiest. Each block can describe one item, an array of items, or an @graph of linked items, and a page can have several blocks.

Does adding schema markup improve rankings?

Not directly. Google says structured data helps it understand a page and makes it eligible for rich results such as product prices or recipe images, which can raise click-through. It does not guarantee a rich result, and markup that does not match visible content can trigger a manual action.

Why does the generator move price into an offers object?

In schema.org, price, priceCurrency and availability are properties of Offer, not of Product. A Product with a top-level price is not valid for Google's product snippets. The generator builds an Offer with the price as entered, an upper-case currency code and an availability URL such as https://schema.org/InStock.

Should I still add FAQPage schema?

Only if you have a reason beyond Google rich results. Since August 2023 Google shows FAQ rich results only for well-known, authoritative government and health sites, and it removed HowTo rich results in September 2023. The markup is still valid and other consumers may read it.

Why does the JSON contain <\/ instead of </?

A browser ends a script element at the first </script it finds, even inside a JSON string. Writing the slash as \/ is a legal JSON escape, so the data parses to the same text while the script element stays intact. This protects pages where a field contains HTML or user-supplied text.

What is the difference between schema.org and JSON-LD?

Schema.org is the vocabulary: types like Product and properties like offers. JSON-LD is one syntax for writing that vocabulary, as JSON with @context and @type keys. Microdata and RDFa are the other syntaxes; they put the same vocabulary into HTML attributes instead of a separate script block.

Is there an in-depth guide to the Schema Markup Generator?

Yes. “JSON-LD Structured Data: What Still Earns Rich Results” covers the background, how it works, common pitfalls and worked examples. Read the full guide.