Common Schema types
Organization, website, article, product, local business, FAQ and breadcrumbs.
Choose an entity type, enter facts shown on the page and generate valid JSON-LD.
JSON-LD code
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization"
}
</script>Structured data and entities
Schema.org structured data describes page entities in machine-readable fields. JSON-LD can express authors, offers, logos, FAQs and breadcrumb relationships.
Markup must match visible content. Never invent reviews, prices or availability. Valid code does not guarantee a rich result.
Organization, website, article, product, local business, FAQ and breadcrumbs.
Review required values, absolute URLs, price, dates and duplicates.
Output a deployable script with @context and @type.
Each Schema type needs different fields. Generic templates often omit properties, use relative URLs or conflict with visible content.
Handle quotes, arrays, nested objects and script wrapping automatically.
Show relevant inputs and flag obvious missing or invalid values.
Preview complete JSON before publishing it on the page.
The form is converted to JSON-LD entirely in the browser. No external API is called and inputs are not stored.
Select Organization, Article, Product or another page subject.
Add names, URLs, images, dates, prices or questions shown on the page.
Fix missing fields, invalid URLs, duplicate items and format issues.
Add it to HTML, then check the actual live output.
Yes. Related entities may be separate or connected in @graph, but avoid duplication and conflicts.
Search engines heavily restrict FAQ rich results, but accurate visible FAQ markup can still provide machine-readable meaning.
A Product can exist without an Offer. If an Offer is included, provide real price, currency, availability and landing URL.
Either is generally acceptable when crawlers can receive it and the data matches visible content.
Yes. Templates, escaping and dynamic data can change the final page output.
Validate live JSON-LD, metadata, canonical and crawl state after publishing.