JSONKit
Web & Standards

JSON-LD Structured Data (Schema.org) JSON Example

A JSON-LD structured data example using Schema.org — an Article with @context, @type, author, and publisher. Copy-ready for SEO rich results and Google structured data.

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Understanding JSON: A Complete Guide",
  "description": "Learn what JSON is, how it works, and where it is used.",
  "image": "https://example.com/images/json-guide.jpg",
  "datePublished": "2025-05-01T08:00:00Z",
  "dateModified": "2025-05-18T10:30:00Z",
  "author": {
    "@type": "Person",
    "name": "Ravi Mehta",
    "url": "https://example.com/authors/ravi"
  },
  "publisher": {
    "@type": "Organization",
    "name": "Example Media",
    "logo": {
      "@type": "ImageObject",
      "url": "https://example.com/logo.png"
    }
  },
  "mainEntityOfPage": {
    "@type": "WebPage",
    "@id": "https://example.com/blog/understanding-json"
  }
}

Field Reference

@contextrequiredstringThe vocabulary URL — almost always 'https://schema.org' for SEO
@typerequiredstringThe Schema.org type, e.g. Article, Product, FAQPage, BreadcrumbList
authoroptionalobjectNested Person or Organization with its own @type
publisheroptionalobjectOrganization that published the content; required for some rich results
mainEntityOfPageoptionalobjectLinks the structured data to the canonical page URL via @id

Variants

Product with offersSchema.org Product markup that can produce price-and-rating rich results.
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Classic Cotton T-Shirt",
  "image": "https://example.com/tshirt.jpg",
  "brand": {
    "@type": "Brand",
    "name": "UrbanThreads"
  },
  "offers": {
    "@type": "Offer",
    "price": "499.00",
    "priceCurrency": "INR",
    "availability": "https://schema.org/InStock"
  },
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "4.5",
    "reviewCount": "382"
  }
}
FAQPageFAQ markup eligible for expandable Q&A in Google results.
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is JSON?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "JSON is a lightweight data-interchange format."
      }
    }
  ]
}

Common Use Cases

  • →Adding rich-result markup to pages for Google Search
  • →Describing articles, products, FAQs, and breadcrumbs for SEO
  • →Publishing machine-readable linked data alongside HTML
json-ldschema.orgstructured dataseorich resultslinked data

Validate or format this JSON

One click loads this exact example into the tool — no copy-paste needed. Format it, validate it, explore the tree, or generate TypeScript types instantly.

FormatValidateExplore treeGenerate TypeScriptMinify

Frequently Asked Questions

Inside a <script type="application/ld+json"> tag, ideally in the <head> or anywhere in the <body>. Unlike microdata, JSON-LD is decoupled from your visible HTML, so it's the format Google recommends and the easiest to maintain.

@context defines the vocabulary (https://schema.org) so terms like 'author' are unambiguous. @type names the kind of thing you're describing (Article, Product, FAQPage). Together they let search engines and other consumers interpret your data.

Use Google's Rich Results Test and the Schema.org validator. They parse your JSON-LD, report errors and missing required fields, and tell you which rich result types your markup is eligible for.

Related JSON Examples

ContentBlog PostBlog post JSON with author, categories, SEO metadata, and publish status fields.E-commerceProduct ListingE-commerce product JSON with pricing, variants, images, and inventory fields.DataHTTP Status CodesReference dataset of 12 HTTP status codes with category, text, and description.