Schema Markup Generator

Generate valid JSON-LD schema markup for 15 types: Article, Product, FAQ, Event, Local Business, Recipe, and more.

Pick a schema type

15 types

Deprecated: HowTo · Q&A Page

Need more page audits per day?

Your current plan (Free) gets up to 50 page audits per day across all our crawl-using tools combined. The form mode is always free regardless of plan.

Upgrade plan
How it works

The Schema Markup Generator builds production-ready JSON-LD structured data for 15 schema types covering content, commerce, business, and other use cases. JSON-LD is the format Google explicitly recommends: a separate <script> block that does not interfere with your visible HTML.

Form mode (free, unmetered for everyone): pick a schema type, fill in the fields, and copy the JSON-LD block. Field-level validation runs live against Google's spec, flagging missing required fields and recommended-but-empty fields as you type. A SERP preview tile renders a rough mock of the rich result your markup would produce.

Extract from URL mode: paste a URL and we fetch the page through our proxy pool, parse the HTML, and pre-fill the form from existing JSON-LD blocks, OpenGraph tags, Twitter cards, standard meta tags, page title, first H1, and canonical URL. Useful for migrating between schema types or auditing what your CMS already emits. Each URL extract consumes 1 unit from your daily page-audit quota (50 per day on the Free plan, shared with every other crawl-using tool).

Validation strip: at the top of the editor, the validation strip shows live counts of filled required and recommended fields. Click any flagged issue to scroll to and focus the offending input.

Live SERP preview: a per-type mock of how the rich result might appear on Google: Article cards, Product star ratings with price, FAQ accordions (with the deprecation note), Recipe tiles with cook time, Event date cards, Job pills, and more. The preview recomputes on every keystroke.

Save and share: click Save and share to persist the draft and get a ?draft=<uuid> URL anyone can open to load the same form state. Drafts expire after 30 days.

Important caveat on FAQ Page and HowTo: Google deprecated the FAQ rich result for most sites in August 2023 and removed HowTo rich results entirely in September 2023. We still expose FAQ Page (with an explicit banner) because the markup still helps AI Overviews and voice-search surfaces. HowTo is excluded.

What each editor section means
Schema type picker
The first decision. 15 types covering Content (Article, BlogPosting, NewsArticle, Recipe, VideoObject, FAQPage, Course), Commerce (Product, Review), Business (Organization, Person, LocalBusiness, Event, JobPosting), and Other (Website, BreadcrumbList, SoftwareApplication).
Sub-type selector
Some schema types (Article, LocalBusiness) have narrower sub-types. Article can be NewsArticle, BlogPosting, or TechArticle. LocalBusiness has dozens of specializations (Restaurant, Hotel, Dentist, etc). Picking a sub-type narrows the spec and gives you more relevant field hints.
Required fields (red border)
Per Google's spec, these fields MUST be present for the rich result to be eligible. Missing any will fail validation in Google's Rich Results Test. We surface them at the top of the form.
Recommended fields (amber border)
Optional in the strict spec but strongly improve the rich result's quality and chances of appearing in search. Filling them is the difference between a bare-bones snippet and a visually-rich one.
Optional fields
Fully optional fields the spec accepts but Google does not require or strongly recommend. Add only if you have the data and it improves the snippet (e.g. aggregateRating with a real review count, award, sameAs).
JSON-LD output panel
The generated JSON-LD updates on every keystroke. Toggle Wrap in <script> to copy a ready-to-paste block, or leave it off to copy the raw JSON for inclusion via your CMS.
SERP preview
A rough mock of the rich result your markup might produce in Google. Useful for sanity-checking that your title, description, image, and ratings would actually look the way you expect. Not pixel-perfect; Google's real rendering varies by device and query.
Frequently asked questions

What is schema markup and why does it matter for SEO?

