JSON-LD Generator

How it works

Two tabs. Generate builds JSON-LD from a form: pick one of 17 types (Article, FAQPage, Person, Organization, LocalBusiness, Product, BreadcrumbList, WebSite, WebPage, Event, JobPosting, Recipe, Review, VideoObject, HowTo, SoftwareApplication, Service), fill the fields, copy the result with or without the <script type="application/ld+json"> wrapper. Empty fields get dropped from the output, so you never ship "image": "". Nested structures come out right: a Product with a rating gets a proper AggregateRating object, an Event wraps its venue in a Place.

Check goes the other way. Paste bare JSON-LD, a script-wrapped block, or an entire page source. The tool pulls out every ld+json block it finds, parses it, and validates against the required and recommended properties from Google's rich-results documentation. It walks @graph arrays too, which is where most CMS plugins hide their markup. Errors are things that break eligibility (missing headline on an Article); warnings are fields Google would like to see.

The checker covers the same 17 types plus the entities that usually hide inside them: Offer, AggregateRating, Rating, ListItem, ItemList. Nested objects get checked for their required fields too, so a Product whose Offer is missing priceCurrency gets flagged even though the Product itself looks fine. Common subtypes resolve to their parent's rules automatically: a BlogPosting validates as an Article, a Restaurant as a LocalBusiness. Anything it doesn't know gets a syntax check and an honest note saying so.

When to use it

• Adding FAQ or Article markup to a page without writing JSON by hand.
• Checking what your SEO plugin actually outputs. Paste the page source, see the entities.
• Debugging why a rich result stopped showing. Missing required field is the usual answer.

Does structured data still matter?

For rich results, yes: FAQ snippets, breadcrumbs, product prices in the SERP all depend on it. And AI search engines parse it too: a clean Person or Organization entity is one of the few machine-readable statements about who you are that you fully control. I wouldn't expect ranking miracles from it. I would treat broken markup as leaving money on the table.

One honest caveat: this tool checks structure, not policy. Google can parse your FAQ markup perfectly and still decide not to show it. For the final word, run the page through Google's Rich Results Test. This tool is for the fast iteration loop before that.