Free tool · No sign-up

Schema Markup Generator

Create valid JSON-LD structured data for 28 guided schema types, plus every other type in the schema.org vocabulary. Fill in a form, check it against Google's rules, preview the rich result and copy the code.

  • 800+ schema.org types
  • Google required-field checks
  • Nothing you enter is stored

Step 1

Choose a schema type

Pick the type that matches the page you are marking up. Not sure? The type guide below explains each one.

Business and identity

Content and pages

Commerce and reviews

Events, jobs and learning

  • Google rich result
  • Limited by Google
  • Structured data only (no rich result)
From code to live

How to add schema markup to your website

Generating the code takes a minute. These four steps get it onto your page and checked.

1

Copy the snippet

Use Copy code in HTML snippet mode. It includes the script tag, so it is ready to paste.

2

Paste it on the page

Put it in the head or body of the page it describes. In WordPress use a Custom HTML block or your SEO plugin's schema box; in Tag Manager use a Custom HTML tag.

3

Test it

Check the code in our Schema Markup Validator, then run the live URL through Google's Rich Results Test.

4

Monitor it

After Google recrawls the page, open the Enhancements reports in Search Console to watch for errors across the site.

Which schema type?

All 28 guided schema types and what Google needs

Match the page you are working on to a type. The last column says what Google does with that markup today, because not every valid type produces a rich result.

Schema types in the generator, what each is best for, the properties Google needs and its status in Google Search
Schema type Best for What Google needs In Google Search
Organization Your company or brand on its homepage or About page. No required properties; name, url, logo and address recommended. Google rich result
Local business A business with a physical location and opening hours. name and address. Google rich result
Person An author, founder or expert page. name; the rest is recommended for entity clarity. Structured data only
WebSite Your homepage, to state your preferred site name. name and url. Structured data only
Profile page A page about one person or organization. mainEntity (Person or Organization) with a name. Google rich result
Service A service page: what you do, for whom and where. name; provider and areaServed recommended. Structured data only
Article Blog posts, news articles and guides. No required properties; headline, image, author and dates recommended. Google rich result
WebPage Any page, including About and Contact pages. name and url. Structured data only
FAQ A page with questions and answers written by you. mainEntity with Question name and acceptedAnswer text. Limited by Google
HowTo Step-by-step tutorials. name and a list of steps. Structured data only
Q&A page A page with one question and user answers. Question name, answerCount and at least one answer. Google rich result
Discussion forum A forum thread or social post with comments. author, datePublished and text, image or video. Google rich result
Video A page that features a video. name, thumbnailUrl and uploadDate. Google rich result
Image metadata Photos and graphics you license. contentUrl plus license, creator, credit or copyright. Google rich result
Dataset Open data and research for Dataset Search. name and description. Google rich result
Book A book detail page. name and author. Structured data only
Breadcrumb Every page below the homepage. At least 2 items, each with name and position. Google rich result
Carousel (ItemList) A category page that lists recipes, courses, movies or restaurants. Each ListItem needs url and position. Limited by Google
Recipe Recipes with ingredients, times and ratings. name and image. Google rich result
Product A product page: price, stock, ratings and shipping. name, plus offers, review or aggregateRating. Google rich result
Product variants One product sold in several sizes or colors. name; productGroupID, variesBy and hasVariant recommended. Google rich result
Review A review of a product, book, movie or business. itemReviewed, reviewRating and author. Google rich result
Software app Apps and web software. name, offers.price and a rating or review. Google rich result
Event Events with a date, place and tickets. name, startDate and location. Google rich result
Job posting A vacancy page. title, description, datePosted, hiringOrganization and jobLocation. Google rich result
Course A course or training page. name and description; provider recommended. Google rich result
Movie A film detail page. name and image. Google rich result
Vacation rental A holiday home or room listing. name, identifier, image, latitude, longitude and containsPlace with occupancy. Google rich result

