Schema generators

How to use it

1. 1Fill in the formChoose the type you are describing — article, product, organisation, breadcrumb and five more — then fill in that type's fields. Nothing is sent anywhere: the file is built in your browser from what you type.
2. 2Fill in the required fields the form marksEach type has properties without which the block is not understood. They are marked, and a missing one is a warning above the output rather than invalid code you find out about later.
3. 3Use ISO dates and plain numbersA date that is not ISO 8601 is left out and named rather than emitted broken, and a formatted price like "$19.99" is refused because the currency symbol invalidates the whole Offer. Free software needs price 0, which almost everyone gets wrong.
4. 4Notice there is no aggregate rating fieldThat absence is the product decision this tool is built around. A form for it invites "4.8 from 214 reviews" onto pages with no reviews, which is what manual actions are issued for.
5. 5Paste the block into the page it describesStructured data must match what a visitor can actually see. Markup describing a product that is not on the page is the other way sites get penalised.
6. 6Read the warnings before you copy anythingWarnings appear ABOVE the generated code on purpose. A caution printed underneath output somebody has already copied has not been communicated, and the mistakes this tool warns about are the expensive kind.
7. 7Copy or download the fileEach output block has its own Copy and Download button, so you can take one file without the other. Paste it where the block says it belongs.

About this tool

Structured data is how you tell a search engine what a page is about in a form it does not have to guess at: this is an article, published on this date, by this author; this is a business at this address; these are the steps from the home page to here. Choose a type, fill in the facts, and this generates the JSON-LD to paste in.

It is the counterpart to our structured data validator, which reads markup against Google's documented requirements. Same requirements, pointed the other way — so what comes out of here passes there. Everything runs in your browser; nothing you type is sent anywhere.

Understanding the result

The output is a complete <script type="application/ld+json"> block. JSON-LD does not have to sit near the content it describes, so it can go anywhere in the head or body.

Warnings appear above the code. Some are limits (a headline over 110 characters gets truncated); some are corrections (a price of "₹1,299" is refused rather than emitted as a broken Offer, because a formatted price makes the whole markup invalid).

A value that cannot be used is left out and named, never emitted broken — consumers skip malformed fields silently, so you would otherwise never learn it was wrong.

Example

Type: LocalBusiness · name: Roftr Clouds LLP · Kochi, Kerala

{
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "name": "Roftr Clouds LLP",
  "address": { "@type": "PostalAddress", "addressLocality": "Kochi" }
}

Limitations

• There is deliberately no rating field. Self-declared star ratings on pages with no reviews are the most-abused pattern in structured data and a manual-action risk; a site with real reviews should emit ratings from its review system, not from a form.
• Markup is generated, not validated against your live page. Once it is live, run the structured data validator — and Google's own Rich Results Test — to confirm it matches what is published.
• Valid markup makes a rich result possible, never certain. Google decides whether to display one and guarantees nothing.
• The types covered are the ones Google documents requirements for. Schema.org has hundreds more; those are valid but carry no rich-result treatment.

Questions