Sixteen schema.org types
Article, FAQ Page, Product, Local Business, Organization, Person, Breadcrumb, How-to, Event, Recipe, Video, Website, Job Posting, Course, Software App, and Review are each available from one selector.
Schema Markup Generator
Pick a schema.org type, fill the properties Google looks for, and copy a JSON-LD block that is ready to paste into your page template.
Sixteen schema.org types with the properties Google documents for each rich result.
Empty properties are dropped so the finished JSON-LD block never carries blank keys.
- Required and recommended properties flagged live.
- Paste-ready JSON-LD with script tag.
- Sixteen schema.org types in one page.
How to generate schema markup in JSON-LD
Choose the schema.org type that matches the page, fill the documented properties, then copy the JSON-LD block into the page head.
- 1
Pick the schema type for the page
Select Article for a blog post, Product for an ecommerce page, Local Business for a storefront, FAQ Page for a question section, or any of the other types listed across the selector. One page usually deserves one primary type plus a breadcrumb block.
- 2
Fill the documented properties
Properties marked Required are the ones Google lists as mandatory for that rich result, and properties marked Recommended improve eligibility. Multi-value inputs such as image URLs, opening hours, or ingredients accept one entry per line, and repeatable rows cover questions, steps, and breadcrumb levels.
- 3
Read the field check panel
The panel beside the code lists any required property you have left empty and any recommended property worth adding. Structured data must describe content a visitor can actually see, so confirm each price, rating, date, and answer also appears in the rendered page.
- 4
Copy the JSON-LD into your template
Keep the script tag wrapper on to copy a complete block for the page head, or turn it off to copy raw JSON for a CMS field or a component prop. After deploying, run the live URL through the Rich Results Test to confirm Google parses the markup.
Required and recommended flags
Each property carries the label Google publishes for it, and the field check panel lists what is still missing before the markup can qualify for a rich result.
Live JSON-LD output
The code panel rebuilds on every keystroke in the browser, drops properties you left blank, and prints indented JSON-LD wrapped in an application/ld+json script tag.
Nested objects handled for you
Author, publisher, offer, aggregate rating, postal address, geo coordinates, salary range, and search action objects are nested correctly instead of being flattened into loose keys.
Repeatable question and step rows
FAQ questions, how-to steps, and breadcrumb levels use add and remove rows, so a long support page or a multi-level path stays quick to describe.
Copy or download the block
Copy the markup to the clipboard for a template paste, or download it as an HTML snippet with the script tag or a plain JSON file for a CMS field.
Schema Markup Generator privacy and processing
These notes describe where the JSON-LD is assembled, what happens to the property values you type, and whether an account is involved in generating or copying a schema block.
Browser JSON-LD builder
Every property you type is assembled into a schema.org JSON-LD object inside the open page, empty properties are dropped, and the finished block is printed with indentation you can paste straight into a template.
No stored schema drafts
Typed property values, added question rows, and the generated JSON-LD block stay in current tab state only. Closing the tab or refreshing the page discards everything you entered.
Schema Markup Generator account access
Choosing a schema type, filling properties, and copying the finished JSON-LD block all work without an account, and nothing you type is attached to a profile.
Before You Use Schema Markup Generator
Read these notes before publishing structured data on a live page, since incorrect markup can trigger a manual action against the site.
Accuracy
Structured data must describe content that is visible on the same page to a normal visitor.
Prices, ratings, review counts, dates, and answers in the markup have to match what the rendered page shows.
Eligibility
Valid markup makes a page eligible for a rich result but never guarantees that Google will show one.
Some rich results are limited by country, language, site type, or an ongoing Google search feature rollout.
Placement
Paste the script tag into the head of the page, or render it from your template or CMS field.
One primary type per page plus a breadcrumb block is usually enough, and duplicated blocks can conflict.
Verification
Run the deployed URL through the Rich Results Test and the schema.org validator after publishing the markup.
Watch the Search Console enhancement reports for parsing errors that only appear once Google recrawls the page.
Limits
Schema Markup Generator builds JSON-LD in the browser from the values you type, so extremely long descriptions or hundreds of question rows can slow the active tab.
Questions about Schema Markup Generator
What is schema markup and why does it matter for SEO?
Schema markup is structured data written in the schema.org vocabulary that tells search engines what a page describes: an article, a product, a recipe, a job listing. It can make a page eligible for rich results such as review stars, FAQ dropdowns, and event listings.
Which schema format should I use, JSON-LD or microdata?
Google recommends JSON-LD, which is what this generator produces. JSON-LD sits in a single script tag instead of being woven through your HTML attributes, so it is far easier to add, template, review in a diff, and update later without touching page layout.
Where do I paste the generated schema markup?
Put the script tag inside the head of the page, or render it from your layout template, CMS structured data field, or framework component. Google also reads JSON-LD placed in the body, and it will pick up markup injected by JavaScript once the page is rendered.
Does adding schema markup guarantee rich results in Google?
No. Valid markup only makes the page eligible. Google decides case by case using page quality, site history, query intent, and feature availability in that country and language, and it can drop a rich result even from pages with flawless structured data.
How many schema types can one page use?
A page can carry several blocks, but they should describe the same content honestly. A common combination is one primary type such as Article or Product plus a BreadcrumbList. Stacking unrelated types on a single page invites parsing conflicts and spam reports.
Is anything I type into the schema fields sent anywhere?
No. Property values are assembled into JSON-LD inside your browser tab and never leave it. Nothing is stored between visits, so treat the page as a scratch pad and keep the finished markup in your repository, CMS, or template.
4.1 (378 ratings)