Schema Markup Generator
Valid JSON-LD for seven schema types, with the fields Google actually requires flagged as you go.
Blog posts, news stories and guides. Powers the article rich result and Top Stories.
Keep under 110 characters.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "How to Compress Images Without Losing Quality",
"image": "https://example.com/cover.png",
"author": {
"@type": "Person",
"name": "Jane Doe"
},
"publisher": {
"@type": "Organization",
"name": "Example Tools"
},
"datePublished": "2026-09-01",
"dateModified": "2026-09-01"
}
</script>How to Use
- 1. Pick the schema type that matches your page.
- 2. Fill in the fields, starting with the ones marked required.
- 3. Check the validation notice reports no missing fields.
- 4. Copy the JSON-LD block into your page and test it in Google's Rich Results Test.
Structured Data Without the Violations
Structured data does not improve rankings. What it does is make a page eligible for rich results — star ratings, FAQ dropdowns, recipe cards, event dates — and those occupy far more space in search results than a plain blue link, which is where the click-through gain comes from. Eligibility is not a promise; Google decides per page whether to show them.
The rule that catches people out is that the markup must describe what is visible. FAQ schema for questions that only exist in the JSON, review stars for reviews nobody can read, a price that differs from the one on the page — each is a violation, and the penalty is losing rich results across the whole site rather than just that page. This is why the FAQ builder here carries that warning next to the fields.
A few format details matter more than they look. Durations have to be ISO 8601, so a twenty-minute prep time is PT20M and the string "20 minutes" is silently ignored. Dates want ISO too. Empty properties are worse than absent ones, so this generator omits any field you leave blank rather than emitting an empty string for validators to complain about.
One page can carry several blocks, and often should — an Article plus an FAQPage plus a site-wide Organization block is entirely valid. Generate them separately and paste all three.
Related: Meta Tags Generator, JSON Formatter, and JSON Schema Generator.
Frequently Asked Questions
What is JSON-LD and why use it over microdata?
JSON-LD is a block of structured data placed in a script tag, separate from your markup. Google recommends it precisely because it is separate — you can add or change it without touching the HTML, and nothing breaks if a template changes.
Will adding schema improve my rankings?
Not directly. Structured data makes a page eligible for rich results — star ratings, FAQ dropdowns, recipe cards, event dates — which usually lifts click-through rate substantially. Eligibility is not a guarantee; Google decides case by case.
Does the schema content have to match the page?
Yes, strictly. Marking up FAQs, reviews or prices that a visitor cannot see on the page is a structured data violation and can cost you rich results across the whole site. Only describe what is genuinely there.
Where do I put the generated code?
Anywhere in the HTML — the head is conventional, but Google reads it from the body too. One page can carry several blocks, so an Article plus an FAQPage plus a site-wide Organization block is perfectly valid.
How do I check it works?
Paste the page URL into Google’s Rich Results Test, which reports what it detected and any errors or warnings. The separate Schema.org validator is stricter and useful for catching vocabulary mistakes Google tolerates.