Draftcamp

Schema markup generator

Valid JSON-LD for articles, products, organisations and how-tos

Runs entirely in your browser - your text is never uploaded

Schema type

Fill in a field to generate JSON-LD

Fields Google requires for a rich result are marked, and missing ones are listed rather than silently dropped.

Structured data, and what it is actually for

Schema markup does not improve rankings. It is not a ranking factor and never has been. What it does is make a page eligible for a rich result - the star ratings, the FAQ accordions, the recipe cards - and rich results change how much of the search page you occupy. The gain shows up in click-through rate, not position.

Valid is not the same as eligible

This is the trap. schema.org's spec is permissive: an Article with only a headline is perfectly valid. Google's rich-result requirements are much stricter, and if you miss one of them Google parses your markup, finds it well-formed, and shows nothing. No error, no warning in Search Console, just no rich result.

So this tool marks fields against Google's requirements and lists what is missing rather than quietly omitting it.

Rules that get people penalised

  • Only mark up visible content. Prices, reviews and FAQ answers must appear on the page. Marking up invisible content is a policy violation and a common cause of manual actions.
  • One primary type per page. Stacking Article, Product and FAQPage on the same URL confuses selection rather than improving odds.
  • Keep dates honest. Bumping dateModified without changing anything is a freshness signal you have not earned.

For question and answer content specifically, the FAQ schema generator handles the nesting and escaping.

Common questions

Does schema markup improve rankings?
Not directly. Structured data is not a ranking factor. What it does is make a page eligible for rich results - star ratings, FAQ dropdowns, recipe cards - and those change how much of the result page you occupy and how many people click. The gain is in click-through, not position.
JSON-LD, Microdata or RDFa?
JSON-LD. Google explicitly recommends it, and it is the only one of the three that lives in a single block in the head instead of being woven through your markup. That means it can be changed without touching templates and cannot be broken by a design change.
What happens if a required field is missing?
The markup stays valid but becomes inert: Google will parse it and decline to show a rich result. That is the worst outcome, because everything looks fine. This tool lists the fields Google requires rather than the far looser set schema.org accepts.
Can I mark up content that is not visible on the page?
No. Structured data must describe content the user can actually see. Marking up prices, reviews or FAQ answers that are absent from the visible page violates Google policy and is a common cause of manual actions against structured data.
How do I test it?
Paste the output into Google Rich Results Test to confirm eligibility, and the Schema.org validator for spec conformance. They check different things: one asks "will Google show this", the other asks "is this correct".