Schema Markup Generator
Say what is on the page and this names the schema.org type to use, whether that type still earns a rich result in 2026, and which generator writes the JSON-LD. Including the types we have no generator for, because the answer still matters.
Short answer
A schema markup generator writes structured data from a form rather than by hand. The decision before that is which type to use, and the rule is that it must describe what the page genuinely is. CrawlRaven generates Article, Product, FAQ, LocalBusiness, Event and BreadcrumbList. The chooser also names the type for Recipe, Video, JobPosting, Review and Organization, which have no generator here, and says what still earns a rich result.
Which type to use, and what it still earns
Schema markup is worth writing when two things hold: the type describes the page, and the type still does something. The second has changed a lot since 2023, and most advice on the subject has not caught up.
| Type | Use it for | Rich result in 2026 | Generator |
|---|---|---|---|
| Product | Something you sell | Yes: price, availability, rating | Product |
| Event | A dated event at a venue | Yes: date, location, tickets | Event |
| Article | Editorial and news content | Yes, modest; Top stories for news | Article |
| BreadcrumbList | The path to a deep page | Yes: replaces the URL in the result | Breadcrumb |
| LocalBusiness | A physical location | Knowledge panel details | Local business |
| FAQPage | Questions and answers | Restricted in 2023 to gov and health | FAQ |
| Recipe | A recipe | Yes: image, rating, time, calories | None here |
| VideoObject | A video | Yes: thumbnail and key moments | None here |
| JobPosting | A vacancy | Yes: Google Jobs | None here |
| Review | A rating of something | Not on your own business, since 2019 | None, deliberately |
| HowTo | A procedure | Retired entirely | None |
A dead rich result is not always a dead type
FAQ markup earns almost no rich results now, and is still worth keeping on pages that genuinely hold questions and answers. The rich result was never the only thing reading it: an assistant summarising your page gets a clean question-and-answer pair from the markup rather than having to infer one from prose.
The properties that decide eligibility
Every type has a small set of properties Google will not generate a rich result without. Markup missing one of them is valid schema.org and completely ineligible, which is the state most unexplained "my markup is fine but nothing shows" cases are in.
| Type | Will not work without | Commonly forgotten |
|---|---|---|
| Product | name, offers (with price and priceCurrency) | availability, and an image |
| Event | name, startDate | location, and an endDate for multi-day events |
| Article | headline | datePublished, dateModified, author as a nested Person |
| Recipe | name, image, recipeIngredient, recipeInstructions | cookTime and nutrition, which earn the card |
| JobPosting | title, description, datePosted, hiringOrganization, jobLocation | validThrough, without which the posting goes stale |
| LocalBusiness | name, address | openingHoursSpecification, and a precise @type |
| BreadcrumbList | itemListElement with position and name | item, the URL each crumb points at |
Dates are the other reliable failure
datePublished, dateModified, startDate, endDate and validThrough all want ISO 8601: YYYY-MM-DD, optionally with a time and a timezone. A date written 14/03/2026 is ambiguous between two continents and is rejected rather than guessed at.
What to do after the generator hands you a block
Generating the JSON-LD is the quick part. These are the steps between that and a rich result, in the order they fail.
- 01
Decide whether the page has a thing on it
Structured data describes an entity with a defined shape: a product, an event, a recipe, a job. A general page about a topic has no shape to declare. Most pages need no markup at all, and adding some because a plugin offered does not help.
- 02
Pick the type that matches, not the type with the best rich result
Marking a landing page up as an Article because Articles get a rich result is the mismatch Google acts on. The type has to describe what the page genuinely is, which is the one rule that governs all of this.
- 03
Fill the required properties before the optional ones
Each type has a short list without which no rich result is generated: a Product needs a name and an offer, an Event a name and a startDate, an Article a headline. Valid markup missing one of these is valid and ineligible.
- 04
Make the markup agree with the visible page
A price, a rating or a date in the markup must match what a visitor sees. This is the rule Google issues manual actions over, and the commonest way to break it is leaving an old price in a template after the page was updated.
- 05
Paste it into the head and validate the live URL
JSON-LD goes in a script tag with type application/ld+json, usually in the head. Validate the deployed URL rather than the snippet you wrote, because plugins, themes and tag managers all rewrite structured data on the way out.
- 06
Check eligibility separately from validity
Our validator tells you the markup is correct. Google's Rich Results Test tells you whether Google will use it, and the Search Console enhancement reports tell you what it does with it at scale. The three answer different questions.
- Validate the deployed URL, not the snippet. Plugins, themes and tag managers rewrite structured data on the way out, and what matters is the block that reached the browser.
- Expect a wait. Rich results appear when the page is re-crawled and re-processed, which is days rather than minutes, and Google chooses whether to show them per query.
- Watch Search Console's enhancement reports rather than re-testing one URL. They are the only view of what Google is doing with your markup across the whole site.
To check what a page is currently serving, the structured data testing tool fetches a live URL and parses the JSON-LD that actually rendered, which is a different question from whether the snippet you wrote is well-formed.
What this hub gives you
A type for every page
Including the types we have no generator for, because the answer still matters
Rich result status
Which types still earn one in 2026, and which were restricted or retired
Required properties
The short list each type will not produce a rich result without
Six generators
Article, Product, FAQ, LocalBusiness, Event and BreadcrumbList
The honest no
Most pages need no markup at all, and the chooser says so
Validation next
Every path ends at the validator, because untested markup is a guess
Why there is no Review generator
Frequently asked questions
What is a schema markup generator?
It is a tool that writes structured data for you, usually as JSON-LD, from a form rather than from hand-written code. Structured data is a block of machine-readable description added to a page: it names what the page is about in a vocabulary from schema.org, so a search engine does not have to infer it. The generator's job is getting the required properties and the syntax right, which is where hand-written markup usually fails.
Which schema type should I use?
The one that describes what the page genuinely is. Use the chooser above: say what is on the page and it names the type, says whether that type still earns a rich result, and links the generator for it. The temptation worth resisting is picking a type because its rich result looks good. A mismatch between the markup and the page is the thing Google penalises.
Does schema markup improve rankings?
Not directly, and Google has said so repeatedly. Structured data is not a ranking factor. What it does is change how a result looks, and a result with a price, a rating or an event date attached earns more clicks than a plain one at the same position. The gain is in click-through, and on some types it is substantial.
What is the difference between JSON-LD, microdata and RDFa?
Three syntaxes for the same vocabulary. JSON-LD puts the description in a script tag separate from the HTML; microdata and RDFa weave attributes through the markup itself. Google recommends JSON-LD and so does everything here, for one practical reason: it can be added, changed or removed without touching the page's HTML, so it survives a redesign.
Which rich results can I still get in 2026?
Fewer than a few years ago. Product, Event, Recipe, Video, JobPosting and Breadcrumb are still widely granted. FAQ rich results were restricted in 2023 to government and health sites, and HowTo results were retired entirely. Self-serving reviews, a business marking up ratings of itself, have been ignored since 2019. That the rich result is gone is not always a reason to drop the markup, since assistants read it either way.
Where does the JSON-LD go on the page?
In a script tag with type="application/ld+json", normally in the head. The body works too and Google reads both. What matters more is that it ends up in the HTML your server returns: markup injected by client-side JavaScript is read only after a rendering pass that is queued and can lag the first crawl by days.
Can one page have several schema blocks?
Yes, and most well-marked-up pages do. A product page commonly carries Product, BreadcrumbList and Organization at once. They can be separate script tags or one @graph array; Google reads both. What causes trouble is two blocks of the same type describing the same thing differently, because then nothing on the page says which one is true.
Do I need schema markup on every page?
No, and the attempt is a common waste. Structured data describes an entity with a shape. A contact page, an about page or a general guide has no entity to declare, and marking one up as an Article adds a claim nobody asked for. Breadcrumbs are the exception worth applying sitewide, because every deep page has a navigation path.
What happens if my markup does not match the page?
In the mild case Google ignores it. In the serious case you get a manual action for spammy structured data, the rich results disappear for the whole site, and you file a reconsideration request to get them back. The usual cause is not fraud but drift: a price or a rating left in a template after the visible page changed.
Is there a generator here for every schema type?
No. There are six: Article, Product, FAQ, LocalBusiness, Event and BreadcrumbList, which cover the types most sites need. The chooser above names the right type even when we have no generator for it, says what its required properties are, and sends you to the validator to check what you write by hand. Pretending to cover a type we do not would be worse than saying so.
How do I check my structured data is correct?
Validate the live URL rather than the snippet. Our structured data testing tool fetches the page, parses the JSON-LD that actually rendered, and reports syntax errors, missing required properties and malformed dates. Then run Google's own Rich Results Test, which answers a different question: not whether the markup is valid, but whether Google will use it.
Does AI search read structured data?
It helps, though less decisively than vendors claim. An assistant summarising a page benefits from an unambiguous statement of what the thing is, what it costs and when it happens, rather than having to infer it from prose. That is the better argument for keeping FAQ markup now that the rich result is gone: the rich result was never the only reader.
Other schema generators
Local Business Schema Generator
Tell Google your business name, address, phone, and opening hours in the format it reads literally. Type your details, copy the code, paste it into your site.
Use toolProduct Schema Generator
Give Google your price, stock status, and star rating so they can show under your listing in search. Fill in the product details, copy the code.
Use toolFAQ Schema Generator
Mark up your questions and answers so search engines and AI assistants can lift them as direct answers. Unsupported HTML is stripped for you.
Use toolEvent Schema Generator
Get your event date, venue, and ticket link into Google's event listings and Maps. Handles in-person, online, and hybrid events correctly.
Use toolBreadcrumb Schema Generator
Replace the raw URL under your search result with a readable trail like Home > Guides > Technical SEO. Enter each level, copy the code.
Use toolArticle Schema Generator
Tell Google who wrote your article, when, and for whom. The author link is the part that carries E-E-A-T, and most sites leave it out.
Use toolRead up on structured data
A tool tells you what is wrong. These explain what to do about it.
Technical SEO Audit Checklist 2026 (Free Template, 50+ Checks)
Read guideSEO Checklist for Blog Posts 2026 (Free Template, Pre & Post Publish)
Read guideEcommerce SEO Checklist 2026 (Free Template, Complete Store Optimization)
Read guideTerms this tool checks
- Schema Markup
Schema markup is a standardized vocabulary (developed by Schema.org and supported by Google, Bing, Yahoo, and Yandex) used to annotate web content with structured data.
- Structured Data
Structured data is code (typically JSON-LD format) added to web pages that helps search engines understand the content in a machine-readable way.
- Rich Results
Rich results (formerly called rich snippets) are enhanced search result formats that display additional visual information beyond the standard title, URL, and description.
Markup on one page, and the other nine hundred
A generator writes one block at a time. CrawlRaven crawls the whole site, finds the pages whose structured data is missing, invalid or contradicting the content on the page, and ranks them by the impressions behind each one, so the markup gets fixed where it earns something.