JSON-LD Schema Generator
Build structured data (Article, Product, FAQ, Organization) as JSON-LD.
Schema Type: ArticleScript Size: 0 BFields Configured: 0
JSON-LD Output
Structured data with JSON-LD
JSON-LD is Google's recommended format for structured data — a <script type="application/ld+json"> block you drop into your page's <head>. It helps search engines understand your content and can unlock rich results — star ratings for products, expandable FAQs, article bylines, and business info. Fill in the fields above (blank ones are omitted), paste the output into your page, then validate it with Google's Rich Results Test. Generation is 100% client-side.
Built and maintained by Meet Shah · Last updated
What this tool is used for
- Building structured data for an article, product, FAQ or organisation page.
- Producing a block with the properties a rich result requires.
- Generating a starting point you then extend by hand.
- Producing consistent markup across a set of pages.
- Comparing generated output against a page's existing block.
Frequently Asked Questions
- Why JSON-LD rather than microdata?
- Because it lives in one `<script>` block instead of being woven through your markup. Google explicitly recommends it, and the practical argument is maintenance: a redesign that moves the price into a different component cannot silently break structured data that was never attached to the DOM.
- Where should the script tag go?
- Either `<head>` or `<body>` — Google reads both, and it can be injected by JavaScript as long as it exists by the time the page finishes rendering. `<head>` is conventional; what matters far more is that exactly one block describes each entity rather than several disagreeing ones.
- Does structured data improve my ranking?
- Not directly — Google is clear that it is not a ranking signal. What it does is make a page eligible for rich results: star ratings, FAQ accordions, recipe cards. Those change the click-through rate, which is a real effect on traffic reached by a different mechanism.
- What is @context and why is it always the same URL?
- It maps the short property names to full vocabulary URIs, and `https://schema.org` is that vocabulary. JSON-LD is a serialisation of RDF, so `"name"` is really shorthand for a globally unique identifier — the context is what makes the abbreviation unambiguous.
- Can I mark up content that is not visible on the page?
- No, and doing it is a documented spam policy violation. Structured data must describe what a user actually sees; a rating in the markup that appears nowhere on the page is grounds for a manual action that removes rich results across the whole site.
Common errors and gotchas
- Marking up content the page does not display, which the guidelines prohibit.
- Adding FAQ markup to a page whose questions are not visible to a reader.
- Using an approximate date format rather than the ISO form the parser expects.
- Producing several blocks that describe the same entity differently.
- Treating eligibility as a guarantee, when Google decides whether to show a rich result.
Related Web & SEO tools
Meta Tag Generator
Build SEO title, description, and viewport meta tags.
Open Graph Generator
Generate Open Graph and Twitter Card meta tags.
Robots.txt Generator
Build a robots.txt file with per-bot rules. Block AI crawlers, set crawl delays, define sitemaps.
UTM Campaign URL Builder
Append UTM parameters to build trackable campaign URLs.
Hreflang Tag Generator
Generate hreflang link tags for multilingual SEO.
Sitemap XML Generator
Build an XML sitemap from a list of URLs.
SERP Snippet Preview
Preview how your page title and meta description appear in Google search.
Meta Tag Analyzer
Paste a page's HTML head to audit its title, meta, and social tags.