What Is Schema Markup Generator?
Schema Markup Generator creates structured data (JSON-LD) for your web pages to help search engines understand your content. It covers 13 types, among them Article, Product, Recipe, Event, LocalBusiness and Organization, and labels which ones can still earn a Google rich result (FAQ and HowTo no longer can).
How to Use This Tool
Select a schema type, fill in the required and recommended fields (name, description, image, dates, ratings, etc.), and the tool generates valid JSON-LD markup. Preview how the rich result might appear in Google search, then copy the script tag to paste into your page’s HTML head. Everything runs in your browser.
Why Use Schema Markup Generator?
Writing JSON-LD by hand is tedious and a single syntax error can invalidate the entire block. This tool generates schema markup with proper nesting, correct property types, and valid formatting — reducing the risk of errors that prevent your pages from earning rich results. It’s free, instant, and requires no technical background. For a detailed walkthrough, see our step-by-step guide.
See also: once you have generated schema, run it through the Rich Results Tester to confirm Google rich-result eligibility under 2026 rules, and the Schema Validator for a pure Schema.org structural check independent of Google's policies.
Related tools
Frequently Asked Questions
What is JSON-LD and why does Google prefer it?+
JSON-LD (JSON for Linking Data) is a structured-data format that lives in a script tag in your page head, completely separate from the visible HTML. Google explicitly recommends it over Microdata and RDFa because it is easier to maintain, does not force you to interleave markup with content, and works cleanly with any rendering pipeline including React, Next.js, and static site generators. A page can have multiple JSON-LD blocks — one for the Article, one for the BreadcrumbList, one for the Organization — and Google reads them all.
Do all schema types trigger rich results?+
No. Schema.org defines hundreds of types, and Google shows rich results for a small set listed in its Search Gallery, a list that keeps shrinking. HowTo rich results ended in September 2023, Course Info and six other features were retired in June 2025, and FAQ rich results ended for all sites on May 7, 2026. The markup for those types is still valid Schema.org and other consumers can read it; the tool labels each type RICH, LIMITED, DEPRECATED or DATA so you know what to expect.
What is the difference between Schema.org and Google Rich Results?+
Schema.org is the vocabulary — the canonical list of types, properties, and their relationships, maintained jointly by Google, Microsoft, Yahoo, and Yandex. Google Rich Results is one consumer of that vocabulary: the subset of schema types that Google renders as enhanced listings in its search results. Schema.org has two validators worth knowing. The Schema Markup Validator at validator.schema.org checks your JSON-LD against the full schema.org vocabulary regardless of whether Google renders it. The Google Rich Results Test at search.google.com/test/rich-results checks only whether your markup qualifies for a Google rich result. Use both: Schema Markup Validator tells you the markup is technically correct, Rich Results Test tells you Google will do something visible with it.
Why does this tool mark some fields as 'required' and others as 'recommended'?+
Google's documentation for each rich result type splits properties into required (leave one out and the page is not eligible) and recommended (more complete results). For Product snippets, name is required plus at least one of review, aggregateRating or offers; brand, sku and gtin are recommended. The tool puts required fields first in each form.
Is the markup I generate here safe to paste into production?+
Structurally, yes: the default output of all 13 types was checked against the current schema.org vocabulary (every type and property exists and is allowed on its parent type), and any < in your text is escaped so a value cannot close the script tag early. Google's policy still applies: the markup must describe content visible on the page, so a JSON-LD price of $49.99 on a page showing $59.99 is a policy violation even though it parses. Run Google's Rich Results Test on the live page before relying on a rich result.
Does this tool send my data anywhere?+
No. Every field you type stays in your browser. The JSON-LD is assembled entirely in JavaScript on your machine and rendered into the output pane in real time. Nothing is uploaded, logged, or transmitted by this site. The two external-tool buttons next to the Copy button are plain links that open Google's Rich Results Test and the Schema.org Validator in a new tab — neither tool receives your markup from us. The normal workflow is to click Copy, click Open, then paste into the validator's Code field. That ordering is deliberate: Safari and some strict-mode browsers will not allow a single click to both copy to the clipboard and open a popup tab, so we keep the two actions separate and reliable.
Which schema.org types does the generator support?+
Thirteen: Article, Product (with offers and ratings), FAQPage, Recipe, Event, LocalBusiness, Organization, Person, BreadcrumbList, VideoObject, Review, Course and HowTo. For anything else, copy the output and edit it by hand; the output pane itself is read-only.
Should I use JSON-LD or microdata?+
JSON-LD. Google recommends it because it sits in its own script block instead of being woven into the HTML. Microdata uses itemscope, itemtype and itemprop attributes on your visible elements and still works, but it is harder to maintain. This tool outputs JSON-LD only.
Built by Derek Giordano · Part of Ultimate Design Tools
Privacy Policy · Terms of Service