Try it

Schema type

Name / headline

URL

Description (optional)

Image URL (optional)

datePublished (optional, for Article)

Breadcrumb items (optional, Label|URL per line)

FAQ items (optional, Question|Answer per line)

Or drop a .json file here.

JSON-LD: { "@context": "https://schema.org", "@type": "WebSite", "name": "Gampangin", "url": "https://gampangin.example/", "description": "Browser-local developer tools." }
Missing required: none
Eligibility: Eligible for sitelinks search box when the site has a working search.
Findings: INFO: Generated a valid WebSite node.

{
  "@context": "https://schema.org",
  "@type": "WebSite",
  "name": "Gampangin",
  "url": "https://gampangin.example/",
  "description": "Browser-local developer tools."
}

Supported formats

Input: text, url
Output: json

Privacy

Runs entirely in your browser. Your input is never uploaded, stored, or sent to a third party.

Processing: In your browser
Privacy level: Browser only

Generated valid WebSite JSON-LD.

How it works

Looked up the required properties for the chosen schema type.
Built the node with @context https://schema.org and @type.
Reported each missing required property and the current eligibility note.

Rich results are not guaranteed; eligibility rules change and this tool states them as of its sources.

Methodology

Look up the chosen type's required properties and eligibility note.
Build a schema.org node with the supplied values, expanding breadcrumb and FAQ inputs into the correct nested lists.
Report missing required properties and the eligibility note without claiming a guaranteed result.

Usage

Choose a schema type.
Fill in the name and absolute URL.
Add the optional description, image, date, breadcrumb items or FAQ items the type needs.
Generate and copy the JSON-LD into a script tag.

Examples

These are examples, not current values: they use fixed inputs, while the interactive tool computes live results in your browser.

A WebSite node

{
  "type": "WebSite",
  "name": "Gampangin",
  "url": "https://gampangin.example/",
  "description": "Browser-local developer tools."
}

A BreadcrumbList node

{
  "type": "BreadcrumbList",
  "name": "Breadcrumb",
  "url": "https://gampangin.example/tools/json-formatter/",
  "breadcrumb": "Home|https://gampangin.example/\nTools|https://gampangin.example/tools/\nJSON Formatter|https://gampangin.example/tools/json-formatter/"
}

Example result

{ "json": "{\n \"@context\": \"https://schema.org\",\n \"@type\": \"BreadcrumbList\",\n \"itemListElement\": [\n {\n \"@type\": \"ListItem\",\n \"position\": 1,\n \"name\": \"Home\",\n \"item\": \"https://gampangin.example/\"\n },\n {\n \"@type\": \"ListItem\",\n \"position\": 2,\n \"name\": \"Tools\",\n \"item\": \"https://gampangin.example/tools/\"\n },\n {\n \"@type\": \"ListItem\",\n \"position\": 3,\n \"name\": \"JSON Formatter\",\n \"item\": \"https://gampangin.example/tools/json-formatter/\"\n }\n ],\n \"url\": \"https://gampangin.example/tools/json-formatter/\"\n}", "node": { "@context": "https://schema.org", "@type": "BreadcrumbList", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://gampangin.example/" }, { "@type": "ListItem", "position": 2, "name": "Tools", "item": "https://gampangin.example/tools/" }, { "@type": "ListItem", "position": 3, "name": "JSON Formatter", "item": "https://gampangin.example/tools/json-formatter/" } ], "url": "https://gampangin.example/tools/json-formatter/" }, "missing": [], "eligibility": "Eligible for the breadcrumb rich result when the trail matches the page.", "findings": [ { "severity": "info", "field": "type", "message": "Generated a valid BreadcrumbList node." } ] }

An Article node with a missing date

{
  "type": "Article",
  "name": "How canonical URLs work",
  "url": "https://gampangin.example/articles/canonical-urls/",
  "image": "https://gampangin.example/img/canonical-cover.png"
}

Example result

{ "json": "{\n \"@context\": \"https://schema.org\",\n \"@type\": \"Article\",\n \"headline\": \"How canonical URLs work\",\n \"image\": \"https://gampangin.example/img/canonical-cover.png\",\n \"url\": \"https://gampangin.example/articles/canonical-urls/\"\n}", "node": { "@context": "https://schema.org", "@type": "Article", "headline": "How canonical URLs work", "image": "https://gampangin.example/img/canonical-cover.png", "url": "https://gampangin.example/articles/canonical-urls/" }, "missing": [ "datePublished" ], "eligibility": "Eligible for article rich results; author and publisher are recommended.", "findings": [ { "severity": "error", "field": "datePublished", "message": "Missing required property \"datePublished\" for Article." } ] }

Limitations

Structured data, honestly

Structured data describes a page so search engines can understand it. It makes the page eligible for a rich result; it never guarantees one.

Only mark up information that is visible on the page. Never add ratings, prices, FAQs or dates the page does not actually show.

Frequently asked questions

Will structured data always produce a rich result?: No. Structured data makes a page eligible; Google may still choose not to show a rich result, and some types (FAQPage) are limited to a small set of sites.
Which types are offered?: WebSite, WebPage, BreadcrumbList, Article, SoftwareApplication, Organization, LocalBusiness, Product and FAQPage, each with its current required properties.

Sources

Schema.org — Vocabulary — Schema.org
Google Search Central — Structured data search gallery — Google Search Central

Send feedback

Tell us if this tool helped, report a problem, or suggest a tool. Only the message you type is sent — never the input you used in the tool.

Was this tool useful?

Prefer to write to us directly? See the contact page.