Schema.org JSON-LD
Build Article, FAQPage, Recipe, BreadcrumbList, and Organization schema. Validates against Google’s required properties; emits ready-to-paste <script type=application/ld+json>.
Article
Author (Person)
Publisher (Organization)
No issues detected. Verify the final output with Google’s Rich Results Test before going live.
JSON-LD output
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "How to Brew the Perfect Espresso",
"description": "A complete guide to dialing in your espresso shots — grind size, dose, yield, and time.",
"image": "https://example.com/blog/espresso-cover.jpg",
"datePublished": "2026-04-24",
"dateModified": "2026-04-24",
"mainEntityOfPage": {
"@type": "WebPage",
"@id": "https://example.com/blog/perfect-espresso"
},
"author": {
"@type": "Person",
"name": "Alice Chen",
"url": "https://example.com/authors/alice-chen"
},
"publisher": {
"@type": "Organization",
"name": "Example Coffee Co.",
"logo": {
"@type": "ImageObject",
"url": "https://example.com/logo.png"
}
}
}
</script>After deployment, validate at search.google.com/test/rich-results.
About this tool
Schema.org JSON-LD is structured data — machine-readable annotations that tell search engines what a page is. Google reads it to surface rich results: FAQ accordions, recipe cards with images and ratings, breadcrumb trails, article author boxes. Done well, structured data gets your page more screen real estate in search results without changing anything visible on the page itself.
The builder covers the five most useful types. Article with nested Person author and Organization publisher (the structure Google expects for news and blog post snippets). FAQPage for guides with multiple questions — Google's FAQ rich result is the single biggest SERP real-estate grab available. Recipe with ISO 8601 durations, structured ingredient and instruction lists, and aggregate rating. BreadcrumbList with proper position numbering. Organization for sitewide identity (publisher, logo, social profiles, contact).
The output is automatically wrapped in a
<script type="application/ld+json"> tag for
pasting into your page head — toggle that off if you need just the
JSON. Empty fields are removed before output.
Always validate before shipping. Paste the generated JSON-LD into Google's Rich Results Test to confirm it parses, the right rich-result type is detected, and no required fields are missing. The validation panel in this tool catches the common mistakes; Google's validator catches the rest.
Frequently asked questions
Will my generated JSON-LD pass Google’s Rich Results Test?
For Article, FAQPage, Recipe, and BreadcrumbList — yes, the output follows Google’s required and recommended properties. The validation panel flags missing fields before you ship. Always run the final HTML through search.google.com/test/rich-results before going live.
What schema types are supported?
Article (BlogPosting, NewsArticle), FAQPage, Recipe, BreadcrumbList, and Organization. These cover the schema types eligible for Google rich results plus the schema most often used for site identity.
How do durations work in Recipe?
Enter prep, cook, and total time as plain minutes — the generator converts to ISO 8601 duration format (PT30M for 30 minutes, PT1H30M for 90 minutes). Google requires ISO 8601 for durations.
Why does FAQPage need 3+ questions?
Google’s FAQ rich results don’t reliably trigger with one or two questions. Three is the de facto minimum. The validation panel flags this as a warning rather than an error.
Does the generator strip empty fields?
Yes. Empty strings, undefined values, and empty arrays are removed from the JSON-LD before output, so you get only the fields you actually filled in.