Structured Data Generator

How this calculation works

Choose a type, fill in what you have, and the markup is assembled with the properties that type needs, wrapped in the script tag it belongs in. Empty fields are omitted rather than emitted as blanks, since an empty property is worse than an absent one. Recommended properties that are missing are listed, because they are usually what stands between eligible and ignored. JSON-LD goes in the head or the body — both work — and does not have to sit next to the content it describes, which is exactly why it is easy to let the two drift apart.

What the results mean

Required properties

Without them the markup is ignored for rich results entirely, silently. There is no warning anywhere.

Recommended properties

Not mandatory, and usually the difference between eligible and shown. Images and dates matter most.

@context

Tells the parser the vocabulary is schema.org. A block without it describes nothing at all.

JSON-LD

The format search engines prefer, separate from your markup rather than woven through it. That is its advantage and its risk.

Common problems and fixes

I added markup and nothing changed

Eligibility is not a guarantee. Confirm the page is indexed, that required properties are present, and then wait — rich results appear on the engine's schedule, not on deployment.

The markup describes content the page does not show

Fix that before anything else. Marking up invisible reviews or prices is a manual-action risk, and it is one of the few structured-data rules that gets actively enforced.

Which page should the markup go on?

The page it describes, one block per entity. Product markup belongs on the product page, not the category listing.

Frequently asked questions

More in SEO

• Structured Data ValidatorCheck JSON-LD for the errors that make search engines discard it silently.
• SERP Snippet PreviewSee where a title and description get cut — measured in pixels, as search results are.