Home › Tools › Schema Markup Generator

Schema Markup Generator

Generate valid JSON-LD for Article, FAQ, HowTo, Product, BreadcrumbList and Organization. Fill in fields, get copy-ready markup that validates.

SerpPrism's JSON-LD Schema Markup Generator is a free online tool that builds valid structured data for Article, FAQ, HowTo, Product, BreadcrumbList, and Organization types — fill in the fields, get copy-ready markup that validates. There is no sign-up and generation runs in your browser. It is for site owners and developers who want rich-result eligibility without hand-writing JSON-LD and its error-prone syntax. Pick a schema type, fill in the fields, and get JSON-LD you can paste straight into your page head. Every field is validated as you type, and the output is checked for the properties Google actually requires.

How to use it

  1. Choose the schema type that matches what the page actually is — not the one you wish it were.
  2. Fill in the fields. Required ones are marked; the validator tells you what is missing as you type.
  3. Copy the JSON-LD and paste it into the <head> of your page, then test it in Google's Rich Results Test.

Structured data is a claim, not a ranking factor

Adding schema does not by itself move a page up. What it does is make your claims machine-readable: this is an article, it was published on this date, by this author, and this is the answer to this question. Systems that need that information can then use it.

The failure mode is claiming things that are not true of the page. Marking up an FAQ section that does not exist on the page, or a product the page does not sell, is a structured-data violation and can cost you eligibility for rich results entirely.

Why one @graph beats several loose blocks

Most generators emit one detached JSON-LD blob per type. That works, but it throws away the relationships: this article was published by this organization, on this website, and sits at this position in this breadcrumb trail.

Emitting a single @graph where nodes reference each other by @id expresses those relationships explicitly, and it is how the same facts stop being repeated in three places where they can drift apart. If your Organization name changes, you change it once.

Required versus recommended

Google treats some properties as required for a given rich result and others as recommended. Missing a required property means the result simply will not appear, with no error shown anywhere in Search Console.

This tool marks required fields and refuses to produce output that omits them. It does not warn about recommended fields, because those trade off against how much you want to describe.

A worked example: an Article block, field by field

Take a how-to article: headline 'How to Fix Subtitle Sync in VLC', author 'Hongtao Ren', published 2026-11-18, site 'SerpPrism'. The generator produces a single JSON-LD block — @context set to schema.org, @type Article, the headline as a plain string, the author as a nested object with its own @type of Person, datePublished in ISO form, and the publisher as an Organization object carrying the site name.

Leave dateModified empty if the article has never been revised. An invented date is worse than a missing one: a modified date that moves on every deploy tells crawlers the field is noise, and a date that claims a revision nobody made is a false claim in structured data.

The last step is verification, not trust. Paste the generated block into the JSON-LD Validator before it ships: the generator removes syntax errors by construction, but only the validator confirms the required fields for the type are all present.

Dates are the most common silent error

datePublished and dateModified need to be ISO 8601, and dateModified needs to mean something. Incrementing it on every deploy to make a page look fresh is a well-known trick that stops working the moment anyone compares it against the actual content.

Set dateModified when the content genuinely changes. A page whose modified date moves every day but whose words never change is telling crawlers the date field is noise.

Questions

Does schema help rankings?

Not directly. It makes your content eligible for rich results and helps systems understand what the page is. The ranking effect, if any, is indirect.

Where does the JSON-LD go?

Anywhere in the head or body. Google reads it regardless of position. The head is conventional and keeps it out of the way.

Can I use several types on one page?

Yes. Either as separate script blocks or, preferably, as one @graph with cross-referenced @id values so the entities are explicitly related.

Why does my FAQ rich result not appear?

Most often because the marked-up questions and answers are not visible in the page HTML, or the page is not indexed. Schema must describe content that actually exists on the page.

Which schema type should I use for my page?

Match the type to the content: Article for posts and news, Product for product pages, FAQ only for genuine question-and-answer pages, HowTo for step-by-step instructions, BreadcrumbList for navigation trails, Organization for your business entity. The generator lists the required and recommended properties for each type as you fill it in.

How do I check if my JSON-LD is valid?

Run the page or the pasted markup through Google's Rich Results Test or the Schema.org validator. The two most common silent errors are malformed dates and properties that describe content not visible on the page. Generating the markup field-by-field, as this tool does, removes the syntax errors; the validators catch the rest.

What is the difference between JSON-LD and microdata?

Both express the same schema.org vocabulary. Microdata weaves attributes through your HTML elements; JSON-LD keeps everything in one script block, separate from the visible markup. Google recommends JSON-LD because it is easier to add, audit, and remove — it is the only format the generator outputs.

Does the generator cover every schema.org type?

No — six types: Article, FAQPage, HowTo, Product, BreadcrumbList and Organization. They cover the pages most sites actually publish. Anything else needs hand-written JSON-LD, which the validator can check.

What happens if I leave a required field empty?

The tool flags the missing field above the output, and the generated JSON-LD carries the field empty. Fill in every field marked required before you paste the block into a page.

Related tools

Related guides