Schema Markup Generator

This free schema markup generator builds JSON-LD for twelve types in your browser, then answers the question other generators skip: whether Google still shows that rich result. It marks every property Google actually requires, separately from what schema.org merely allows, and flags the three features Google has already retired.

Schema type

Active rich result

Article is an active rich result in Google Search.

Google documents no required properties for Article. Every field below is listed as recommended, which surprises people who were told headline and image were mandatory. Checked against Google's documentation on September 20, 2026.

Blog posts, news stories and editorial pages.

Exact @type

headlinerecommended

The title of the article.

imagerecommended

Representative image, absolute URL.

datePublishedrecommended

First published, ISO 8601.

dateModifiedrecommended

Last meaningful update.

author.namerecommended

Person or organisation.

author.url

A page about the author.

publisher.name

The publication.

description

Short summary.

mainEntityOfPage

Canonical URL of this page.

JSON-LD

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article"
}
</script>

Wrap in a <script> tag

Nothing missing that Google requires.

Recommended by Google, not required

headline is recommended by Google. Valid without it, better with it.
image is recommended by Google. Valid without it, better with it.
datePublished is recommended by Google. Valid without it, better with it.
dateModified is recommended by Google. Valid without it, better with it.
author.name is recommended by Google. Valid without it, better with it.

This checks your markup against Google's documented requirements, read on September 20, 2026. The official confirmation is Google's own Rich Results Test, which reads your live page.

What does this generator do?

It builds JSON-LD from a form, like every schema generator does, and then answers the second question, which almost none of them answer: will Google actually do anything with this?

The rich result status of every type, with the date it changed. Three of the features generators still advertise were retired by Google, and you will see that stated before you fill in a single field.
Required by Google, marked separately from recommended. Two different lists, because they are two different things. Schema.org will happily accept markup that Google ignores.
Format checks where people actually break it: a date with no time zone, a price written as $19.99, a relative URL, a duration written as 1h30 instead of PT1H30M.
Audit mode. Paste the markup already on your site and it names each type, what is missing, and what is no longer shown.
12 types: Article, Product, Local Business, Event, Breadcrumb, Organization, Person, Recipe, Job Posting, Video, FAQ and How-to.
Copy or download the complete block, as a <script> tag or as a .json file. Nothing leaves your browser.

Three features Google retired, and generators still sell

Feature	Status in Google Search	Since
FAQ rich result	No longer shown	7 May 2026
How-to rich result	No longer shown	September 2023
Sitelinks Search Box	Removed	21 November 2024

All three remain valid schema.org, and keeping them causes no harm or error. Machines still read them, AI answer engines included. What changed is that they no longer draw anything in the search result. We state the fact and the date; what you do about it on your own site is yours to decide.

Valid is not the same as eligible

This is the distinction that explains most of the "my schema is fine but nothing shows" questions:

Type	What Google requires	What people assume
Article	Nothing at all. Every property is recommended	headline and image are mandatory
Product	`name`, plus one of offers, review or aggregateRating	`name` and a price is enough
Event	`name`, `startDate`, `location`, and the street address inside it	a venue name is enough
Job Posting	title, description, datePosted, hiringOrganization, and `addressCountry` by name	a city is enough
Breadcrumb	`name` and `item`, except `item` on the last crumb	every crumb needs a URL

Every line there was read from Google's own documentation, and the page shows the date it was checked.

What this tool does not do

It does not test your live page. There is no backend and no crawler, so it cannot fetch your URL. The official confirmation is Google's Rich Results Test, which we link to rather than imitate.
It does not guarantee a rich result. Eligible is not the same as shown. Google decides per query, per page, per day.
It checks Google's documented rules, not Google itself. Our checks are that documentation transcribed by hand. That is why the verification date is printed on the page, and why this file changes when Google changes.
It does not generate Microdata or RDFa. Only JSON-LD, which is the format Google recommends.
It does not cover every schema.org type. Twelve, chosen and checked properly, instead of forty listed with nothing behind them.

Is my markup private?

Yes. The form, the JSON-LD it produces and every check run against it happen in JavaScript already loaded in your browser. No network request carries what you type, nothing is logged or stored, and closing the tab clears it. That matters more than it sounds: schema drafts routinely contain an unannounced price, an unpublished job opening or a launch date that is not public yet.

Frequently asked questions

Does FAQ schema still work in 2026?

The FAQ rich result stopped appearing in Google Search on May 7, 2026, and Search Console stopped reporting on it that June. FAQPage is still valid schema.org markup that machines read, including AI answer engines, so it does no harm. It simply will not draw the expandable questions any more.

Which schema types still produce rich results?

Article, Product, Event, Recipe, Job Posting, Video, Local Business, Breadcrumb and Organization are all documented as active features today. FAQ, How-to and the Sitelinks Search Box are not. This page states the status of every type it generates, with the date Google made the change.

Why is my schema valid but not showing rich results?

Because validity and eligibility are two different tests. Schema.org accepts markup that Google will not act on. Google publishes its own required properties per type, and missing one blocks the rich result while the JSON stays perfectly valid. This generator shows both layers separately.

What does Google require for Event schema?

Four things: name, startDate, location, and the street address inside that location. The last one is what most people miss, because a venue name feels like enough. An Event carrying only a venue name is not eligible, and this tool flags that as an error rather than a suggestion.

Does schema markup improve rankings?

Google has said repeatedly that structured data is not a ranking factor on its own. What it does is make your page eligible for richer presentation and easier for machines to parse, which can affect how many people click. Treat ranking claims about schema with suspicion.

Is JSON-LD better than Microdata for schema?

Google recommends JSON-LD, which is why this page generates only that. JSON-LD sits in one block in your HTML instead of being threaded through your markup, so it survives template changes and is far easier to review. Microdata and RDFa still work, they are just harder to maintain.

Where do I put the JSON-LD code on my page?

Inside a script tag with the type application/ld+json, anywhere in the head or the body. Google reads it in either place, including markup injected by JavaScript, though server-rendered markup is read more reliably. One block per schema object, or several objects inside one graph.

Can I check schema markup I already have?

Yes. Switch to the audit mode and paste what is on your page, with or without the script tag around it. It reads a single object, an array, or a graph block, names each type it finds, and lists what Google requires that is missing or malformed.

Does HowTo schema still do anything?

Google removed the How-to rich result in September 2023 and it is no longer in the documented feature list. The markup remains valid schema.org and still describes your steps to any machine reading the page, so keeping it is harmless. Expecting a visual step-by-step result is not.

Is my data sent anywhere when I use this?

No. The form, the JSON-LD it builds and every check run against it happen in your browser, so nothing you type is uploaded, logged or stored. Closing the tab clears it. That matters when the markup contains an unpublished job posting, price or launch date.

Rate Schema Markup Generator & help shape it

This tool is free and still growing. Tell us what works, what you would change, and what is missing. Your feedback is what decides what we build next.

Last updated: September 20, 2026