Schema markup generator (JSON-LD)
Pick a schema type — Article, FAQPage, HowTo, Person, Organization, Product, or BreadcrumbList — fill in the fields, and get valid JSON-LD inside a script tag, ready to paste into your page head.
JSON-LD
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Article"
}
</script>Valid markup is not a rich result. The markup must describe content actually visible on the page — validate against the live page before shipping.
How it works
You choose one of seven schema.org types and the form adapts to show that type's relevant properties: headline, author, and dates for Article; question and answer pairs for FAQPage; steps for HowTo, and so on. Required properties are marked so you know what search engines expect at minimum, and optional fields can be left blank without breaking the output.
As you type, the tool assembles a JSON-LD object with the correct @context and @type, escapes your text safely, and wraps it in a script tag with type application/ld+json. JSON-LD is the format Google recommends because it lives in one block instead of being woven through your HTML, which makes it easier to maintain and audit.
Copy the output into your page's head (or anywhere in the HTML) and validate it with a rich results testing tool before shipping. Everything is generated in your browser, so nothing you enter leaves the page.
Assumptions and limitations
- Valid markup is not a rich result. Google decides eligibility case by case, and the markup must describe content actually visible on the page — marking up FAQs or reviews that are not on the page violates structured data guidelines and can earn a manual action.
- The generator covers the common properties for each type, not the full schema.org vocabulary. Complex nesting, multiple authors, or niche properties may need hand-editing after you copy the output.
- Syntactically valid JSON-LD can still be semantically wrong — a Product without offer data, an Article with a mismatched headline. Always test against the live page, not just the snippet.
- Rich result features change over time; a type that produces an enhanced listing today may be scaled back later. Treat schema as accurate description of your content, not a rankings lever.
Frequently asked questions
Does adding schema markup improve rankings?
Schema markup is not a direct ranking factor. What it can do is make your page eligible for rich results — FAQ dropdowns, star ratings, breadcrumb trails — which can improve click-through rate. Eligibility depends on the markup accurately matching visible page content, and Google grants it selectively.
Where do I put JSON-LD schema on my page?
Paste the script tag anywhere in your HTML — the head is the convention, but Google reads it in the body too. One block per entity is cleanest. If your CMS has a custom HTML or head-injection field, that is usually the right home for it.
Why is my FAQ schema not showing rich results in Google?
The most common causes are FAQ content that does not appear visibly on the page, eligibility restrictions Google applies to certain site types, or simply Google choosing not to show the enhancement. Validate the markup first, then confirm the questions and answers match the rendered page word for word.
What is the difference between JSON-LD and microdata?
Both express the same schema.org vocabulary, but JSON-LD sits in one self-contained script block while microdata is scattered through your HTML attributes. JSON-LD is Google's recommended format and far easier to maintain, which is why this generator only produces JSON-LD.
Is the information I type into this generator stored anywhere?
No. The JSON-LD is assembled entirely in your browser with client-side JavaScript. Nothing you enter is transmitted to a server, logged, or stored — closing the tab discards everything.
More free tools like this, by email
I publish new calculators and explainers regularly. Get them when they land — no spam, unsubscribe anytime.