Generate valid JSON-LD schema markup for SEO rich snippets in seconds. 8 schema types covered: Article, Product, FAQPage, Recipe, LocalBusiness, Event, Organization, BreadcrumbList. Live preview, validation of required fields, copy as JSON or as a complete <script type="application/ld+json"> snippet ready to paste in your <head>. Free, runs in your browser, no signup.
—
{}
Schema.org is a shared vocabulary co-developed by Google, Microsoft, Yahoo and Yandex that lets you describe the meaning of your web content in a way search engines understand. It defines types like Article, Product, Recipe, Event and hundreds more, each with their own properties (price, author, date, address, rating, etc.).
JSON-LD (JSON for Linked Data) is the format Google explicitly recommends for adding schema markup. You drop a <script type="application/ld+json"> tag in your page's <head> (or anywhere in <body>) containing a JSON object describing your content. Unlike Microdata or RDFa, JSON-LD lives separately from your HTML — easier to write, easier to maintain, no risk of breaking your design.
When Google parses a page with valid schema markup, it can show rich snippets in search results: star ratings on products, recipe cards with cook times, FAQ accordions, breadcrumb trails, event dates and venues. Rich snippets dramatically increase click-through rates — typical lift is 20-30% for product results, sometimes more.
Step 1 — Pick a schema type. Eight chips at the top cover the most common cases:
Step 2 — Fill in the form. Required fields are marked with a red asterisk; the preview will warn if any are missing. Most fields accept plain text; URL fields validate the format; dates use a date picker.
Step 3 — Copy or download. Three options: Copy JSON (raw object), Copy with <script> (full snippet ready to paste in your <head>), or Download .html (the snippet as a file).
Step 4 — Paste into your site. Best placed in the <head> of the relevant page. Multiple schema types per page are fine — just paste multiple <script> blocks.
Schema markup is not a direct ranking factor — Google has been clear about this. But it has powerful indirect SEO benefits:
In short: schema markup doesn't make you rank higher directly, but it gives Google reasons to display your result more prominently — which compounds into more clicks, more engagement, and over time, better rankings.
Three formats exist for adding schema to a page:
<script> tag, fully separate from HTML, easy to copy-paste, no risk of breaking layout.itemscope, itemtype, itemprop) on existing HTML elements. Older approach, more verbose.For 99% of sites in 2025, use JSON-LD. It's the format every modern guide recommends, the format the major search engines optimize for, and the only one this generator outputs.
The standard location is inside the page's <head> element, alongside other meta tags. It can also be placed anywhere in <body> (Google parses both), but <head> is the convention. For pages with multiple schema types (e.g. an article that's also a product), paste multiple <script> blocks — each independent.
Before deploying, validate with Google's official tools:
If both pass, you're ready to deploy. Note: passing validation only means the markup is syntactically correct — Google can still choose not to display rich snippets if your content quality is low or the schema seems misleading. Don't markup content that doesn't match (e.g. fake reviews); Google penalizes spam schema.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "How to Generate Schema Markup",
"image": "https://example.com/cover.jpg",
"author": { "@type": "Person", "name": "Jane Doe" },
"datePublished": "2026-05-23",
"publisher": {
"@type": "Organization",
"name": "Example Blog",
"logo": { "@type": "ImageObject", "url": "https://example.com/logo.png" }
}
}
</script>{
"@context": "https://schema.org",
"@type": "Product",
"name": "Wireless Headphones X1",
"brand": { "@type": "Brand", "name": "Acme" },
"offers": {
"@type": "Offer",
"price": "149.99",
"priceCurrency": "USD",
"availability": "https://schema.org/InStock"
},
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": "4.5",
"reviewCount": "237"
}
}{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{ "@type": "Question", "name": "What is JSON-LD?", "acceptedAnswer": { "@type": "Answer", "text": "JSON for Linked Data — the format Google recommends." }},
{ "@type": "Question", "name": "Where do I put it?", "acceptedAnswer": { "@type": "Answer", "text": "Inside the page's <head> element." }}
]
}Schema.org is a shared vocabulary developed by Google, Microsoft, Yahoo and Yandex that defines structured data types (Article, Product, Recipe, etc.). Adding this markup helps search engines understand and display your content with rich snippets — star ratings, recipe cards, FAQ blocks, event dates.
JSON-LD (JavaScript Object Notation for Linked Data) is the format Google recommends for adding schema markup. It's a JSON object placed inside a <script type="application/ld+json"> tag. Unlike Microdata, it lives separately from your HTML markup — easier to add, maintain, and reuse.
Not as a direct ranking factor (Google has been clear about this). But it has powerful indirect benefits: rich snippets (stars, prices, FAQ, recipes) boost click-through rates 20-30%, Knowledge Graph eligibility, better positioning in voice and AI search results, and easier entry into featured snippets. Higher CTR is a behavioral signal that influences rank over time.
Use JSON-LD. Google explicitly recommends it, it's cleaner (lives in a script tag, separate from HTML), easier to copy-paste, and doesn't risk breaking your layout. Microdata is older inline markup; RDFa is niche/academic. Every modern SEO guide uses JSON-LD.
Inside the page's <head> element is the convention. Google also parses JSON-LD anywhere in <body>, so it's flexible. For multiple schema types on the same page (e.g. an article with breadcrumbs and FAQ), use multiple <script> blocks — each independent.
Yes, and you should. A typical content page might have: BreadcrumbList (navigation), Article (content), Organization (publisher), FAQPage (Q&A section). Each goes in its own <script> block. Alternative: combine into a single script using @graph array (more advanced).
Use Google's Rich Results Test (paste URL or markup, see eligible rich result types) and the Schema Markup Validator (structural validity check). Pass both before deploying. Then check Google Search Console's "Enhancements" section over the next weeks to see actual rich-result impressions.
(1) Marking up content that doesn't match (e.g. fake reviews, Product schema on a landing page that doesn't sell anything) — Google penalizes spam schema. (2) Missing required fields — the rich snippet won't appear. (3) Inconsistency between visible page content and schema data. (4) Marking up the wrong type (e.g. BlogPosting when it's actually a Product). Always match the schema to what the page actually contains.