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 supports common schema types including Article, Product, FAQ, HowTo, LocalBusiness, Event, Recipe, and Organization — enabling rich results and enhanced search listings in Google.
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: the Canonical Tag Generator to add a canonical tag alongside the structured-data block; and the Internal Link Visualizer to confirm your structured-data pages aren't orphaned in the internal link graph.
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.
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 over 800 types, but Google only renders rich results for about 30 of them, and that list shrinks over time. As of 2026, HowTo rich results are fully deprecated (removed from search in September 2023) — the markup is still valid JSON-LD and still useful as machine-readable context for AI engines, but it will not show a rich result on Google. FAQPage rich results were also restricted in 2023 and now appear almost exclusively for government and health sites. Product, Recipe, Event, Article, LocalBusiness, Review, Video, BreadcrumbList, and Course remain fully supported for eligible content. This tool shows an eligibility badge on every type so you know exactly what you are getting.
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 developer documentation for each structured data type distinguishes two tiers. Required properties are the ones Google needs to render a rich result at all — leave them out and the rich result is ineligible. Recommended properties improve the rich result quality and the likelihood that Google chooses to display it when the page is competing with others for the same query. For Product, name and offers are required; brand, aggregateRating, and review are recommended. This tool surfaces the required fields at the top of each form with a red asterisk and validates them live so you know the moment your markup is eligible.
Is the markup I generate here safe to paste into production?+
Yes, with one caveat that applies to any schema generator. The JSON-LD produced here is valid against schema.org and Google's requirements as of April 2026. The caveat is Google's policy rule that your markup must represent content that is visible on the page. If you declare a Product price of $49.99 in JSON-LD but the page shows $59.99, your markup is syntactically valid but violates policy and can trigger a manual action. Always keep the two in sync, especially on CMS-driven sites where prices and inventory update asynchronously. For one-off pages this is trivial; for large catalogs, drive the JSON-LD from the same data source as the visible HTML.
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?+
The most common types are covered: Article, BlogPosting, NewsArticle, Product (with offers and reviews), Recipe, Event, LocalBusiness, Organization, Person, FAQPage, HowTo, BreadcrumbList, VideoObject, WebApplication, and Course. Each type has its required and recommended properties exposed as form fields. For less common types (Vehicle, RealEstateListing, SoftwareApplication subtypes), the JSON output is editable so you can add custom properties after generation.
Should I use JSON-LD or microdata?+
JSON-LD. Google explicitly recommends JSON-LD over microdata and RDFa because it sits in a separate script block, does not interfere with page rendering, and is easier to maintain. Microdata (data-* attributes scattered through HTML) is the older standard and still works, but new schema implementations should be JSON-LD. The generator emits JSON-LD by default; microdata output is available for legacy migrations.
Built by Derek Giordano · Part of Ultimate Design Tools
Privacy Policy · Terms of Service