JSON-LD and Schema.org Generator
Generate JSON-LD structured data for FAQs, articles, products, organizations, people, breadcrumbs and books, with validation, right in your browser.
"Headline" is required.
"Page URL" is recommended for Google rich results.
"Image URL" is recommended for Google rich results.
"Date published" is recommended for Google rich results.
"Author name" is recommended for Google rich results.
Check the result before publishing it:
What JSON-LD is and how to use this generator
JSON-LD is the format you use to tell a search engine what a page contains, using the Schema.org vocabulary: that the page is an article with a headline, an author and a date, or a product with a price, or a list of questions and answers. It's written as a block of JSON inside a script tag of type application/ld+json, separate from the visible HTML, and it's the format Google recommends. This tool walks you through it field by field and produces code ready to paste.
What to expect from structured data: it helps search engines understand the page and makes it eligible for rich results, such as price and rating for products, breadcrumbs in place of the URL, author and date for articles. It doesn't guarantee them, and Google doesn't list it as a direct ranking factor. One useful detail: since 2023, FAQ rich results are only shown for well-known government and health sites. FAQPage markup stays valid and machine-readable, but for most sites it won't change how the result looks.
How to use it: pick the data type, fill in the fields (those with an asterisk are required; the others are simply left out of the output when empty), copy the code and paste it into the page, in the head or the body, since both are accepted. Before publishing, check the result with the Google Rich Results Test and the Schema Markup Validator: the links are below the tool.
The most important rule: markup must describe what is actually visible on the page. Don't mark up content users can't see, and don't add ratings or reviews that are invented or absent from the page: that violates Google's guidelines and can lead to a manual action against your site. That's why the tool only generates a product rating if you fill in both the average and the number of reviews, and it reminds you to use real data only.
Everything runs in your browser: the data you enter is never sent to any server. When the code is wrapped in the script tag, the tool replaces the "<" character with its equivalent sequence \u003c: if the text accidentally contained "</script>" it would close the tag and break the page, and this substitution prevents that without changing the meaning of the data. You can put several JSON-LD blocks on the same page, for example an Article and a BreadcrumbList together.
Frequently asked questions
- Where do I paste the JSON-LD code?
- In a script tag of type application/ld+json, in the head or the body of the page: Google accepts both. If you use a CMS, many have a field for custom code or a plugin; with a framework it goes in the page template.
- JSON-LD or Microdata?
- Both are valid, but Google recommends JSON-LD: it sits apart from the visible HTML, so it's easier to write, update and check.
- Does structured data improve rankings?
- Not directly, according to Google. It can make a page eligible for rich results, which may increase visibility and clicks, but there's no guarantee they'll be shown.
- Why don't FAQs show the rich result?
- Since 2023, Google only shows FAQ rich results for well-known government and health sites. The markup stays valid and machine-readable, but for other sites it usually doesn't change how the result looks.
- Can I put several JSON-LD blocks on the same page?
- Yes. You can use several script tags, for example one for the article and one for the breadcrumb, or a single block with several entities. Each block must describe content that is really on the page.
- Is the data I enter sent to a server?
- No. The code is generated entirely in your browser: nothing is transmitted, stored or logged.
From the books
