⌘ K
json-ld · schema.org · seo · rich results

Build JSON-LD for any schema

Generate schema.org structured data for Article, Product, FAQ, Recipe, Event, Organization, Person and Breadcrumbs. Ready-to-paste script tag.

Structured Data Generator
Schema
Article
type
Fields
6
configured
Bytes
371
json-ld
Status
ready
live
Schema
input · fields
output · json-ld
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Hello World",
  "image": [
    "https://example.com/hero.jpg"
  ],
  "author": {
    "@type": "Person",
    "name": "Jane Doe"
  },
  "publisher": {
    "@type": "Organization",
    "name": "Example Co"
  },
  "datePublished": "2026-01-15",
  "description": "A short article about hello world."
}
Quick Start

How to add structured data

Drop a JSON-LD script in <head> (or anywhere in the body) and search engines will use it for rich results.

  1. 01

    Pick a schema

    Article, Product, FAQ, Recipe, Event, Org, Person, or Breadcrumbs.

    Lookups reference the IANA registries (MIME, HTTP status, TLDs) bundled at build time — no live network calls, no rate limits, no leaked queries.

    schemaIANAregistryofflinelive
    type · queryArticle · IANA
    @type: Article
    loaded · IANA bundlespec · ready
  2. 02

    Fill the fields

    Only required fields matter for eligibility — the rest enrich the result.

    Builders emit canonical syntax per the relevant RFC (9110 for HTTP, 5322 for headers, 3986 for URLs) so the output passes spec-compliant parsers.

    fieldsRFC 9110canonicalspec-compliantlive
    fields · options6 · live
    headline · image · author
    options applied · livecanonical
  3. 03

    Copy the script

    One click gives you a complete <script type="application/ld+json"> tag.

    Validation flags common pitfalls — uppercase header names, smart quotes inside Content-Type, missing ;charset=utf-8 — before they bite production.

    copyvalidationlintpitfallslive
    out · looked up<script> · ready
    <script>...</script>
    result · livevalidated
  4. 04

    Validate

    Paste into Google's Rich Results Test to confirm it parses.

    Copy writes the snippet directly into your clipboard; downloads emit the right extension and MIME so curl/httpie pick them up correctly.

    validateclipboardMIME-correctblobcurl-ready
    ok · copiedvalid · done
    Rich Results Test
    shipped · ready to shipsuccess
Pro tips

Web-spec details that bite later

Idempotency saves retries

POST/PUT/DELETE should be safely retried. Use idempotency keys and return the same response on duplicate requests.

Match RFC 9110 status codes

Don’t invent codes. 422 for validation errors, 409 for conflicts, 429 for rate limits. Standard codes work with off-the-shelf clients.

Set <code>Cache-Control</code> deliberately

Default browser caching is conservative. Use max-age + stale-while-revalidate for hot endpoints.

Validate Open Graph in dev

OG tags break silently. Use a previewer like OG Generator + Facebook’s debugger before launch.

CORS is a server concern

The browser sends the preflight; the server decides. Wildcard origins disable credentials — be explicit.

MIME drives behaviour

Servers must send the right Content-Type. Browsers sniff but the spec says they shouldn’t — be explicit to avoid surprises.

Related toolsMeta TagsOpen GraphTwitter CardCanonical URLHreflangSitemap
Use Cases

When to use JSON-LD

Rich results, knowledge panels, voice search.

Article rich results

Headlines, hero images and dates in Google Search. Bundled from IANA registries at build time — no live network call, no rate limit, no leaked queries. The MIME, TLD, and status-code tables are baked in so the tool works offline once loaded.

spec-compliant

Product cards

Price, availability and ratings in shopping results. Output is canonical per the relevant RFC (9110 for HTTP, 5322 for headers, 3986 for URLs), so spec-compliant parsers accept it as-is. Cross-browser and cross-library behaviour stays consistent.

offline

FAQ rich snippet

Expandable Q&A panel right in the SERP. Pairs with the curl-to-fetch converter for end-to-end test stubs — copy the curl from DevTools, paste, get an idiomatic fetch() body. Drop into Playwright/Vitest fixtures without manual translation.

IANA-backed

Recipe cards

Cook time, image and ratings in Google recipes. Catches common pitfalls (uppercase header names, smart quotes inside Content-Type, missing ;charset=utf-8) before they bite production. Validation flags rather than auto-corrects so you stay in control.

RFC-aligned

Event details

Dates and venue info in Google events. Validation runs as you type — copy only when the output is shaped correctly. The output drops directly into nginx, Apache, or CDN configs without re-formatting or re-quoting.

production-grade

Voice search

Assistants prefer structured data for spoken answers. Same input plus same options always produces identical canonical output, so the tool is safe to embed in CI scripts that diff against expected configs.

curl-ready
FAQ

Frequently asked questions

Inside <head> or anywhere in <body>. Google parses JSON-LD anywhere in the document.
No — only required fields are mandatory for eligibility. Optional fields enrich the appearance.
Yes — drop multiple <script type="application/ld+json"> blocks, one per entity.
Use Google's Rich Results Test or the Schema.org validator. Both accept pasted JSON-LD.
Yes. JSON-LD is generated entirely in your browser.
Suggest a tool

Something missing?

Tell us what you need. We ship the top requests every two weeks.

Sent straight to the maintainers · no account needed
47 in queue·8 shipped this month
Request queued. Thanks!