Schema Markup Generator
Generate valid JSON-LD schema markup for Article, Product, Organization, LocalBusiness, BreadcrumbList, FAQPage, Event, Recipe, VideoObject, WebSite, and WebPage: Rich Results-ready.
Interactive tool
Fields
JSON-LD output
LiveWhat is the Schema Markup Generator?
A free Schema.org JSON-LD generator covering the 11 most-used Rich Results types: Article, Product, Organization, LocalBusiness, BreadcrumbList, FAQPage, Event, Recipe, VideoObject, WebSite, and WebPage. Pick a type, fill in a few fields, and get production-ready JSON-LD you can drop into your <head> as a <script type="application/ld+json"> block.
How to Use the Schema Generator
- 1Pick a schema type from the dropdown
- 2Fill in the required fields (marked with *)
- 3Optionally fill in recommended fields for full Rich Results eligibility
- 4Watch the JSON-LD output update live on the right
- 5Click "Copy" or expand the script-tag block and paste it into your page <head>
- 6Verify in Google Search Console > Rich Results Test once deployed
Key features
11 Rich Results types
Article, Product, Organization, LocalBusiness, BreadcrumbList, FAQPage, Event, Recipe, VideoObject, WebSite, WebPage
Required and recommended hints
Inline reminders for fields Google wants present for full Rich Results eligibility
Drop-in script tag
One-click copy of either the raw JSON-LD or a ready-to-paste <script> block
Smart sample data
Each type has a curated example to seed the form so you can see the structure instantly
No empty fields in output
Optional fields you leave blank are omitted from the JSON-LD: no clutter
Nested entities handled
Author, publisher, address, geo, and offer blocks are nested under the correct parent automatically
Keyboard shortcuts
⌘+Enter to copy, ⌘+K to clear the current type
Runs in your browser
No data ever leaves your device: the entire generator is client-side
Why Add Schema Markup?
Schema.org markup tells search engines exactly what your page is about. Pages with valid markup are eligible for Rich Results: review stars, FAQ accordions, breadcrumbs, recipe cards, event listings, and more, which significantly increase click-through rates from search. JSON-LD is the format Google explicitly recommends, and it lives invisibly in your <head> without affecting your visible HTML or rendering performance.
Common use cases
- Adding FAQPage markup to documentation and help center pages
- Tagging blog posts with Article schema for richer search snippets
- Marking up product pages with offer, price, and aggregate rating data
- Listing local business hours, address, and phone for "near me" searches
- Annotating events for Google Events Knowledge Panel inclusion
- Recipe sites earning the recipe card carousel
JSON-LD vs Microdata vs RDFa
JSON-LD is Google's recommended format because it lives in a single <script> tag rather than being interleaved with your visible HTML. Microdata and RDFa are still valid but require sprinkling itemprop attributes throughout your markup, which is harder to maintain and easier to break. Always use JSON-LD for new work.
Required vs recommended fields
- Required: rejected by Google if missing, your page will not be eligible for Rich Results.
- Recommended: still eligible without them, but Google will downgrade or omit features (e.g. an Article without dateModified will not show "Updated" badge).
- This generator marks required fields with a red * and recommended fields with a "recommended" badge.
Validating in production
After deploying, paste your URL into Google's Rich Results Test (search.google.com/test/rich-results). It runs the same parser that powers Google Search and reports any issues. The Schema Markup Validator tool on Zap.Tools (coming in this same Phase 6 batch) gives you the same check without leaving the site.
Tips & best practices
Use absolute URLs everywhere
Image, logo, and URL fields should use full https:// addresses. Relative paths break in some validators.
Match the structure to the visible page
Google penalises markup that contradicts the page (e.g. claiming an aggregate rating that is not visible). Only mark up what users can actually see.
Keep one primary @type per page
You can have multiple JSON-LD blocks (e.g. WebSite + Article on a blog post) but each should describe a distinct entity. Avoid mixing types in a single block.
Date format: ISO 8601
Dates use YYYY-MM-DD; datetimes use YYYY-MM-DDTHH:MM±HH:MM. The form's date inputs already produce the right format.
Test, then deploy, then test again
Validate locally with this tool, deploy, then re-test with Google's Rich Results Test. Live HTML can differ subtly from what the build produced.
Privacy & security
This tool runs entirely in your browser. No field values, output JSON, or analytics are sent anywhere. Close the tab and your work is gone. There is no save state on the server.
Related tools
- XML Sitemap Generator
Build a sitemaps.org-conformant XML sitemap from a URL list. Auto-paginates at 50,000 URLs or 45 MB, generates a wrapping sitemap-index, downloads as a single file or a multi-file ZIP.
SEO Tools
- CSP Generator
Build a Content-Security-Policy with a per-directive visual editor. Outputs the header form and the <meta http-equiv> form, with live evaluation against Google CSP Evaluator heuristics.
SEO Tools
- UTM Builder
Build trackable campaign URLs with UTM parameters for Google Analytics, GA4, and other tracking tools
SEO Tools
- CSP Evaluator
Audit a Content-Security-Policy for unsafe directives, wildcards, missing object-src/base-uri, weak nonces, and other XSS escape hatches. Paste a policy or fetch a URL: get severity-grouped findings with remediation.
SEO Tools
- HTTP Header Checker
Inspect every response header from any URL: security (HSTS, CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy, COOP/COEP/CORP, cookie flags), performance (Cache-Control, ETag, compression), and the full redirect chain.
SEO Tools
- Robots.txt Tester
Test whether a list of URLs are allowed or blocked by a robots.txt file, across multiple user-agents. RFC 9309-compliant matching with rule and line attribution. Paste content or fetch from any domain.
SEO Tools
Frequently Asked Questions
Which schema types are supported?
Article, Product, Organization, LocalBusiness, BreadcrumbList, FAQPage, Event, Recipe, VideoObject, WebSite, and WebPage. Together these cover roughly 95 percent of real-world Google Rich Results usage.
How do I install the generated schema?
Copy the JSON-LD output (or expand the drop-in script tag), then paste it inside the <head> of the page you want to mark up. The tag is invisible to users and does not affect rendering performance.
What is the difference between required and recommended?
Required fields must be present for the page to be eligible for Rich Results. Google rejects markup that omits them. Recommended fields are not strictly required but unlock additional features (a "Last updated" line on Articles, the search box on a WebSite, etc.) and improve match quality.
How do I validate the output?
Paste your URL into Google's Rich Results Test at search.google.com/test/rich-results. Or use the Zap.Tools Schema Markup Validator (coming in this same release) without leaving the site.
Is my data sent to a server?
No. The Schema Markup Generator is fully client-side. Field values never leave your browser, and there is no save state on a server: close the tab and your work is gone.
Can I edit the JSON-LD by hand?
Yes, the output is plain text. Many users tweak the generator output by hand to add fields outside the 11 supported types: go ahead and validate the result with Google's Rich Results Test before deploying.