Schema markup is structured data that helps search engines understand what your content represents (an article, a product, a recipe, an event, a person, a local business, etc). Google, Bing, and other engines use it to power rich results: star ratings under product listings, image carousels for recipes, event date cards, FAQ accordions, and AI Overview citations. The markup itself does not change your page's ranking directly, but the rich features it unlocks can dramatically improve the click-through rate from search results.

How do I add schema markup to my website?

Use this tool to pick a schema type, fill in the fields, and copy the generated JSON-LD block. Then paste it into your page's <head> (or anywhere in the body) wrapped in <script type="application/ld+json">...</script>. Google explicitly recommends JSON-LD over Microdata or RDFa because it sits separately from your visible HTML and is easier to maintain. Most CMS platforms (WordPress, Shopify, Webflow) also have plugins or built-in fields that accept JSON-LD blocks.

What is the difference between JSON-LD, Microdata, and RDFa?

All three are syntaxes for embedding the same Schema.org vocabulary in your page. JSON-LD is a separate <script> block that does not touch your visible HTML; this is Google's recommended format and what this tool generates. Microdata sprinkles itemscope / itemprop attributes on existing HTML elements. RDFa is similar to Microdata but uses different attribute names. JSON-LD is easier to add, maintain, and validate, so almost all modern sites use it.

Which schema types should I use?

  • Article / NewsArticle / BlogPosting: any editorial content.
  • Product: e-commerce pages with price, availability, and (if applicable) reviews.
  • Recipe: cooking content with ingredients and steps.
  • Event: anything with a date and location.
  • LocalBusiness: brick-and-mortar storefronts.
  • Organization and Person: about pages, author boxes.
  • FAQPage: pages structured as Q+A (note Google deprecated the FAQ rich result in 2023, but the markup still helps AI Overviews and voice search).
  • BreadcrumbList: navigation breadcrumbs for the site hierarchy.
  • VideoObject: hosted or embedded video pages.

Does the URL auto-fill feature work on any site?

The URL extractor fetches your page through our proxy pool, parses the HTML, and pre-fills the form from any existing JSON-LD blocks, OpenGraph tags (og:title, og:image), Twitter card tags, standard meta tags, the page title, the first H1, and the canonical URL. Sites that hide their content behind heavy JavaScript (SPAs that only render in the browser) may give weak results, since our fetch sees the raw HTML the server returned, not the JS-rendered DOM. Form-fill mode always works regardless of source.

Will my schema markup show up as a rich result in Google?

Adding valid markup makes you eligible for rich results, but Google decides per-page whether to actually surface them. Pages that match the schema spec exactly, sit on reputable sites, and serve a clear query intent are the most likely candidates. Use this tool's validation strip to catch missing required fields, then run the output through Google's Rich Results Test to confirm eligibility before deploying.

Is FAQ schema still useful after Google deprecated the rich result?

Yes, with a caveat. In August 2023 Google removed the FAQ-accordion rich result for most sites (only government and well-known authority sites still see it). However, FAQ markup remains useful: AI Overviews and voice-search surfaces still parse it, structured-data validators still expect it on Q+A pages, and the markup itself signals semantic clarity. We keep FAQ Page in this generator with an explicit deprecation banner so you know what you're getting.

How is this different from Yoast, RankMath, or Schema App?

Those are WordPress plugins or paid SaaS that auto-inject schema across an entire site. They're great if you're running on a platform they support. This tool is for everyone else: pages on Webflow, Squarespace, Ghost, custom-built sites, static sites, headless CMS setups, internal tools, and anywhere a plugin can't reach. You generate the JSON-LD here, then paste it once. No signup, no monthly fee, no platform lock-in.

. Google explicitly recommends JSON-LD over Microdata or RDFa because it sits separately from your visible HTML and is easier to maintain. Most CMS platforms (WordPress, Shopify, Webflow) also have plugins or built-in fields that accept JSON-LD blocks."}},{"@type":"Question","name":"What is the difference between JSON-LD, Microdata, and RDFa?","acceptedAnswer":{"@type":"Answer","text":"All three are syntaxes for embedding the same Schema.org vocabulary in your page. JSON-LD is a separate