Schema Markup Generator (JSON-LD)

Q: Why are some slashes written as <\/ in the output?

A closing script tag that appears inside your text (for example in an FAQ answer) would end the JSON-LD block early and break it. The generator therefore writes every less-than sign followed by a slash as <\/. That is a standard JSON escape, so Google and any JSON parser read exactly the same text.

Pick a schema type, fill in the form and copy valid JSON-LD ready to paste into your page. A live checklist compares your markup with Google Search Central's required and recommended properties and flags bad dates, URLs and prices. Everything is generated on this page; nothing you type is uploaded.

Runs locally — nothing you enter is sent SEO Free · no signup

How to use

Choose a schema type: Article, FAQ page, Organization, Local business, Product, Breadcrumbs, Event, Person or WebSite.
Fill in the form, or click Load example to see a complete one. Use Add buttons for extra questions, breadcrumb items, images, profiles and opening hours.
Work through the Google checklist: ✗ marks properties Google requires, ⚠ marks values to fix (dates, URLs, prices) and ○ marks recommended properties.
Copy the <script type="application/ld+json"> block into your page, or download the JSON.
Test the live page with Google's Rich Results Test and the Schema.org validator before relying on it.

Examples

Type

BreadcrumbList with Home › Books › Science fiction

JSON-LD

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://example.com/" },
    { "@type": "ListItem", "position": 2, "name": "Books", "item": "https://example.com/books" },
    { "@type": "ListItem", "position": 3, "name": "Science fiction" }
  ]
}
</script>

Supported formats

Output: JSON-LD wrapped in a <script type="application/ld+json"> tag, or plain .json when downloaded.
Types: Article, NewsArticle, BlogPosting, FAQPage, Organization (and subtypes), LocalBusiness (and common subtypes such as Restaurant or Dentist), Product with Offer and AggregateRating, BreadcrumbList, Event, Person and WebSite.
Dates in ISO 8601 (2026-10-09 or 2026-10-09T19:00:00+01:00); URLs must be absolute http(s) addresses.

Privacy

This tool runs entirely in your browser. Nothing you enter or open is sent anywhere. Privacy policy.

Limitations

The checklist follows Google Search Central's documentation for each type as of 2026, but Google changes its requirements; the Rich Results Test is the final word.
Valid markup does not guarantee a rich result. Since August 2023, FAQ rich results only appear for well-known government and health websites, and HowTo rich results are no longer shown, so HowTo is not offered.
It builds one item per block: no nested reviews, multiple offers, product variants, merchant return policies or event series. Combine blocks by hand if you need them.
It cannot check that the markup matches what is visible on your page — that is up to you, and Google requires it.

FAQ

Where do I put the generated JSON-LD?

Paste the whole <script type="application/ld+json"> block into the HTML of the page it describes, either in the <head> or the <body>. Google reads JSON-LD added by JavaScript as well, but markup in the server-rendered HTML is the most reliable.

Will FAQ markup give me FAQ rich results?

Probably not. Since August 2023 Google shows FAQ rich results only for well-known, authoritative government and health websites. FAQPage markup is still valid Schema.org, but most sites should not expect the expandable questions in search results.

What is the difference between required and recommended properties?

Google only considers a page for a rich result if every required property is present and valid. Recommended properties are optional, but adding the ones that apply gives Google more to show and can improve how the result looks.

Why are some slashes written as <\/ in the output?