Schema Markup Generator
Build valid JSON-LD for articles, FAQs, products and local businesses, ready to paste into a script tag.
Schema
One question on its own line, the answer on the lines below it, and a blank line between entries.
JSON-LD
Saving needs a Dex account. The tool never does.
How it works
- Pick a type, fill in its fields, and the JSON-LD appears ready to paste inside a script tag. Required fields are enforced, so a Product without a price is an error rather than invalid markup.
- FAQPage takes question and answer pairs in a plain text box: one question per line, the answer underneath, a blank line between entries.
- The output is serialised JSON, so it can be checked in the JSON formatter before it goes anywhere near a template.
- Nothing is validated against Google remotely and nothing is uploaded. The rules enforced here are the schema.org required properties, not a guarantee of a rich result.
Examples
An FAQ block
Paste four questions and their answers, copy the JSON-LD, and add it to the page as a script tag with type application/ld+json.
A product page
Name, price and currency are enough for a basic Offer. Availability defaults to in stock, which you should change if it is not true.
Frequently asked questions
Does adding markup guarantee a rich result?
No. Valid markup makes a page eligible; Google decides whether to show the enhancement. Markup that does not match the visible page is treated as spam.
Where does the script tag go?
In the head or the body, as a script element with type application/ld+json containing exactly this JSON. It is not executed, only read.
Which type should I choose?
Match the page: an FAQ section deserves FAQPage, a product page Product, a blog post Article, a shop with an address LocalBusiness. Do not mark up content that is not on the page.
Why does the FAQ output need pairs?
A question without an answer is invalid structured data and can invalidate the whole block, so the tool refuses rather than emitting something Google will reject.