Schema Markup Generator

How to use it

1. Pick the type you are describing — Article, BlogPosting, Product, FAQPage, BreadcrumbList, LocalBusiness, Organization or Person.
2. Fill the fields; required ones carry a badge, and repeatable rows add questions, crumbs or offers one at a time.
3. Read the output card: the block updates as you type, with anything missing or rejected named beside it.
4. Copy the block, copy the JSON alone, download it, or share the form as a link.

Choose one of eight schema.org types, fill the labelled fields, and the matching JSON-LD script block assembles as you type — nested authors, offers and questions included. Required fields are checked before anything is emitted, and every value is escaped so the block cannot break the page it lands in. Paste an existing block back in to edit it.

How it works

JSON-LD is metadata, not markup you can see: the block sits in a <script type="application/ld+json"> element and renders nothing. @context names the vocabulary — always https://schema.org here — and @type names the thing described, with nested objects carrying their own @type. Key order is fixed, so the same form emits the same bytes.

Required here means required by this tool for a coherent document, not a schema.org obligation and not a promise about any search feature. The checks are structural and local: absolute URLs, ISO 8601 dates, decimal prices, enumeration members. Search engines read the block; what they show for it is their call.

Examples

Organization — the default document

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Northwind Coffee",
  "url": "https://example.com",
  "logo": "https://example.com/logo.png",
  "sameAs": "https://example.com/about",
  "contactPoint": {
    "@type": "ContactPoint",
    "telephone": "+31 20 555 0100",
    "contactType": "customer service"
  },
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "1 Example Street",
    "addressLocality": "Amsterdam",
    "addressRegion": "North Holland",
    "postalCode": "1011 AB",
    "addressCountry": "NL"
  }
}
</script>

Product with an offer and rating

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Ridgeline Pour-Over Kettle",
  "image": "https://ridgeline.example/kettle.jpg",
  "sku": "RL-KTL-900",
  "brand": {
    "@type": "Brand",
    "name": "Ridgeline"
  },
  "offers": {
    "@type": "Offer",
    "price": "49.99",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock",
    "url": "https://ridgeline.example/kettle",
    "priceValidUntil": "2026-12-31"
  },
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "4.6",
    "reviewCount": "218",
    "bestRating": "5",
    "worstRating": "1"
  }
}
</script>

FAQPage with a </script> in an answer

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Can an answer contain HTML?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "It can. A phrase like <\/script> is escaped on emit, so it cannot close the block early."
      }
    }
  ]
}
</script>

BreadcrumbList — three crumbs, hand-typed positions

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    {
      "@type": "ListItem",
      "position": 1,
      "name": "Home",
      "item": "https://ridgeline.example/"
    },
    {
      "@type": "ListItem",
      "position": 2,
      "name": "Brewing gear",
      "item": "https://ridgeline.example/gear"
    },
    {
      "@type": "ListItem",
      "position": 3,
      "name": "Pour-over kettle"
    }
  ]
}
</script>

Every example on this page is executed against the same engine that powers the tool, on every build.

Common errors

headline is required by this tool and is empty.

Nothing is emitted while a badged field is blank, and the message names the property rather than the input box.

url "/about" is not an absolute URL. Use an absolute http:// or https:// URL — schema.org values are resolved as-is, not against the page they sit on.

A site-root path resolves against whatever page the consumer is reading, which is rarely yours. javascript: and data: are refused on the same field.

datePublished "2026-08-12T09:30:00" has a time but no UTC offset, so the moment it names is ambiguous. Write a calendar date as YYYY-MM-DD (2026-08-12) or a full date-time with a UTC offset (2026-08-12T09:30:00+02:00).

The check walks the calendar, so 2026-02-30 and 2026-13-45 fail as dates, and 03/04/2026 fails because nobody can tell March from April.

offers.price "$49.99" is not a decimal string. Write digits only, with a dot for the fraction and no currency symbol, no thousands separator and no comma decimal: 49.99, not $49.99 or 49,99.

The currency lives in priceCurrency, so a symbol here is duplicate information consumers have to strip.

Input is larger than the 256 KB limit for this tool. Nothing was truncated. For a document this size, read its type on the command line instead: python3 -c "import json,sys;d=json.load(open(sys.argv[1]));print(d['@type'])" schema.json

A half-read document emits a block that looks finished and is not, so the tool stops instead of trimming. A paste that large is usually a whole page source.

Keyboard shortcuts

⌘/Ctrl + Enter

Re-emit the block from the current fields.

⌘/Ctrl + S

Download the document as .json.

⌘/Ctrl + C

Copy the script block while nothing is selected.

⌘/Ctrl + Shift + C

Copy the script block even over a selection.

t

Cycle the color theme.

? or ⌘/Ctrl + /

Open the shortcut help dialog.

Esc

Close the topmost dialog.