Schema generator. Six types. Valid JSON-LD.
Fill a form, get copy-ready JSON-LD that validates against schema.org and Google Rich Results. Article, Product, FAQPage, LocalBusiness, Event, and BreadcrumbList. No signup, no server.
Article schema inputs.
Copy-ready.
Sources used by the inline validator
- schema.org/Article · Google Article required fields
- schema.org/Product · Google Product required fields
- schema.org/FAQPage · Google FAQPage required fields
- schema.org/LocalBusiness · Google LocalBusiness required fields
- schema.org/Event · Google Event required fields
- schema.org/BreadcrumbList · Google Breadcrumb required fields
Schema is the machine-readable translation.
Structured data is a JSON-LD script tag that translates your page into the vocabulary search engines and AI systems can parse reliably. A human reader sees an article with a headline, an author, and a date; a machine reader without schema guesses at those fields by heuristics. A machine reader with Article schema reads them from labeled properties. The difference shows up in rich results, knowledge-panel eligibility, and increasingly, AI citation rates. Schema is not optional for pages you want cited.
Six types cover roughly 95 percent of real ecommerce and agency use cases: Article for editorial posts, Product for SKU pages, FAQPage for Q and A sections, LocalBusiness for store or office pages, Event for time-bound listings, and BreadcrumbList for site-hierarchy signals. Each maps to a Google rich-result format when eligibility criteria are met. The generator above outputs one type at a time; to ship multiple on a single page, wrap them in an @graph array.
Validation before publishing is not optional. The generator above runs an inline validator on demand — required-field check, ISO-8601 date format, ISO-4217 currency, ISO-3166 country, URL syntax, type-specific structural rules — entirely in your browser. No JSON is sent to any external service. The Sources panel under the output lists every schema.org type definition and required-field reference the validator checks against, so you can confirm what is being inspected. The validator runs against the same publicly-documented rule set the major external validators use; passing here means the JSON conforms to the spec.
Tools in the same cluster: Meta tag generator for the HTML head. OG preview for the social share view.
Five answers.
Which schema type should I pick for my page?
Pick by page purpose. A blog post or editorial piece gets Article. An ecommerce product page gets Product with offers and aggregateRating. A service page with Q and A sections gets FAQPage. A physical or online business page gets LocalBusiness with address and openingHoursSpecification. An event-listing page gets Event. Every page gets BreadcrumbList to describe its position in the site hierarchy. You can combine types on one page using a @graph array; the generator above outputs a single type at a time for clarity.
Does this schema validate against Google Rich Results?
Yes. Every output is built against the required properties Google publishes for that type. Article requires headline, datePublished, author, image, and publisher. Product requires name, image, offers (price + priceCurrency). FAQPage requires at least two Question items with acceptedAnswer. LocalBusiness requires name, image, and a complete address. Click "Run inline validator" above for a full per-field verdict that runs entirely in your browser — no JSON is sent anywhere. The Sources panel lists every type definition and required-field doc the validator references.
Why JSON-LD instead of Microdata or RDFa?
Google recommends JSON-LD as the preferred format since 2015. JSON-LD lives inside a single script tag in the head or body, which keeps markup separated from the rendered HTML. Microdata and RDFa embed attributes inside rendered tags, which is harder to maintain and more error-prone. Every major search engine parses JSON-LD. The output generated above is JSON-LD by default; microdata is available from schema.org for edge cases.
How do I add multiple schema types to one page?
Wrap both types in an @graph array. For example: context is schema.org, graph is an array containing one Article object and one BreadcrumbList object. Both parse correctly and both appear in Rich Results Test. Google explicitly supports this pattern. Generate each type separately above, then combine by hand inside the graph array. Do not nest types; keep them as siblings unless the schema spec explicitly requires nesting (Review inside Product, for example).
Does this tool save my data?
No. Every value you enter lives in memory for this browser tab only. Nothing is transmitted to a server, stored in a database, or synced. Close the tab and the data is gone. The Copy button puts the JSON-LD on your clipboard; that is the only output path. The tool uses localStorage optionally to remember your last schema type and saved form state; clear your browser data to reset.
One page. Not enough.
Our SEO engagements ship schema across every template (product, collection, article, location, FAQ) plus entity-level Organization schema with sameAs, aggregateRating, and knowsAbout. Written plan in 2 weeks.
Published · Last updated .