Developer Schema markup generator
Generate valid JSON-LD for Organization, LocalBusiness, Article, Product, FAQPage and BreadcrumbList, ready to paste into your head.
Absolute URL. Feeds the knowledge panel.
Two letters, e.g. ID, US, GB.
JSON-LD
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization"
}
</script>Paste this into the <head> of the page it describes. Structured data must match visible page content: marking up a price or a review that a visitor cannot see is a spam policy violation and can cost you rich results across the whole site. Validate with Google’s Rich Results Test and the Schema.org validator before publishing.
Ready. Runs locally on your device.
Your files stay on your device. The tool works directly in your browser, using your device to process your files. Nothing is sent to our servers, and we never receive, store, or see your files or figures.
Share result
Cite
Cite this page
Reembun. (2026, July 28). Schema markup generator. https://reembun.com/schema-markup-generator
How to use it
Pick the type
Organization, LocalBusiness, Article, Product, FAQPage or BreadcrumbList. The form changes to the fields that type actually uses.
Fill in the fields
URLs have to be absolute. The output updates as you type, so you can see the shape of what you are building.
Copy the script tag
Copy script tag gives the whole JSON-LD block wrapped and ready to paste.
Put it on the right page
Structured data has to describe the page it sits on. Paste it there, then check it in Google's Rich Results Test.
Why JSON-LD
Three formats express structured data. Google recommends JSON-LD, and it is the right choice for practical reasons:
| Format | Where it lives |
|---|---|
| JSON-LD | A <script> tag, separate from the markup |
| Microdata | Attributes scattered through the HTML |
| RDFa | Attributes scattered through the HTML |
Because JSON-LD is separate, it can be generated server-side and updated without touching templates, and a change to the visual markup cannot accidentally break it.
What still earns rich results in 2026
| Type | Status |
|---|---|
| BreadcrumbList | Breadcrumb trail in results |
| Product | Price, availability, review stars |
| Recipe | Image, rating, cook time |
| Event | Date, venue, ticket link |
| VideoObject | Thumbnail, duration, key moments |
| JobPosting | Google Jobs listing |
| Organization | Knowledge panel signals |
| FAQPage | No longer rendered |
| HowTo | Deprecated 2023 |
The last two are worth stating plainly because a great deal of SEO advice still recommends them for rich results. Google restricted FAQ to authoritative government and health sites in August 2023, then removed the feature entirely, dropping support from the Rich Results Test in June 2026. The markup remains valid and is still parsed, which is useful for AI answer engines, but it will not win you a larger listing.
Organization and LocalBusiness
Best placed on the homepage and, if you use one, referenced from every other page by @id. The logo property is what feeds brand treatments and knowledge panels.
LocalBusiness is a subtype of Organization that adds address, opening hours and geographic properties. Use it if you have a physical location customers visit; use Organization if you do not.
Article
headline, datePublished and author are the properties that matter. Google has stated it uses datePublished and dateModified as signals for freshness, and inaccurate dates are treated as a quality problem, so updating a date without updating the content is a bad idea.
Product
Rich results here need a genuine offers block with price, priceCurrency and availability. Review markup needs real reviews visible on the page. Self-serving review markup, where a business marks up its own aggregate rating without displaying it, has been ineligible for rich results since 2019.
BreadcrumbList
The lowest-effort, highest-certainty item on this list. It replaces the raw URL in the result with a readable trail, it is simple to generate from your site structure, and it still renders reliably.
Rules that matter
Mark up what is visible. Structured data describing content a visitor cannot see violates Google’s policies. This is the most common cause of a manual action for structured data, and the penalty applies site-wide rather than to one page.
Keep it in sync. A price in the markup that no longer matches the page is worse than no markup.
Validate before publishing. Google’s Rich Results Test shows what Google can parse and which enhancements it qualifies for. The Schema.org validator checks vocabulary correctness more broadly. Use both, since they catch different problems.
One graph per page. Multiple script tags are legal, but a single @graph array with @id references between nodes is easier to keep consistent.
Common questions
Which schema types still produce rich results?
Breadcrumb, Product with offers and reviews, Recipe, Event, Video, JobPosting and a handful of others still render enhancements. FAQ and HowTo do not. FAQ was restricted to government and health sites in 2023 then removed entirely, and HowTo was deprecated the same year.
Should I still add FAQPage markup?
Only if the Q&A is genuinely on the page. It earns no SERP real estate now, but it is still parsed and can help AI answer engines understand the content. Adding it purely as a ranking tactic is wasted effort.
JSON-LD, Microdata or RDFa?
JSON-LD, which Google explicitly recommends. It sits in a script tag separate from the markup, so it can be generated and updated without touching the template, and it does not clutter the HTML with attributes.
Can structured data get me penalised?
Yes. Marking up content that is not visible to a visitor, such as prices, reviews or ratings that appear only in the markup, violates Google's structured data policies and can cost rich results across the entire site, not just the page. Structured data must describe what is actually there.
Last reviewed
