Overview
What this tool does
Schema.org JSON-LD is structured data Google reads to enrich your search-result listings: star ratings on products, FAQ accordions, author bylines on articles, opening hours on local businesses, and so on. Adding it correctly is the difference between a plain blue link and a visually rich result that gets noticeably more clicks. This builder covers five of the most common schema types: Article, Product, FAQPage, LocalBusiness, and Organization. Fill the form, copy the resulting <script type="application/ld+json"> tag, paste it into your page's <head>. 100% client-side; no signup, no upload.
How to
Use it in 3 steps
- Pick the schema type that matches your page (Article for a blog post, Product for a listing, FAQPage for an FAQ section, LocalBusiness for a brick-and-mortar, Organization for a company entity).
- Fill in the form. Empty fields are silently dropped from the output so you only ship what you actually have.
- For FAQ pages, list each question + answer exactly as they appear on the page (Google checks for an exact text match before showing the rich result).
- Copy the resulting <script> tag from the right column and paste it inside your page's <head>.
- Validate the output at Google's Rich Results Test (link under the output) before pushing to production.
FAQ
Frequently asked questions
▶Will this guarantee rich results in Google?
No. Valid JSON-LD is a prerequisite, not a guarantee. Google decides which pages get rich treatment based on many signals (content quality, site authority, click-through history). Valid markup makes your page eligible.
▶Where does the <script> tag go?
Inside the <head> of your page, typically near the other meta tags. It can also live in <body>; Google reads either location. For server-rendered pages, set it in your template. For SPAs / single-page apps, inject it client-side before initial paint.
▶Why are empty fields removed from the output?
Schema.org technically accepts empty values but Google sometimes penalises markup with placeholder/empty data. We compact-strip nulls and empty strings so what you see is what you ship. Don't make up fake values to fill required fields; just leave them out.
▶What's the difference between Article and Product?
Article is for editorial content (blog posts, news, opinion). Product is for items for sale (with price, currency, availability, ratings). Don't put product schema on a blog post or vice versa; Google will flag it as misleading markup.
▶Can a page have multiple JSON-LD blocks?
Yes. A common pattern is one Organization block site-wide, plus a per-page Article or Product block. Just include multiple <script type="application/ld+json"> tags, one per entity.
▶Why FAQPage with only my actual on-page Q&As?
Because Google requires the JSON-LD to match the visible page content. Don't list FAQs in the JSON-LD that aren't on the page; Google will reject the markup as deceptive and may suspend your site's rich-result eligibility.