PK Systems PK Systems
Web & marketing

JSON-LD Schema Builder

Build valid <code>application/ld+json</code> blocks for Article, Product, FAQPage, Recipe, Event, Organization and LocalBusiness — copy and paste into your <code>&lt;head&gt;</code>.

JSON-LD Schema Builder

Pick the type that matches the page's primary content. Most pages need only one block.

JSON-LD output

What is JSON-LD?

JSON-LD (JSON for Linking Data) is the format Google, Bing and most other search engines prefer for structured data. You drop a <script type="application/ld+json"> block in the page <head> with a JSON object describing the page — and the crawler uses that to enable rich results: review stars, FAQ accordions, recipe cards, event listings. The vocabulary comes from Schema.org, a community-maintained ontology of around 800 types and 1,400 properties.

How to use this builder

Pick the schema type that matches your page's primary content. Most pages need exactly one block — an article page is an Article, a product page is a Product, an event page is an Event. Fill in the required fields (marked in the reference table below); optional fields are there if you have the data, but skipping them is fine. The output panel updates live and reformats the JSON. When the structure looks right, click Copy JSON-LD and paste the snippet — including the <script> tags — into your page's <head>. Validate with Google's Rich Results Test before shipping.

JSON-LD vs Microdata vs RDFa

Schema.org markup can be expressed in three syntaxes: Microdata (inline itemscope / itemprop attributes on visible elements), RDFa (similar idea, different attribute names), and JSON-LD (a self-contained JSON block in <head>). Google has officially recommended JSON-LD since 2015 because it decouples the markup from the visible HTML — content teams can edit the page without breaking the schema, and structured data can be added without restructuring templates. Unless you're maintaining a legacy site, JSON-LD is the right default.

When to use each type

Type Best for Key required fields
ArticleNews stories, blog posts, long-form essays.headline, author, datePublished, image
ProductE-commerce product pages — physical or digital goods with a price.name, image, offers
FAQPagePages whose primary content is a list of questions and answers.mainEntity[].name, acceptedAnswer.text
LocalBusinessA specific physical business location with address and hours.name, address, telephone
OrganizationThe home page of a company, charity or institution.name, url, logo
RecipeCooking recipes with ingredients, steps and times.name, image, recipeIngredient, recipeInstructions
EventConcerts, conferences, webinars, classes — anything with a start time and venue.name, startDate, location

Frequently asked questions

Will this guarantee a rich result in Google?
No. Valid JSON-LD makes the page eligible, but Google still chooses whether to show the rich result based on quality signals, query intent and category-specific guidelines. Many pages with perfect markup show no enhancements. Treat JSON-LD as a prerequisite, not a guarantee.
Where do I paste the output?
Inside the page's <head> (or just before </body> — both work). Keep the <script type="application/ld+json"> wrapper; the crawler looks for that exact MIME type. One block per type per page is plenty.
Can I have multiple JSON-LD blocks on a page?
Yes. A common pattern is one block for Organization on every page, plus a page-specific block for Article, Product or Event. Google merges them into a single graph as long as the JSON itself is valid in each block.
How do I validate the output?
Paste the snippet into Google's Rich Results Test for the consumer view, and into the Schema.org validator for a stricter, vendor-neutral check. Both tools accept either a URL or a code snippet directly.
What date format should I use?
ISO 8601, always. Dates: 2026-05-04. Datetimes with time zone: 2026-05-04T19:00-03:00. Durations: PT45M for 45 minutes, PT1H30M for 90 minutes. Search engines reject anything that doesn't parse as 8601.
Does this tool send my data to a server?
No. The form, the JSON serialisation and the validation all run in your browser. Nothing is uploaded — you can build schema for unpublished pages, internal tools or stealth products without leaking the contents.