Choose Schema Type
Article
Product
FAQ Page
Local Business
Recipe
Event
Person
Organization
Breadcrumb
Video
HowTo
Review
Job Posting
Course
WebSite
Fill Details Article

About This Schema Markup Generator

What This Tool Generates

This schema markup generator creates valid JSON-LD structured data for 15 Schema.org types. Everything runs in your browser — no data is uploaded to any server.

  • Article — with sub-types Article, NewsArticle, BlogPosting, and TechArticle; includes author, publisher with logo, dates, and featured image
  • Product — with SKU, brand, price, currency, availability status, and aggregate rating from reviews
  • FAQPage — unlimited Q&A pairs via repeatable rows; the most reliable schema for rich result expansion in SERPs
  • LocalBusiness — with address, phone, email, opening hours, price range, rating, and 9 business sub-types
  • Recipe — with prep/cook time, ingredients, step-by-step instructions, nutrition, cuisine, and rating
  • Event — with start/end date, location, ticket offers, attendance mode (in-person, online, mixed), and event status
  • HowTo, Review, JobPosting, Course, VideoObject, Person, Organization, BreadcrumbList, WebSite — all fully supported with their required and recommended properties
  • Three output tabs — Formatted JSON-LD for readability, Minified for production, and HTML script tag for direct paste
  • Built-in validation — required field checks per schema type with a pass/issue badge

How to Use This Tool

  • Click a schema type card — the form updates instantly to show relevant fields for that type
  • Fill in the required fields (marked with a red asterisk) — these are needed for valid schema and rich results
  • Fill optional fields as completely as possible — more data helps search engines better understand your content
  • For FAQPage and BreadcrumbList, use the Add Question / Add Breadcrumb buttons to add unlimited items
  • Click Generate Schema — the JSON-LD appears in the output panel with syntax highlighting
  • Check the validation badge — green means valid, orange means missing required fields
  • Switch to HTML Tag tab to get the complete script block ready to paste into your HTML head
  • Click Copy JSON-LD or Download .json to save the output
  • Test your schema at Google's Rich Results Test before deploying
  • Also validate at validator.schema.org for full Schema.org compliance

Schema Markup Complete Reference Guide

JSON-LD Basics

Every JSON-LD schema block must include @context: "https://schema.org" and @type specifying the schema type. The script tag must use type="application/ld+json". JSON-LD is the only format recommended by Google — it is separate from page HTML and does not require inline markup. Multiple schema blocks can coexist on one page, or be combined in a @graph array. Schema markup must match the actual visible content on the page — Google penalizes misleading or false structured data.

Rich Result Schema Types

These schema types most reliably produce rich results in Google Search: FAQPage shows expandable Q&A accordion; Product shows price, availability, and star ratings; Recipe shows image, cook time, and rating; Event shows date, location, and ticket link; JobPosting shows salary, employment type, and location; HowTo shows step-by-step instructions; VideoObject enables video carousels and rich previews; Course shows provider and price in education-related searches.

Required vs Recommended

Required fields (marked with * in this tool) must be present for Google to consider the schema valid. Missing required fields does not necessarily break the page, but may prevent rich results. Recommended fields increase the chance of rich results and provide more information to search engines. For Article: headline, author, datePublished, and publisher are required. For Product: name is required, but offers with price and aggregateRating greatly improve rich results. For FAQPage: at least one Question with a non-empty Answer is required.

Testing & Troubleshooting

Always test with Google Rich Results Test (search.google.com/test/rich-results) before deploying. Common issues include missing required fields (the most common cause of no rich results), schema type mismatch with page content, invalid date formats (use ISO 8601: YYYY-MM-DD), malformed JSON (missing commas, unclosed brackets), and deploying schema markup inside client-rendered JavaScript that Googlebot cannot process. If rich results stop appearing after changes, re-test and check Search Console's Rich Results report for errors.

Schema Markup Generator FAQ

Schema markup is structured data added to web pages that helps search engines understand content context. It uses vocabulary from Schema.org, maintained by Google, Microsoft, Yahoo, and Yandex. JSON-LD (JavaScript Object Notation for Linked Data) is Google's recommended format — added as a <script type="application/ld+json"> block in your HTML head, completely separate from visible content. It is the easiest format to implement and maintain compared to Microdata and RDFa.

Rich results are enhanced Google search listings showing star ratings, product prices, FAQ dropdowns, recipe details, event dates, and job salary ranges. They require correct schema markup. Schema types most reliably producing rich results include FAQPage (expandable Q&A), Product (price, availability, rating stars), Recipe (image, cook time, rating), Event (date, location, ticket link), and JobPosting (salary, employment type). Google selects based on content quality and guidelines — schema is necessary but not sufficient.

Use the schema type that most accurately describes your content. Article or BlogPosting for editorial content; Product for items you sell; FAQPage for Q&A pages; LocalBusiness for physical locations; Recipe for cooking content; Event for conferences, concerts, or webinars; HowTo for step-by-step guides; JobPosting for job listings; Review for editorial or user reviews; Course for online learning; VideoObject for video pages; Person for author or bio pages; Organization for company about pages; BreadcrumbList for navigation paths; WebSite with SearchAction for your homepage to enable the Google Sitelinks Searchbox.

Generate the JSON-LD with this tool, then use the HTML Tag tab to get the complete script block. Paste it into your HTML <head> section. For WordPress, plugins like Yoast SEO or RankMath generate schema automatically — or use a code snippet plugin to inject custom schema. For other CMS platforms, use a header code injection field. After adding, test with Google's Rich Results Test at search.google.com/test/rich-results to confirm there are no errors before deploying to production.

Yes. A page can include multiple JSON-LD script blocks with different schema types, or combine them in a single @graph array. Common combinations: Article + BreadcrumbList + Person for blog posts; Product + BreadcrumbList for product pages; LocalBusiness + FAQPage for business pages with a FAQ section; WebSite + Organization for homepages. Each schema block must accurately reflect actual visible content on the page — Google penalizes misleading or false structured data.

Schema markup is not a direct ranking factor — Google has confirmed that structured data itself does not boost rankings. However, rich results (star ratings, FAQ dropdowns, product prices) significantly increase click-through rates in search results, which can lead to more traffic and engagement signals that may influence rankings over time. Schema markup also helps search engines better understand your content, improving how accurately pages are matched to relevant queries. The most practical benefit is appearing in rich result features that competitors without schema may miss.

This generator includes built-in validation that checks required fields and shows a pass or issue count badge. For full validation before deploying, use: Google's Rich Results Test (search.google.com/test/rich-results) — checks whether your page qualifies for rich results in Google Search. Schema Markup Validator (validator.schema.org) — validates against the full Schema.org specification, broader than just Google's requirements. Always fix critical errors before deploying — invalid markup may be partially or completely ignored by search engines.