Schema Markup Generator
Fill in a short form and get valid JSON-LD structured data for nine schema.org types: Organization, LocalBusiness, Article, Product, FAQPage, HowTo, BreadcrumbList, Event and WebSite (sitelinks search box). Fields are marked required or recommended as in Google's rich-result documentation; URLs, dates, prices and codes are checked as you type; the output is ready to paste into <head> and to test in Google's Rich Results Test. Runs in your browser, nothing stored.
Findings (0)
No findings — every required and recommended field is present and well-formed.
JSON-LD
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Example GmbH",
"url": "https://www.example.com/",
"logo": "https://www.example.com/logo.png",
"description": "Example GmbH builds measurement tools for marketing teams.",
"telephone": "+49 30 1234567",
"email": "hello@example.com",
"sameAs": [
"https://www.linkedin.com/company/example",
"https://x.com/example"
],
"address": {
"@type": "PostalAddress",
"streetAddress": "Musterstraße 12",
"addressLocality": "Berlin",
"addressRegion": "BE",
"postalCode": "10115",
"addressCountry": "DE"
}
}
</script>Test it
The generator checks shape, not Google's verdict. Paste the output into Google's Rich Results Test to see whether a rich result is detected and which properties it flags, and into the Schema.org validator for vocabulary checks.
Everything runs in your browser — no request leaves the page and nothing is stored. Required and recommended labels follow Google's structured-data documentation as of September 2026; the generator reports what is missing or malformed and does not decide which types a page should carry.
How it works
1. Pick a type — Organization, LocalBusiness (with a subtype such as Restaurant or Dentist), Article / NewsArticle / BlogPosting, Product with Offer and AggregateRating, FAQPage, HowTo, BreadcrumbList, Event or WebSite with SearchAction
2. Fill the form — every field is labelled required, recommended or optional following Google's structured-data documentation for that type; the page opens with a worked example
3. Values are checked as you type: absolute http(s) URLs, ISO 8601 dates and date-times (with a timezone warning), ISO 8601 durations (PT10M), numbers, three-letter ISO 4217 currency codes, GTIN length (8/12/13/14 digits), e-mail shape, the {search_term_string} placeholder in a search target
4. The JSON-LD is assembled from what you filled: empty fields are left out rather than emitted blank, nested objects (PostalAddress, Offer, GeoCoordinates, Person, Place, HowToStep, ListItem…) get their @type, enumerations become their https://schema.org/ URLs
5. Findings list what is missing or malformed — a missing required field is an error, a missing recommended field a warning, a cosmetic issue an info line; the generator never fills a gap with a guess
6. Copy the <script type="application/ld+json"> block into the page's <head>, then verify it with Google's Rich Results Test and the Schema.org validator — the generator produces the markup, those tools confirm Google can read itAbout structured data and what the generator checks
Structured data is a machine-readable description of what a page is about, written in the schema.org vocabulary and, in practice, embedded as JSON-LD — a <script> block that browsers ignore and search engines read. It does not change ranking by itself; it makes the page eligible for rich results (review stars, product prices, event dates, breadcrumbs, a sitelinks search box) and gives crawlers and AI answer engines unambiguous facts: this is the price, this is the author, this is the address. Google recommends JSON-LD over Microdata and RDFa because it lives in one place and does not have to be woven into the HTML.
Each rich result has its own required and recommended properties, and those come from Google's documentation rather than from schema.org, which allows almost anything. The generator marks fields accordingly: required means Google will not show the rich result without it, recommended means the result may still appear but with less detail. Values must also be in the right shape — dates and times in ISO 8601 with a timezone, prices as numbers with a separate ISO 4217 currency, URLs absolute, images reachable and, for Article, ideally in several aspect ratios. The generator checks the shape; it cannot check that the image exists or that the price matches the page, which is what Google's tools and, eventually, Google's crawler verify.
Coverage of rich results has narrowed since 2023: FAQ rich results are now limited to well-known government and health sites, and HowTo rich results were removed from Search. Both types remain valid schema.org markup and are still read as page-level signals, so the generator keeps them, with a note on each. The rule that has not changed is that markup must describe visible content — a FAQ block in JSON-LD that is not on the page, or a rating no user can see, is a spam-policy violation rather than an optimisation.
One page can carry several JSON-LD blocks — an Organization on the home page, BreadcrumbList on every page, Product on product pages — and they can be separate <script> elements or one array. The generator produces one type at a time; run it again for each. It reports what it found in the form and does not suggest which types a site should use; that follows from what the page shows.
Frequently asked questions
- Does structured data improve rankings?
- Not directly. Google has said structured data is not a ranking factor. It makes a page eligible for rich results, which can raise click-through rate, and it removes ambiguity about facts on the page for search engines and AI answer engines. Whether the rich result actually shows is Google's decision, made per query.
- JSON-LD or Microdata?
- JSON-LD. Google recommends it, it lives in a single <script> block that can be generated server-side or injected by a tag manager, and it does not depend on the HTML structure. Microdata and RDFa are still supported but harder to maintain. This generator emits JSON-LD only.
- Where do I put the code?
- Inside the page's <head> or <body> — Google reads both; <head> is the convention. Paste the whole <script type="application/ld+json"> block unchanged. If a tag manager injects it, make sure it fires on the page load, not on a later interaction, so the crawler sees it in the rendered HTML.
- Why are FAQ and HowTo marked with a note?
- Since August 2023 Google shows FAQ rich results only for authoritative government and health sites, and in September 2023 it removed HowTo rich results entirely. The markup is still valid schema.org and still describes the page, so the generator keeps both types — with the note so nobody expects a rich result that will not appear.
- Can I add a rating to a Product without reviews on the page?
- No. Google's structured-data policies require that marked-up ratings and reviews be visible on the page and collected from real users. AggregateRating that is not backed by visible reviews can lead to a manual action. The generator only emits AggregateRating when both a rating value and a review count are given, and it cannot verify the reviews exist.
- What does 'missing timezone' mean on a date?
- An ISO 8601 date-time like 2026-09-16T09:00 has no offset, so Google guesses the timezone from other signals. Add it explicitly: 2026-09-16T09:00:00+02:00, or Z for UTC. A date alone (2026-09-16) is fine for datePublished; Event start dates should include the time and offset.
- How do I test the output?
- Paste it into Google's Rich Results Test to see whether Google detects a rich result and which required or recommended properties it flags, and into the Schema.org validator for vocabulary-level checks. After publishing, the URL Inspection tool in Search Console shows what Google actually crawled, and the Enhancements reports track errors across the site.