Home › Tools › JSON-LD Schema Markup Generator
JSON-LD Schema Markup Generator
Generate valid JSON-LD structured data for Article, FAQ, HowTo, Product, BreadcrumbList and Organization. Fill in fields, get copy-ready markup that validates.
Pick a schema type, fill in the fields, and get JSON-LD you can paste straight into your page head. Every field is validated as you type, and the output is checked for the properties Google actually requires.
How to use it
- Choose the schema type that matches what the page actually is — not the one you wish it were.
- Fill in the fields. Required ones are marked; the validator tells you what is missing as you type.
- Copy the JSON-LD and paste it into the
<head>of your page, then test it in Google's Rich Results Test.
Structured data is a claim, not a ranking factor
Adding schema does not by itself move a page up. What it does is make your claims machine-readable: this is an article, it was published on this date, by this author, and this is the answer to this question. Systems that need that information can then use it.
The failure mode is claiming things that are not true of the page. Marking up an FAQ section that does not exist on the page, or a product the page does not sell, is a structured-data violation and can cost you eligibility for rich results entirely.
Why one @graph beats several loose blocks
Most generators emit one detached JSON-LD blob per type. That works, but it throws away the relationships: this article was published by this organization, on this website, and sits at this position in this breadcrumb trail.
Emitting a single @graph where nodes reference each other by @id expresses those relationships explicitly, and it is how the same facts stop being repeated in three places where they can drift apart. If your Organization name changes, you change it once.
Required versus recommended
Google treats some properties as required for a given rich result and others as recommended. Missing a required property means the result simply will not appear, with no error shown anywhere in Search Console.
This tool marks required fields and refuses to produce output that omits them. It does not warn about recommended fields, because those trade off against how much you want to describe.
Dates are the most common silent error
datePublished and dateModified need to be ISO 8601, and dateModified needs to mean something. Incrementing it on every deploy to make a page look fresh is a well-known trick that stops working the moment anyone compares it against the actual content.
Set dateModified when the content genuinely changes. A page whose modified date moves every day but whose words never change is telling crawlers the date field is noise.
Questions
Does schema help rankings?
Not directly. It makes your content eligible for rich results and helps systems understand what the page is. The ranking effect, if any, is indirect.
Where does the JSON-LD go?
Anywhere in the head or body. Google reads it regardless of position. The head is conventional and keeps it out of the way.
Can I use several types on one page?
Yes. Either as separate script blocks or, preferably, as one @graph with cross-referenced @id values so the entities are explicitly related.
Why does my FAQ rich result not appear?
Most often because the marked-up questions and answers are not visible in the page HTML, or the page is not indexed. Schema must describe content that actually exists on the page.
Related tools
llms.txt Generator
Build a valid llms.
Meta Tag Generator
Generate clean page title, meta description, canonical, Open Graph and Twitter card tags.
Heading Structure Analyzer
Paste HTML and get a clean H1–H6 outline plus a list of real problems: missing or duplicated H1, skipped levels, and headings that are too long.