Processing locally — files never leave your device

JSON-LD Schema Generator

Generate JSON-LD structured data for Article, FAQPage, BreadcrumbList, Product, LocalBusiness, and Organization. Paste straight into your HTML.

Headline

Author

Date published (YYYY-MM-DD)

Image URL

Article URL

JSON-LD output

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "My great post",
  "image": [
    "https://example.com/og.png"
  ],
  "datePublished": "2026-06-21",
  "author": {
    "@type": "Person",
    "name": "Jane Doe"
  },
  "mainEntityOfPage": {
    "@type": "WebPage",
    "@id": "https://example.com/post"
  }
}
</script>

How to use Schema Generator

Pick the schema.org type that matches your page — Article, FAQPage, Product, LocalBusiness, BreadcrumbList, or Organization.
Fill in the fields, making sure every value exactly matches what is visible on the page.
Copy the generated JSON-LD <script type="application/ld+json"> block.
Paste it into your page — inside <head> is conventional, but anywhere in the HTML works.
Validate the result in Google's Rich Results Test and the Schema.org validator before shipping.

Structured data: help search engines understand your page

Structured data is machine-readable markup, based on the shared schema.org vocabulary, that describes what a page is about — that this is a product with a price, an article by an author, or a business with an address and opening hours. Search engines use it to power rich results. This generator outputs valid JSON-LD, the format Google recommends, for the most common types.

What JSON-LD looks like

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "How to Add Structured Data",
  "author": { "@type": "Person", "name": "Jane Doe" },
  "datePublished": "2026-01-15",
  "image": "https://example.com/cover.png"
}
</script>

The @context points to the schema.org vocabulary and @type declares what the thing is. Everything else is properties of that type.

Why JSON-LD beats Microdata and RDFa

The same information can be expressed three ways. Microdata and RDFa interleave attributes throughout your visible HTML, which is fragile and hard to maintain. JSON-LD keeps all the structured data in one self-contained script block, decoupled from your markup. That makes it easy to generate dynamically, easy to validate, and easy to keep in sync — which is why Google explicitly prefers it.

Common types and the rich results they unlock

Article / BlogPosting — eligibility for top-stories and article cards
Product — price, availability, and review stars in results
FAQPage — expandable question-and-answer snippets
BreadcrumbList — a breadcrumb trail in place of the raw URL
LocalBusiness — address, hours, and map presence
Organization — brand knowledge-panel and logo signals

The golden rule: match the visible page

Google requires that your structured data describes content users can actually see on the page. Do not mark up a 5-star rating that appears nowhere, prices that differ from the listed price, or FAQs that are not on the page. Mismatches are a guidelines violation that can cost you rich results entirely and, in serious cases, trigger a manual penalty.

Always validate before shipping

Structured data is unforgiving of typos. A misspelled property or wrong nesting silently disqualifies the rich result. Run every block through Google's Rich Results Test to confirm eligibility and through the schema.org validator to confirm syntax. After deploying, watch the Enhancements reports in Search Console for any errors Google detects on live pages.

Related SEO tools

Meta Tag Generator — pair structured data with an optimised title, description, and social tags.
JSON Formatter & Validator — pretty-print and validate your JSON-LD before pasting.
XML Sitemap Generator — make sure the pages with schema are discoverable.
Canonical Tag Generator — keep structured-data pages canonicalised correctly.

Frequently asked questions

What is JSON-LD and why is it preferred?

JSON-LD (JSON for Linking Data) embeds structured data in a single <script type="application/ld+json"> block, separate from your visible HTML. Google recommends it over Microdata and RDFa because it is easier to add, maintain, and inject dynamically without touching your markup.

Where do I paste the JSON-LD?

Anywhere in the HTML document. Placing it in the <head> is conventional and keeps it tidy, but Google parses it correctly whether it is in the head or body. You can include multiple JSON-LD blocks on one page for different types.

Does structured data improve my rankings?

Not as a direct ranking factor. What it does is make your page eligible for rich results — star ratings, FAQ accordions, breadcrumb trails, recipe cards — which increase visibility and click-through. The downstream traffic can help, but the markup itself is not a ranking boost.

How do I validate my schema?

Use two tools. Google's Rich Results Test (search.google.com/test/rich-results) checks eligibility for Google-specific rich results. The Schema.org validator (validator.schema.org) checks general syntactic validity against the vocabulary. Run both.

Must the structured data match the visible page?

Yes. This is a strict Google guideline. The data you mark up must represent content actually visible to users on that page. Marking up information that is hidden, absent, or different from what users see is a violation that can trigger a manual action.

What schema type should I use for an FAQ?

Use FAQPage, with each question as a Question entity and its answer as an acceptedAnswer. Note that Google now restricts FAQ rich results mainly to authoritative government and health sites, so the visual snippet may not show — but the markup still helps machines understand your content.

Can one page have multiple schema types?

Yes, and it is common. A blog post might carry Article, BreadcrumbList, and Organization markup together. You can nest them in a single @graph array or emit separate script blocks; both are valid.

What are required vs recommended properties?

Each type has properties Google requires for rich-result eligibility and others it merely recommends. A Product needs a name and an offers or review/aggregateRating to show price or stars. The Rich Results Test flags any missing required field, so let it guide you.

More tools you might find useful in the same flow.

Meta Tag Generator

Meta tag generator — build complete SEO title, description, robots, and canonical tags for any page, ready to copy and paste. Free, with no signup needed.

robots.txt Generator

robots.txt generator — build a clean robots.txt file with user-agent rules, allow and disallow paths, and sitemap entries in seconds. Free, no signup needed.

Sitemap Generator

Free online XML sitemap generator: paste your URLs and build a valid sitemap.xml with lastmod, changefreq, and priority. Copy or download — no signup.

Open Graph Preview

Open Graph preview tool — see exactly how a URL will look when shared on Facebook, LinkedIn, and other social platforms before you publish. Free and instant.

See all SEO & Web Tools

Built by Muhammad Tahir · About