JSON-LD Schema Generator
Build structured data for Article, FAQ, Product, Organization, and Breadcrumb schemas. Paste-ready, spec-compliant, works with Google rich results AND AI crawlers (GPTBot, ClaudeBot, PerplexityBot).
2026 schema landscape — what changed
- • FAQPage rich results retired May 7, 2026 — the markup is still valid Schema.org and is still parsed by AI engines for extraction, but it no longer produces the FAQ accordion in Google's SERP. Keep adding it for AI; don't expect SERP rich results.
- • HowTo rich results deprecated September 2023 — markup still valid, no SERP benefit. Same logic: still useful for AI extraction.
- • Speakable schema is still in beta — US English + Google Home only. Narrow utility for news publishers.
- • Google's AI Optimization Guide explicitly states no AI-specific schema is required. LLMs.txt files are opt-in convention, not a ranking factor.
For blog posts, news articles, and editorial content.
Output
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Article",
"author": {
"@type": "Person"
},
"publisher": {
"@type": "Organization"
}
}
</script>{
"@context": "https://schema.org",
"@type": "Article",
"author": {
"@type": "Person"
},
"publisher": {
"@type": "Organization"
}
}Paste the first block into your page's <head> or just before the closing </body>.
Pick a schema type
Article, FAQ, Product, Organization, or Breadcrumbs — whatever matches your page.
Fill in the fields
Only required fields are marked. Leave optional fields blank — they won't appear in the output.
Copy and paste
Copy the <script> block and paste it into your page's <head>. Done.
Verify your schema before publishing
Both validators are free. Run both — they catch different classes of errors.
- Google Rich Results Test → — catches syntax errors and shows which rich result types your page is eligible for.
- Schema.org Validator → — catches Schema.org spec violations even for types Google doesn't render as rich results.
Frequently asked questions
What is JSON-LD?▾
JSON-LD (JavaScript Object Notation for Linked Data) is the recommended format for adding structured data to web pages. Google, Bing, and AI search engines like ChatGPT, Perplexity, Gemini, and Claude all parse it to understand page content. It's implemented as a script tag with type="application/ld+json" in the head of the page.
Which schema types still produce rich results in 2026?▾
About 31 schema types currently produce rich results in Google's search results per the Google Search Gallery (developers.google.com/search/docs/appearance/structured-data/search-gallery). The highest-impact ones: Article/BlogPosting, Product, Event, Recipe, LocalBusiness, VideoObject, Organization, Breadcrumb, Review/AggregateRating, JobPosting, Course, Movie. FAQPage rich results were retired on May 7, 2026 — but the markup is still valid Schema.org and is still parsed by AI engines for extraction. HowTo rich results were deprecated in September 2023.
Which schema type should I use?▾
Use Article for blog posts and news. FAQPage for question-answer pages (still parsed by AI even though Google rich results retired May 2026). Product for e-commerce pages. Organization on your about and homepage to establish brand identity. BreadcrumbList for any hierarchical page. The Princeton GEO paper (Aggarwal et al., KDD 2024) found that adding structured citations and explicit author attribution correlates with +27.7% citation visibility lift across AI engines.
Does AI search require special schema markup?▾
No. Google's official AI Optimization Guide (developers.google.com/search/docs/fundamentals/ai-optimization-guide) states verbatim: "Structured data isn't required for generative AI search, and there's no special schema.org markup you need to add." Standard Article, Organization, Person, and Product schema are parsed by AI engines for context — but no AI-specific schema type exists. LLMs.txt files are also NOT a Google ranking factor; they're an opt-in convention popularized by Mintlify, not a platform requirement.
Where do I put the generated code?▾
Paste the full <script type="application/ld+json"> block into the <head> of your page, or just before the closing </body> tag. Both work — <head> is cleaner and loads earlier, which helps for crawler reliability on slow pages or large JavaScript bundles.
Do AI search engines actually use this?▾
Yes. ChatGPT, Perplexity, Gemini, Claude, and Microsoft Copilot all parse structured data when deciding which pages to cite. The Princeton GEO paper measured +27.7% Position-Adjusted Word Count lift from inline citations and structured source attributions — and schema is one of the strongest signals for source attribution. Clear schema signals trustworthiness, easy fact extraction, and entity clarity — all direct factors in AI citation probability.
How do I validate the generated schema?▾
Two free tools: Google's Rich Results Test (search.google.com/test/rich-results) catches syntax errors and confirms which rich result types your page is eligible for. Schema.org's validator (validator.schema.org) catches Schema.org spec violations even for types Google doesn't render as rich results. Run both before deploying — they catch different classes of errors. Schema.org is currently on v30 (mid-2026).
Is the generated schema valid?▾
Yes — the output conforms to Schema.org vocabulary and Google's structured data guidelines as of June 2026. We recommend running it through Google's Rich Results Test (search.google.com/test/rich-results) before deploying to catch any page-specific edge cases or content-match warnings.
Related free tools
Want a full AI SEO audit?
This tool checks one thing. TurboAudit runs 250+ checks across 7 branches — schema, E-E-A-T, AI citeability, and more. Start with 5 free audits, no credit card.