Schema Markup Generator
Generate JSON-LD schema that actually earns a rich result
Build structured data for ten rich-result types from a form, and see live whether Google will actually show the rich result, not just whether the JSON is valid. Preview the result, paste existing markup back in to fix it, and link several entities into one @graph. Nothing leaves your browser.
- 100% free
- No sign-up
- Nothing uploaded
- Runs in your browser
Structured data is what turns a plain blue link into a rich result: the star ratings, the FAQ dropdowns, the business card in the sidebar, the breadcrumb trail. The trap is that valid JSON-LD and markup that actually earns a rich result are two different things. A generator can hand you perfectly valid JSON that Google will never show, because a field it requires is missing, and since nothing throws an error you find out weeks later that the rich result never appeared. Most free generators stop at valid. This one tells you the difference as you type.
What it does, and why it's built this way
Valid is not the same as eligible
Every rich result has fields Google requires and fields it merely recommends. Leave out a required one and the markup is still valid JSON, it just quietly does not qualify. As you fill the form, an eligibility meter separates the two: it names the fields still needed for the rich result and the ones worth adding to make it stronger, so you never ship valid markup that was never going to show.
The types that actually earn a result
There are hundreds of schema types and most do nothing visible. This tool covers the ten that produce a visible win: Organization and Local Business for your brand and premises, Article, Product with price and star ratings, Event, Video, Job Posting, Recipe, FAQ and Breadcrumbs. It is also honest about where the ground has shifted. Google restricted FAQ rich results in 2023 to a handful of authoritative sites, and the tool says so rather than selling you markup that will not show.
See it before you ship it
Alongside the markup you get a live preview of the result: the stars, the FAQ dropdown, the breadcrumb trail, the job card, roughly as they can appear in search. You can paste existing JSON-LD, yours or a competitor's, back into the form to fix it instead of hand-editing JSON. And when a page carries several entities, you can link them into one connected @graph the way real sites do, rather than scattering loose script tags.
How to use it
- 1
Pick the type
Choose what the page is: an organization, a local business, an article, a product, an event, a video, a job, a recipe, an FAQ, or a breadcrumb trail. Each has its own small set of fields.
- 2
Fill the fields and watch the meter
Required fields are marked, and the eligibility meter tracks how close you are to a rich result, naming anything still missing. Fill only what you have; empty fields are dropped, not emitted as blank keys.
- 3
Check the live preview
The preview shows how the result can look in Google as you type, so you can see the payoff before the page is even live.
- 4
Copy the script tag
Copy the complete script tag into the head of the matching page, or add several entities to the page bundle for one @graph. Then confirm the live page with Google's Rich Results Test.
Common mistakes
Shipping valid markup that is not eligible
Valid JSON-LD can still fail to earn a rich result if a required field is missing. This is the quiet failure the eligibility meter is built to catch: check that it reads eligible, not just that the JSON is clean.
Markup that does not match the page
The structured data has to describe what is actually on the page. FAQ schema with questions a visitor cannot see is against the guidelines and can earn a penalty. Mark up what is really there.
Expecting an FAQ rich result on an ordinary site
Google narrowed FAQ rich results in 2023 to well-known government and health sites. The markup is still valid and still useful for accessibility and AI answers, but do not count on the dropdown appearing in Search for a typical site.
One schema block for the whole site
Schema is per page. Your homepage gets Organization, a blog post gets Article, a location page gets Local Business. Pasting the same block everywhere is worse than none.
Frequently asked questions
- Does schema markup improve my ranking?
- Not directly. It makes your result richer and more clickable, which lifts click-through, and it helps engines understand the page. Think of it as improving how you appear, not where you appear.
- What does the eligibility meter check?
- It compares your input against Google's required and recommended fields for that type. Required fields decide whether the rich result can show at all; recommended fields make it stronger. The meter names whatever is still missing so you are not guessing.
- Can I edit schema I already have?
- Yes. Paste an existing JSON-LD snippet or a whole script tag, from your site or a competitor's, and the tool loads it back into the form so you can correct it instead of editing raw JSON by hand.
- What is the @graph option for?
- When a single page carries several entities, an Organization plus an Article plus a Breadcrumb, real sites connect them into one @graph with shared ids rather than pasting separate blocks. Add each entity to the page bundle and the tool builds that connected graph for you.
- How do I check it worked?
- Google's Rich Results Test takes a URL or a snippet and tells you which rich results the page is eligible for. Use it after you paste the markup, and again once the page is live.
Need this done properly, at scale?
The tool handles the one-off. When it's a system you're building, that's the paid version of the job, and we do that too.
SEO Services