Schema Markup (JSON-LD) Generator

Pick one of four types and fill in two boxes. The generator wraps the result in a <script type="application/ld+json"> tag, ready to paste. The two boxes map to different properties depending on the type:

With the headline "How to Repot a Monstera" and a one-line description, the Article output is:

Quotation marks in your text are escaped automatically, so a question such as Do you ship "large" pots? doesn't break the JSON.

Some values in the output are fixed stand-ins. There are no boxes for them, so edit them in the copied code:

• url is always https://example.com. Replace it with the page's real address.
• author on an Article is always a Person named "Author". Put the writer's real name there.
• price on a Product is always "0.00" in "USD". Left as is, the markup describes your product as free. Enter the real price, and change the currency code if you don't sell in US dollars.
• An empty description box still writes "description": "". Fill it in or delete the line.

The FAQPage output holds one question. For more, copy the whole { "@type": "Question", … } block inside mainEntity, paste it after the first one with a comma between them, and change the text.

The generator writes a minimal skeleton. Google's documentation for each rich result lists the properties it uses, and several of them are not in the output:

• Article: datePublished, dateModified and image.
• Product: image, brand, and availability inside the offer.
• LocalBusiness: address, which Google requires for its local business result, plus telephone and opening hours.

Each new property goes on its own line inside the braces, as "name": "value", with a comma after every line except the last. One missing or extra comma is enough to make the whole block unreadable, so validate after every change.

Structured data has to describe what visitors can see on the page. A price in the markup that differs from the price on the page, or an FAQ answer that appears only in the code, can cost the page its rich result.

That makes the copy-and-paste approach risky for content that changes. If prices, opening hours or answers are edited often, have your CMS or template generate the JSON-LD from the same data that fills the page, and use this tool to prototype the shape.

Google limits which sites get FAQ rich results, so add FAQPage markup because the questions are genuinely on the page, not in the expectation of an expandable result.