Why do I need JSON-LD?

Search engines like Google and Bing use structured data to better understand your page. However, some visual features have been retired, including the SearchAction sitelinks search box and Google FAQ rich results, so focus on currently supported types.

Where do I put the generated JSON-LD?

Anywhere inside or , wrapped in a tag. Enable the 'Wrap in script tag' option in this tool to get paste-ready output.

Is my input sent to any server?

No. Everything runs entirely in your browser and nothing is transmitted externally, so it's safe to enter sensitive data.

How do I validate the output?

Paste the generated JSON-LD into Google's Rich Results Test (https://search.google.com/test/rich-results) or the Schema Markup Validator (https://validator.schema.org).

JSON-LD Generator

Generate Schema.org structured data from simple form inputs. Seven schema types supported, with current guidance for Google's retired SearchAction and FAQ rich result features.

Schema type

Output format

Raw JSON Wrapped in <script> tag

Generated JSON-LD

What is JSON-LD?

JSON-LD (JSON for Linking Data) is a structured data format that uses the Schema.org vocabulary to describe the meaning of your web pages to search engines. It's the format Google, Bing, and others officially recommend - you just drop a <script type="application/ld+json"> block into your HTML.

Structured data helps search engines and AI systems understand page meaning, but not every schema type still creates a visual search feature. Google removed the sitelinks search box starting November 21, 2024, and FAQ rich results stopped appearing from May 7, 2026.

The seven schemas supported here

WebSite - site-wide name, URL, and language metadata. SearchAction for the sitelinks search box is retired, but site name data remains useful.
Organization - company or group info. Include a logo and social profile URLs in sameAs to improve Knowledge Graph associations.
Article / BlogPosting - news or blog articles. author, datePublished, and a cover image are the key rich-result fields.
BreadcrumbList - hierarchy trail. Search results will display Home › Category › Current page instead of the raw URL.
Product - commercial products. Required for price, availability, and aggregate-rating rich results.
Review - a review of a specific product, service, business, or creative work. Use it only when the reviewed item is explicit.
FAQPage - FAQ content. Google's FAQ rich result is no longer shown, so treat new FAQPage markup as a limited-use option rather than a CTR tactic.

2026 update

SearchAction - Google's sitelinks search box UI is retired. This tool omits it by default and only generates it when you explicitly opt in for legacy compatibility.
FAQPage - Google FAQ rich results no longer appear in Search. Keep visible FAQ content for readers, and only keep FAQPage JSON-LD for narrow government/health cases or other consumers.
Still worth maintaining - WebSite name/url, Organization, BreadcrumbList, Product, and Review remain clear structured-data signals.

How to validate

Always validate generated JSON-LD with the official tools before shipping:

Google Rich Results Test - checks if your page is eligible for rich results
Schema Markup Validator - validates Schema.org syntax and vocabulary

Required and recommended fields by type

All "required" fields must be present for a page to be eligible for rich results. Based on Google's official documentation.

Article - Required: headline, image, datePublished. Recommended: author, dateModified, publisher.logo. Images should be at least 1200px wide.
FAQPage - Google FAQ rich results stopped appearing on May 7, 2026. If you still generate FAQPage JSON-LD, every Question needs name and acceptedAnswer.text, and the same content must be visible in the page HTML.
BreadcrumbList - Each ListItem needs position, name, and item (URL). The final item may omit item.
Product - Required: name, image, offers.price, offers.priceCurrency. Add aggregateRating or review to enable star ratings in search results.
Recipe - Required: name, image, recipeIngredient, recipeInstructions. Adding cook time, nutrition info, and ratings produces richer results.
Event - Required: name, startDate, location. For online events use eventAttendanceMode: OnlineEventAttendanceMode and location: VirtualLocation.
LocalBusiness - Key fields: address, telephone, openingHoursSpecification. Keep this consistent with your Google Business Profile - they are separate systems.

Common errors and fixes

"The value provided for X is invalid" - Dates must follow ISO 8601: 2026-05-05 or 2026-05-05T15:30:00+00:00. Human-readable date strings will be rejected.
FAQPage content mismatch with HTML - The Google FAQ rich result is retired, but JSON-LD questions that do not appear in the visible page can still create quality and spam-policy risk.
Missing itemReviewed - Review-related schemas (Review, AggregateRating) require an explicit itemReviewed property (Book, Product, Service, etc.).
Relative image URLs - Paths like /image.jpg may not resolve correctly for Google's crawler. Always use absolute URLs: https://example.com/image.jpg.
Multiple JSON-LD blocks are fine - One page can include separate <script type="application/ld+json"> blocks for Article, BreadcrumbList, and FAQPage simultaneously.

Official references

Google Search Structured Data Gallery - Full list of supported rich result types and field requirements.
Schema.org - The official JSON-LD vocabulary standard.
Google Structured Data Guidelines - Spam policies and quality requirements.
JSON-LD official documentation - JSON-LD 1.1 specification.
Google Search Console - The "Enhancements" report shows structured data errors across your entire site.
JSON-LD 2026 update: SearchAction and FAQ rich results - Practical notes from Whisky Noob on what to remove and what to keep.

For a complete SEO foundation, pair structured data with a Robots.txt Generator for crawler control, a Favicon Generator for brand identity, and the Schema.org Types Reference for the full type catalogue.

Frequently asked questions

Where exactly should JSON-LD go in my HTML?

Inside <head> is most common, but anywhere in <body> works too. Google parses the final rendered HTML, so JSON-LD injected by JavaScript is detected as well.

Can I use multiple schemas on one page?

Yes. A product detail page commonly has Product + BreadcrumbList + FAQPage at once. Put each in its own <script type="application/ld+json"> block, or combine them in a single block using the @graph array.

Will rich results appear immediately after adding structured data?

No. Google treats structured data as a signal, not a guarantee. Actual display depends on page quality, authority, competition, and whether Google still supports that visual feature. Retired features, such as the SearchAction sitelinks search box and FAQ rich results, may validate without appearing visually.

Will invalid JSON-LD hurt my SEO?

Syntax errors are simply ignored, so there's no direct penalty. However, using fake reviews or irrelevant structured data to mislead users violates Google's spam policies and can trigger manual actions.