Schema.org JSON-LD Generator
Generate ready-to-paste Schema.org JSON-LD structured data for Article, Product, LocalBusiness, FAQ, BreadcrumbList, Organization, Person, Event, Recipe, and HowTo. Helps search engines understand your page and may make it eligible for rich results — all in your browser.
Schema fields
1200×630 minimum recommended
ISO 8601: 2026-05-01T09:00:00Z
Optional
JSON-LD output
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "How We Cut Our AI API Bill in Half",
"description": "Twelve token-optimization tactics for production LLM apps in 2026.",
"image": "https://example.com/og-image.jpg",
"author": {
"@type": "Person",
"name": "Jane Doe",
"url": "https://example.com/about/jane"
},
"publisher": {
"@type": "Organization",
"name": "Example Inc.",
"logo": {
"@type": "ImageObject",
"url": "https://example.com/logo.png"
}
},
"datePublished": "2026-05-01T09:00:00Z",
"dateModified": "2026-05-01T09:00:00Z",
"mainEntityOfPage": {
"@type": "WebPage",
"@id": "https://example.com/blog/ai-api-cost-optimization"
}
}Test before deploying
After pasting into your page, validate at Google Rich Results Test or Schema.org validator. The Rich Results Test shows which Google rich results the page may be eligible for; the Schema.org validator checks the markup against the vocabulary.
About Schema.org JSON-LD Generator
The Schema.org JSON-LD Generator builds valid, Google-friendly structured data for the ten most common Schema.org types — Article, Product, LocalBusiness, FAQ, BreadcrumbList, Organization, Person, Event, Recipe, and HowTo — through simple form-based inputs. The output is a ready-to-paste `<script type="application/ld+json">` block that drops directly into your page's <head> or just before </body>. Every form is built around the fields commonly used for Google rich results, with required fields marked with an asterisk so you can ship the minimum viable schema first and expand later. Whether Google shows a rich result is always up to Google. All generation runs in your browser — your content never leaves the device.
Why use a Schema.org JSON-LD Generator?
Schema.org structured data tells search engines what a page is about. Google can use it for rich results such as recipe cards, product price and rating snippets, breadcrumbs and event listings — and missing or invalid schema can make a page ineligible. FAQ and HowTo markup is still valid Schema.org, but Google now shows FAQ rich results only for well-known authoritative government and health sites and no longer shows HowTo rich results, so treat those two as plain structured data that may or may not produce a rich result. Writing JSON-LD by hand is error-prone: typos in `@type` values, missing required fields, wrong date formats, malformed nested objects. This tool eliminates that friction with form-based inputs, warnings for empty required fields on Article, Product, FAQ and Breadcrumb, and a copy-ready output block. Think of it as the structured-data equivalent of a meta-tag generator.
Who is it for?
Built for SEO specialists adding structured data to client sites, content marketers shipping FAQ and how-to pages, e-commerce developers wiring up Product schema for rich results, local-business owners adding LocalBusiness markup, technical writers documenting recipes and how-tos, news publishers tagging Articles, and developers integrating Schema.org with their CMS or static-site generator. Anyone whose Search Console says 'no rich results detected' should bookmark this.
How to use the tool
Pick a schema type from the tabs (Article, Product, LocalBusiness, FAQ, BreadcrumbList, Organization, Person, Event, Recipe, HowTo)
Fill in the form fields — required fields are marked, optional fields can be left blank or filled in for richer results
Watch the JSON-LD output update live on the right
For arrays (FAQ questions, breadcrumb steps, recipe ingredients, etc.), click 'Add' to append, 'X' to remove
Copy the output and paste into your page's <head> or just before the closing </body> tag — both work
Test the result in Google's Rich Results Test (search.google.com/test/rich-results) before deploying
Key Features
10 most-used schema types
Article (news + blog posts), Product (e-commerce), LocalBusiness (storefronts), FAQ (question-and-answer markup), BreadcrumbList (breadcrumb chips), Organization (company info), Person (author / staff), Event (concerts, conferences), Recipe (recipe markup), HowTo (step-by-step guides).
Form-based — no JSON wrangling
Each schema type renders the fields commonly used for rich results, with required fields marked with an asterisk. No more 'is this @type spelled right' debugging.
Live validation
The output JSON updates as you type, and a warning appears when required fields are empty (Article, Product, FAQ and Breadcrumb). Dates and URLs are not validated — the form only shows the expected ISO 8601 format as a hint — so check them in the Rich Results Test.
Repeatable arrays for FAQ / breadcrumb / recipe / how-to
Add as many FAQ pairs, breadcrumb steps, recipe ingredients, or how-to instructions as you need with one-click Add / Remove.
Ready-to-paste output
Outputs the JSON object plus a wrapped <script type="application/ld+json"> block — copy whichever you need based on your CMS or template engine.
100% client-side
All form rendering and JSON-LD assembly runs in your browser. Your page content never leaves the device — verifiable in DevTools.
Common Use Cases
Adding FAQ schema to a help-center article
Scenario: You've written an FAQ section on a help-center page and want to mark it up as structured data.
✓ Pick FAQ, add each Q+A pair, copy the output, paste into the page. Search engines can read the questions and answers as structured data. Note that Google shows FAQ rich results only for well-known authoritative government and health sites, so most pages won't get an accordion.
Marking up a product page for rich results
Scenario: Your e-commerce product page should show price, availability, rating, and review count under the search result — but doesn't, because Product schema is missing or incomplete.
✓ Pick Product, fill name + image + price + currency + availability + aggregateRating, copy the output, paste into the product template. After Google recrawls the page, it may show price and rating details in results, but that is not guaranteed.
Setting up LocalBusiness for Google Business + Maps
Scenario: You manage a small business website and want its name, address, phone number and opening hours available as structured data.
✓ Pick LocalBusiness, fill name + address + phone + opening hours + geo, copy the output, paste in your homepage. Search engines can then read your business details directly from the page; keep them consistent with your Google Business Profile.
Tagging a recipe or how-to guide
Scenario: You publish recipes or how-to guides and want to add structured data for them.
✓ Pick Recipe or HowTo, add ingredients/supplies and step-by-step instructions, copy the output. Recipe markup can make a page eligible for Google's recipe rich results; Google no longer shows HowTo rich results, so HowTo markup is plain structured data.
Cleaning up an SEO audit's 'missing schema' findings
Scenario: An SEO audit flagged 200 pages missing structured data; you need to ship templates for Article, BreadcrumbList, and Organization schema fast.
✓ Build one of each in the tool, copy as a template, parameterize with your CMS variables, deploy. Audit closes in a sprint instead of a quarter.
Field structures follow Schema.org property names and commonly used rich-result fields.
100% client-side — your content never leaves your device. No upload, no API call.
Static site — no backend dependency.
Frequently Asked Questions
What's the difference between JSON-LD, microdata, and RDFa?
All three are formats for embedding Schema.org structured data in HTML. JSON-LD is Google's recommended format and what this tool generates — it sits in a single <script> block separate from your visible HTML, which makes it easier to maintain and unlikely to break your page's rendering. Microdata and RDFa interleave attributes into your existing HTML; both are still supported but harder to work with at scale.
Where do I paste the output?
Either inside your <head> tag or just before </body> — Google parses both. <head> is more conventional and what most CMS templates use. For dynamic pages (e-commerce, blog), inject the script with the page-specific values from your CMS or framework's data layer.
How do I test if my schema is valid?
Use Google's Rich Results Test at search.google.com/test/rich-results — paste either your live URL or the raw HTML+schema. It tells you exactly which rich results your page is eligible for, plus any validation errors. The Schema.org validator at validator.schema.org also runs the spec-level checks.
Why doesn't my page show rich results immediately?
Even with valid schema, Google needs to recrawl the page (usually 1-7 days) and decide whether the page meets its quality + content guidelines (rich results aren't guaranteed even with perfect schema). Submit the URL through Search Console's URL inspection tool to request faster recrawl.
Can a page have multiple JSON-LD scripts?
Yes — and it often should. A blog post page might have Article schema, BreadcrumbList for navigation, and Organization for the publisher, all in separate <script> blocks. Google reads each block separately when checking rich-result eligibility.
What about the @id field for cross-linking schemas?
If you have multiple schemas on a page (e.g. an Article that references its Author and Publisher), you can give each its own URL-shaped @id and reference it from the other (e.g. "author": { "@id": "https://example.com/about/jane" }). This tool keeps the basic forms simple — for complex cross-linked graphs, generate each piece separately and combine.
Does this support all of Schema.org's 800+ types?
No — it covers 10 commonly used types. For uncommon types (Vehicle, MedicalProcedure, GovernmentService, etc.), the structure is the same: an @context, @type, and a set of properties. Use one of the included types as a starting point and edit by hand for niche types.
Does this tool send my content anywhere?
No. Form rendering, JSON-LD assembly, and validation all run in your browser. You can verify in DevTools — your content is never sent over the network.
Technical Specifications
Supported Formats
- ✓Schema.org @context (https://schema.org)
- ✓Article (news + blog posts) with author + publisher + datePublished + image
- ✓Product with offers (price, currency, availability), brand, aggregateRating
- ✓LocalBusiness with PostalAddress, GeoCoordinates, opening hours
- ✓FAQPage with mainEntity Question/Answer pairs
- ✓BreadcrumbList with positioned ListItem entries
- ✓Organization with logo + sameAs (social profiles)
- ✓Person with jobTitle + worksFor + sameAs
- ✓Event with location, offers, performer, startDate/endDate
- ✓Recipe with ingredients, instructions, prep/cook/total time, yield, nutrition
- ✓HowTo with steps, supplies, tools, totalTime
Limits & Performance
- •File Size: Form-based — no input size limit
- •Validations: Warnings for empty required fields (Article, Product, FAQ, Breadcrumb); no date or URL validation
- •Response Time: Synchronous, in-browser
- •Browsers: All modern browsers (Chrome, Firefox, Safari, Edge); works offline once loaded
Pro Tips
- For Product schema, the fields that matter most for rich results are name, image, offers (price + currency + availability), and aggregateRating. Skip those and you get no enhancement, even with everything else present.
- For FAQ schema, each Question needs one accepted answer. Keep in mind that Google shows FAQ rich results only for well-known authoritative government and health sites, so for most pages this is plain structured data rather than a search-result feature.
- BreadcrumbList works only when the visible breadcrumb on your page matches the schema. Don't 'manufacture' breadcrumbs in schema that aren't visible to users — Google's guidelines treat markup that doesn't reflect visible content as a violation.
- Use ISO 8601 for dates (for example 2026-05-01T09:00:00Z, ideally with a timezone). The tool does not validate what you type, so check the format yourself and in the Rich Results Test.
- LocalBusiness should match your Google Business Profile name, address, and phone exactly — discrepancies hurt local-pack ranking. If your storefront has multiple locations, generate one schema per location.
- Recipe rich results need an image, and they work best with details such as totalTime and recipeYield filled in.
- After updating schema, request indexing via Google Search Console URL Inspection — otherwise Googlebot may take days to recrawl and re-evaluate the page.
- For multi-page sites, build the schema once, then template the values from your CMS data layer. Don't paste static schema across hundreds of pages — it goes stale fast.
Share This Tool
Found this tool helpful? Share it with others who might benefit from it!
💡 Help others discover useful tools! Sharing helps us keep these tools free and accessible to everyone.