Schema / JSON-LD Generator
Everything runs locally in your browser — nothing is sent to Google or any server, this only builds the JSON-LD markup.
How to use this Schema/JSON-LD generator
- Pick the schema type that matches your page content.
- Fill in the fields — required fields are marked with an asterisk (*).
- Copy the generated script tag into your page's head.
What is JSON-LD structured data?
JSON-LD is a way to describe your page's content in a machine-readable format that search engines use to understand context and, in some cases, show enhanced results like star ratings, FAQ dropdowns, or recipe cards directly in search. This tool builds valid markup and checks that the fields required by each type are filled in, but doesn't submit anything to Google to verify eligibility for rich results.
Does filling in every field guarantee rich results in Google?
No — valid structured data is necessary but not sufficient. Google decides whether to show rich results based on its own quality guidelines and may ignore markup even when it's technically correct. Test your final page with Google's Rich Results Test for eligibility, not just validity.
What does the required field check actually verify?
Only that the fields schema.org and Google commonly require for that type aren't empty — it doesn't check formatting like whether a date follows ISO 8601 or a URL is reachable. Always double-check the output before publishing.
What JSON-LD actually is (and isn't)
JSON-LD structured data lives inside a <script type="application/ld+json"> tag and never affects what a visitor sees on the page — it's a separate, parallel description of the page's content in a standardized, machine-readable format, sitting alongside (not replacing) the actual visible HTML. Search engines parse this block to understand what a page is about with more precision than they could infer from visible text alone: that a particular number is a price rather than just a number, that a name is an author rather than incidental text, that a list of questions is specifically a FAQ rather than generic prose. It's purely additive information for machines, not a substitute for well-written, visible content.
Rich results aren't guaranteed — and some schema types have lost their search-result reach
Adding valid structured data has never guaranteed a special search result appearance, and it's worth knowing that eligibility for certain rich result types has narrowed significantly in recent years. Google discontinued HowTo rich results in search entirely in 2023, and restricted FAQ rich results around the same time to a narrow set of established, authoritative government and health sites, rather than showing them broadly as before. This doesn't mean adding HowTo or FAQPage markup is pointless — the underlying schema.org markup still has value for other consumers of structured data, including AI-assisted search and answer systems that parse page content differently than classic search rich results ever did — but it does mean you shouldn't add either type today specifically expecting the search-result appearance those types used to enable.
Why structured data still matters beyond classic rich results
Structured data's audience has broadened even as some traditional rich-result formats have narrowed. AI-powered search and answer features increasingly rely on parsing a page's content to generate direct answers, and clearly marked-up structured data gives these systems an unambiguous, machine-readable summary of a page's key facts to draw from, separate from whatever rich-result eligibility a specific schema type carries in classic search. Organization and Product schema also feed into a search engine's broader knowledge graph — helping establish entity relationships (this business, at this address, offering this product) — independent of whether any specific visual enhancement appears in results for a given search.
Required-field validity vs. real-world rich-result eligibility
This tool's required-field check confirms that the fields schema.org and Google's own documentation commonly expect for a given type aren't left empty — it's a syntactic and completeness check, not a guarantee of anything beyond "this markup is well-formed and complete enough to be parsed correctly." Actual eligibility for a rich result additionally depends on Google's separate content quality policies: a Product schema with a rating needs that rating to reflect real, verifiable reviews rather than fabricated numbers, and eligibility can be revoked site-wide if Google's quality systems find markup that misrepresents a page's actual visible content. Passing this tool's field check is a necessary first step, not the final word on eligibility.
Limitations of this tool
This generator checks that required fields for each schema type aren't empty, but it doesn't validate formatting details like whether a date follows the ISO 8601 standard, whether a URL is actually reachable, or whether numeric fields (price, rating, duration) are in a sensible range — those checks require pasting the final output into Google's own Rich Results Test or the Schema.org validator. It also builds one schema block at a time rather than combining multiple types into a single @graph structure, and doesn't cover every schema.org type that exists — just the handful most commonly used for SEO purposes (Article, Product, FAQPage, HowTo, LocalBusiness, Organization).