Need something else? The Any other schema.org type builder covers the full vocabulary, from Podcast and Car to Hospital and MusicRecording.

Be realistic

Rich results, limits and markup that is still worth adding

Google has trimmed the number of structured data features that change how a result looks. Knowing which is which saves you time.

Google rich result

Eligible for a visible enhancement

Product, Recipe, Event, Job posting, Local business, Video, Review, Breadcrumb and more. Follow Google's required fields and keep the markup honest, and the page can qualify for stars, prices, dates or key moments.

Limited by Google

Valid, but restricted

FAQ rich results now go mainly to well-known government and health sites, and carousels only appear for lists of recipes, courses, movies and restaurants. The code is correct; the visible result is not guaranteed.

Structured data only

Helps understanding, no rich result

Person, WebSite, WebPage, Service, Book and HowTo don't change how a result looks. They still describe who and what your page is about to search engines and AI assistants, which is why they are worth adding.

What good looks like

Schema markup best practices in six rules

The checklist I use when auditing client sites. Following it avoids the errors and manual actions that waste most schema projects.

1. Mark up what people can see

Every value in your schema should also be visible on the page. Hidden or invented data can lead to a manual action.

2. Use JSON-LD

It is Google's preferred format and the easiest to maintain. Keep it in one script block per page instead of scattering attributes through your HTML.

3. Pick the most specific type

Use Dentist or Restaurant rather than a generic LocalBusiness, and BlogPosting rather than Article, where it fits the page.

4. Fill required first, then recommended

Required fields decide eligibility; recommended fields decide how useful the result is. Skip properties you can't back up with real data.

5. Connect your entities

Give your Organization or Person an @id, then reference it from your Article or WebSite. The bundle tab builds that graph for you.

6. Keep it current

Prices, dates, opening hours and availability go stale. Update the markup when the page changes, and re-test after redesigns.

Honest limits

What a schema generator can't do for you

A generator makes sure the code is well formed and complete. It can't decide these things.

A rich result isn't guaranteed

Google chooses what to show. The preview illustrates what the markup can do, not what you will get.

It can't check your facts

If a price, rating or date in the markup doesn't match the page, that is on you. Never fake reviews or ratings.

Rules change

Google updates its requirements and retires features. The tool follows the documentation as of 2026, so re-test when it matters.

Test with Google's tools

Only the Rich Results Test and Search Console confirm eligibility. Use this tool to build, and those to verify.

Schema markup

What schema markup is and which kinds still earn a rich result

Schema markup is structured data that labels what a page is about, using the shared schema.org vocabulary. Instead of leaving a search engine to infer that a number is a price or a name is an author, the markup says so directly. It is usually written as JSON-LD, a block of JSON inside a script tag that sits apart from your visible HTML. A schema markup generator fills in that block from a form, so you do not write the syntax by hand.

What the markup does depends on the type. Google lists the features it can turn into rich results in its structured data gallery, including Article, Breadcrumb, Event, Job posting, Local business, Organization, Product, Recipe, Review snippet and Video. Valid markup makes a page eligible, not guaranteed. Some features have gone: How-to rich results were removed in 2023, and Google stopped showing FAQ rich results in May 2026. FAQ and HowTo markup is still valid schema.org, but it no longer changes how a Google result looks.

Three rules keep markup safe. Use JSON-LD, which Google recommends. Mark up only what visitors can see on the page, because hidden or misleading markup can lead to a manual action. Then test it before and after you publish. The generator builds the code, and this page's checks flag missing required fields.

When to use it

When to generate schema markup

Add markup where it describes something real on the page and where a type exists for it.

For a business home page

Build Organization and WebSite markup with your name, logo, contact details and profiles. Google can use WebSite markup as one input for your site name in results.

For a local shop, clinic or office

Use Local business, or a more specific subtype, with your address, opening hours and phone. Keep it identical to what the page and your public listings say.

For product pages in a store

Add Product markup with name, image, price, currency and availability. For a Nepali store the currency code is NPR. Refresh the values whenever prices or stock change.

