Structured data without the syntax headaches
This generator builds valid JSON-LD structured data for the schema types you actually use. Hand-writing nested JSON-LD is error-prone — a missing comma or wrong @type silently breaks rich results. Pick a type, fill in your data, and copy a clean <script type="application/ld+json"> block that validates.
How it works
JSON-LD describes your page using the schema.org vocabulary inside a script tag. Every object needs a @context (the vocabulary) and a @type (what the thing is), then type-specific properties:
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{ "@type": "Question", "name": "Q?",
"acceptedAnswer": { "@type": "Answer", "text": "A." } }
]
}For list types the tool builds arrays: FAQPage maps each Q | A line to a Question/Answer pair, and BreadcrumbList maps each Name | URL line to a positioned ListItem. All values are JSON-escaped so quotes and special characters in your text stay valid.
The five schema types and when to use each
Organization — add this to your homepage or about page to tell search engines your official name, URL, logo, and contact information. It helps establish your brand as a known entity in Google’s Knowledge Graph, which can trigger a knowledge panel in search results.
Article — add this to blog posts and news articles. The key fields are headline, author, date published, and date modified. Keeping the dateModified field updated is important because it signals to crawlers that the content is actively maintained.
Product — add this to product pages in an e-commerce context. The offers property inside a Product schema can trigger price and availability information directly in search results, making it one of the highest-value schema types for retail sites.
FAQPage — add this to pages containing question-and-answer content. It is one of the types most likely to generate a rich result, where the questions and answers expand directly in the search listing. The format for this generator is one Question | Answer per line, separated by a pipe character.
BreadcrumbList — add this to any page that sits inside a navigational hierarchy. It generates breadcrumb links in search results, which can improve click-through rates by showing users exactly where in the site a page sits. The format is Label | URL per line.
Where to place the script tag
JSON-LD can go in the <head> or anywhere in the <body>. Google’s documentation recommends the <head> as a best practice, but placement elsewhere is valid and parsed correctly. The advantage of JSON-LD over inline microdata is that the markup is entirely separate from your visible HTML, which means you can update it without touching the rendered content and test it independently.
Validation before you deploy
Always validate your generated markup before it goes live:
- Google Rich Results Test — shows which rich results your page is eligible for based on the structured data it contains. Required before assuming you will get a rich result.
- Schema Markup Validator (validator.schema.org) — checks that your markup is well-formed against the schema.org vocabulary, independent of Google’s eligibility criteria.
- JSON validator — a basic JSON lint check catches syntax errors like missing commas that break parsing silently.
A page with invalid structured data is not penalised, but it also receives no benefit. Valid data makes you eligible; Google then decides independently whether to show a rich result based on content quality and policy.