What the generator produces
You choose one of five schema.org types, fill a few fields, and the tool wraps the result in a <script type="application/ld+json"> block ready to paste. JSON-LD is the format Google recommends because it sits apart from your visible HTML, so it is easy to add and maintain. Each type exposes only a handful of fields, so treat the output as a correct starting skeleton rather than a complete, fully-featured markup.
The five types and what each field maps to
| Type | Fields in this tool | Notes |
|---|---|---|
| FAQPage | Question, Answer | One Q&A per generation |
| Article | Headline, Author, Image URL, Date published (YYYY-MM-DD) | Author is output as a Person; date is omitted if blank |
| Organization | Name, URL, Logo URL | Best placed on your homepage or about page |
| Product | Name, Description, Price, Currency | Wraps price in an Offer; currency defaults to USD |
| BreadcrumbList | Level 1 to Level 3 | Names and positions only, no URLs |
Which types still earn rich results
This matters more than generating the markup. In 2023 Google restricted FAQ rich results to well-known, authoritative government and health sites, so for most sites FAQPage markup no longer shows expandable questions in search. It remains valid and harmless, and other engines and AI systems may read it. HowTo rich results were deprecated the same year, which is why this tool does not offer HowTo. Breadcrumb markup can still replace the raw URL in the result with a readable trail. Product markup can show price and availability when it includes an offer, review or rating. Organization markup helps Google understand your entity and logo but is not guaranteed to produce a visible feature. Article markup has no dedicated rich result for most publishers, but supplies clean headline, author and date signals.
Worked example
Choosing Product with name "Trail Pack 30L", description "Lightweight hiking backpack.", price 89.00 and currency EUR produces:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Product",
"name": "Trail Pack 30L",
"description": "Lightweight hiking backpack.",
"offers": {
"@type": "Offer",
"price": "89.00",
"priceCurrency": "EUR"
}
}
</script>Common mistakes and limits to know
- Markup that does not match the page. Structured data must describe content visible to users. Marking up a price or answer that is not on the page risks a manual action.
- Needing more than one FAQ. The generator emits a single question. For several, copy the Question object and add more entries inside the
mainEntityarray by hand. - Breadcrumbs without URLs. Google expects an
itemURL on each breadcrumb except the last. Add those properties before publishing. - Empty optional fields. A blank Image or Logo URL is still written as an empty string, so fill them or delete the line.
- Skipping validation. Always run the result through Google's Rich Results Test and the Schema Markup Validator. Eligibility is not a promise of display.
For the broader picture of structured data alongside Open Graph, read the structured data and Open Graph guide. If you want to inspect or tidy the generated JSON, the JSON formatter is a quick way to do it.