For articles and guides

Add Article markup with headline, image, author and dates, and link the author to a Person or profile page, so each post carries the same details that are visible on it.

For every page below the home page

Breadcrumb markup describes the page's place in your site. Add it through a template once, then check that it matches the trail visitors see.

To combine several types on one page

Build each type, add it to the bundle and output a single @graph. This links your Organization, WebSite and Article together with shared @id values.

Common mistakes

Schema markup mistakes and how to fix them

Most schema problems are about honesty and freshness, not syntax.

Adding FAQ or HowTo markup for a rich result

What goes wrong: Google stopped showing FAQ rich results on May 7, 2026, and How-to results ended in 2023. Markup added only for those results now earns nothing visible in Google.

The fix: If a visible Q and A or step list helps readers, keep it. Treat the markup as optional, and do not expect a result change from it.

Marking up content visitors cannot see

What goes wrong: Putting prices, ratings, reviews or questions in markup that are not on the page breaks Google's guidelines and can lead to a manual action.

The fix: Only describe what is visible. If a value in the markup is not on the page, add it to the page or remove it from the markup.

Star ratings on your own business

What goes wrong: Google says Local business and Organization markup is only eligible for review snippets on sites that collect reviews about other businesses. Marking up your own testimonials that way goes against Google's self-serving reviews guideline.

The fix: Leave out aggregate ratings for your own business, or mark up only genuine, visible reviews of a product or service that qualifies for review snippets.

Missing required fields or badly formatted values

What goes wrong: A Product price written as a text string with a symbol, a date that is not ISO 8601, or a missing name can make the markup invalid for its feature.

The fix: Write the price as a number and give the currency as a three-letter ISO 4217 code. Fill the required fields first, then the recommended ones.

Duplicate markup from a plugin and the theme

What goes wrong: A theme, an SEO plugin and a pasted snippet can each output their own Organization or Article, giving search engines conflicting copies.

The fix: Pick one source of markup per type. If you paste generated code, switch off the same type in the plugin or theme before you publish.

Letting markup go stale

What goes wrong: Prices, opening hours, availability and event dates change, but markup copied once stays as it was. Google says it will not show a rich result for time-sensitive content that is out of date.

The fix: Generate time-sensitive markup from the same data as the page, and re-test after redesigns or template changes.

Glossary

Schema markup terms explained

Structured data
Information about a page written in a standard format that machines can read. On the web it normally uses the schema.org vocabulary and appears as JSON-LD, Microdata or RDFa.
schema.org
The shared vocabulary of types, such as Product and Event, and properties, such as price and startDate. It is used by Google, Microsoft and other search engines.
JSON-LD
JSON for Linked Data, a W3C format for writing structured data. It sits in a script tag, so it does not mix with visible HTML, and Google recommends it.
Rich result
A search result enhanced with extra detail, such as a price, an image, a date or stars. Eligibility depends on valid markup, and Google decides whether to show it.
Required and recommended properties
Required properties are the ones a Google feature needs to be eligible. Recommended ones are optional, but they add information. Some types, such as Organization, have no required fields.
@id and @graph
@id gives an entity a stable identifier so other markup can refer to it. @graph places several connected entities in one JSON-LD block.
Manual action
A penalty from Google's review team. For structured data, it makes the page ineligible for rich results, though the page can still appear in normal web results.
Enhancements and rich result reports
Reports in Search Console that show errors and valid items for each structured data feature across your site after Google has crawled your pages.
Keep going

Related tools, guides and services

Generate the markup here, then validate it, place it and check the page around it.

Tool

Schema Markup Validator

Paste your code or a URL to check every type, property and value against schema.org and Google's requirements.

 Tool

On-Page SEO Checker

Score the page itself, including whether its structured data is valid.

 Tool

Local SEO Landing Page Audit

Check a location page's content, markup and local signals in one pass.

 Guide

SEO for Nepali ecommerce

See a worked Product markup example with prices in NPR, and what Google does not promise.

 Guide

SEO audit errors that matter

See where structured data ranks among the issues worth fixing, and the note on FAQ markup.

 Service

Technical SEO service

Get structured data planned, implemented and monitored across your site.
Madhav Kushwaha, SEO, AEO, GEO and digital marketing consultant in Kathmandu, Nepal

Built by

Madhav Kushwaha

SEO, AEO, GEO & Digital Marketing Consultant in Kathmandu, Nepal, and trainer at ODcrU Academy and TechAxis Institute. I built this generator because structured data is one of the quickest technical wins for clients, and most tools either cover three types or bury the required fields. The checks follow Google's documentation and the any-type builder uses the official schema.org vocabulary.

About Madhav Technical SEO help

Schema Markup Generator: Frequently Asked Questions

Schema markup is code that describes the content of a page in a standard vocabulary from schema.org, so search engines know that a page is a recipe, a product, an event or a business, and which numbers and names on it matter. It is added to the page as structured data, most often as JSON-LD.
JSON-LD is a way to write structured data as a block of JSON inside a script tag. Google recommends it over Microdata and RDFa because it sits in one place, doesn't touch your visible HTML and is easy to generate, edit and test. This tool outputs JSON-LD only.
Pick a schema type, fill in the form, and watch the JSON-LD update on the right. Fields marked Required are needed for Google's rich results and Recommended fields improve them. Open the Checks tab to see what is missing, then copy the code or download it and add it to your page.
It has guided forms for 28 types: Article, FAQ, HowTo, Recipe, Video, Product, Product variants, Review, Software app, Local business, Organization, Person, WebSite, WebPage, Breadcrumb, Carousel, Event, Job posting, Course, Movie, Book, Dataset, Q&A page, Discussion forum, Profile page, Image metadata, Service and Vacation rental. The Any schema.org type builder covers every other type in the official vocabulary, more than 800 in total.
Paste the script block into the head or the body of the page it describes. Google reads either. In WordPress you can use a Custom HTML block, your theme's header scripts or an SEO plugin's schema field, and in Google Tag Manager you can use a Custom HTML tag. Each page should only describe what is visible on that page.
Not directly. Google has said structured data is not a ranking factor. It makes a page eligible for rich results such as stars, prices and event details, which can lift click-through rate, and it helps search engines and AI assistants understand who and what a page is about.
Not automatically. Valid markup makes you eligible, but Google decides whether to show a rich result based on the page, the query and quality signals. The markup must match what visitors can see on the page, and it must follow Google's guidelines for that type.
In 2023 Google limited FAQ rich results to well-known government and health websites and stopped showing How-to rich results. The markup is still valid schema.org and can still help other search engines and AI tools read your page, which is why the generator keeps both, with a clear status label on each type.
Yes, and it is common: for example Organization, WebSite, Article, FAQPage and BreadcrumbList on one article. Build each one, press Add to page bundle, and the Bundle tab combines them into a single @graph or separate script tags.
Copy the code and paste it into the Schema Markup Validator on this site to check the syntax and every property against schema.org, then use Google's Rich Results Test to see which rich results the page is eligible for. After publishing, the Enhancements reports in Google Search Console show errors across your whole site.
Required fields are the properties Google's documentation says a type needs to be eligible for its rich result. Recommended fields are optional but make the result more useful. For types Google doesn't turn into a rich result, the tool marks the properties that make the markup most useful.
It is free with no sign-up. Everything you type is processed in your browser and never sent to a server. The only request the page makes is to download a copy of the schema.org vocabulary the first time you use the any-type builder or search the picker.

More free SEO tools and ways to learn

Explore the full toolkit, or go deeper with a service or course built from the same client work.

All free tools On-Page SEO Checker Schema Markup Validator Title & Meta Description Preview Technical SEO Service Local SEO Landing Page Audit
Call WhatsApp SEO Audit