SEO

Schema markup generator (JSON-LD)

Pick a type, fill in the fields and copy valid JSON-LD. Required fields are marked, and extra ones sit under "Advanced fields". Below the tool: which types still get a Google rich result, and copy-ready examples.

JSON-LD output
 

Which schema types still get a rich result

Valid markup only makes a page eligible for a rich result; Google decides whether to show one. Google has also retired several rich results over the years, most recently FAQ results on 7 May 2026. The table sorts every type in this generator, plus the retired ones people still ask about, by what Google does with them today. Checked on 24 September 2026 against Google's search gallery and documentation changelog.

Schema typeWhat Google shows
Still shown in Google Search
Article The headline and a large image in article features (news, sports, blogs).
BreadcrumbList The page's place in your site, shown in the result. Desktop only.
Course A carousel of courses from one provider: at least 3 courses in an ItemList. A single course alone no longer gets a rich result (retired 2025).
DiscussionForumPosting Forum and community posts with their discussion.
Event Events with date and venue in an interactive list. Only events at a physical place.
ImageObject Creator, credit and license details in Google Images; the "Licensable" badge needs a license URL.
JobPosting Your job in Google's job search, with your logo and the job details.
LocalBusiness Business hours, departments and other details in the knowledge panel. Reviews and ratings only from sites that review other businesses.
Organization Logo, address and contact details in knowledge panels.
Product Price, availability and ratings. Needs an offer, a rating or a review.
ProfilePage Tells Google a page is about one person or organization, such as an author or creator profile.
QAPage One question with its answers, for pages where visitors write the answers.
Recipe A recipe result on its own or in a carousel.
Review Review stars for products, books, films, recipes, apps and more. Not for a business's reviews of itself.
SoftwareApplication App rating, description and link. Needs a price and a rating or review.
VideoObject Video details with a play option, key moments and live streams.
No rich result of its own
WebSite The site name Google shows above your results. Home page only.
Person Nothing on its own. Use it inside other markup: an article's author, a profile page.
Retired: Google no longer shows these
FAQPage Retired 7 May 2026. Questions that opened under the result. From 2023 only government and health sites got them; now nobody does. Still in the generator: valid markup, no rich result.
Quiz Retired January 2026. Practice problems for students.
ClaimReview and 5 more Retired 2025. Fact checks (ClaimReview), special announcements (SpecialAnnouncement), single-course details (Course), estimated salaries, learning videos and vehicle listings.
SearchAction in WebSite Retired November 2024. The sitelinks search box under a result.
HowTo Retired September 2023. Step-by-step instructions in the result.

JSON-LD examples to copy

Five common types, built by the generator above. Swap in your own values, and describe only what visitors can see on the page. A page can carry several blocks: a product page would usually have the Product and its BreadcrumbList.

Article or blog post

Google lists no required fields for articles, only recommended ones: the headline, an image, the author and the two dates. The author's url should point to a page that identifies them, such as an author bio.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "How to choose a road bike",
  "image": "https://example.com/images/road-bike.jpg",
  "author": {
    "@type": "Person",
    "name": "Jane Doe",
    "url": "https://example.com/authors/jane-doe/"
  },
  "datePublished": "2026-09-01",
  "dateModified": "2026-09-15"
}
</script>

Product with price and rating

Google needs an offer (a price), a rating or a review before it shows a product rich result; this one has the offer and a rating. Only mark up ratings that visitors can see on the page.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Trail running shoe",
  "image": "https://example.com/images/trail-shoe.jpg",
  "description": "Lightweight trail running shoe with a 6 mm drop.",
  "brand": {
    "@type": "Brand",
    "name": "Example Outdoor"
  },
  "offers": {
    "@type": "Offer",
    "price": "129.00",
    "priceCurrency": "EUR",
    "availability": "https://schema.org/InStock",
    "url": "https://example.com/shoes/trail/"
  },
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": 4.6,
    "reviewCount": 87
  }
}
</script>

Local business

Google needs only the name and the address. Write the phone number with its country code. Opening hours go in openingHoursSpecification, one block per group of days with the same times. Google also asks for the most specific type that fits, so change LocalBusiness to Bakery, Restaurant, Dentist and so on.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "name": "Example Bakery",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "Hauptstraße 1",
    "addressLocality": "Berlin",
    "postalCode": "10115",
    "addressCountry": "DE"
  },
  "telephone": "+49 30 1234567",
  "priceRange": "€",
  "url": "https://example.com/",
  "openingHoursSpecification": [
    {
      "@type": "OpeningHoursSpecification",
      "dayOfWeek": [
        "Monday",
        "Tuesday",
        "Wednesday",
        "Thursday",
        "Friday"
      ],
      "opens": "09:00",
      "closes": "17:00"
    },
    {
      "@type": "OpeningHoursSpecification",
      "dayOfWeek": [
        "Saturday"
      ],
      "opens": "10:00",
      "closes": "14:00"
    }
  ]
}
</script>

Organization with logo and profiles

Google suggests putting this on the home page or on one page about the organization, such as About us; it doesn't need to be on every page. sameAs lists your official profiles elsewhere.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Example GmbH",
  "url": "https://example.com/",
  "logo": "https://example.com/images/logo.png",
  "sameAs": [
    "https://www.linkedin.com/company/example",
    "https://github.com/example"
  ]
}
</script>

Breadcrumbs

One ListItem per level, numbered from 1; the generator numbers them for you. Google needs at least two, and the last one may leave out its item URL: Google then uses the page's own URL. It shows breadcrumbs on desktop only.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    {
      "@type": "ListItem",
      "position": 1,
      "name": "Home",
      "item": "https://example.com/"
    },
    {
      "@type": "ListItem",
      "position": 2,
      "name": "Shoes",
      "item": "https://example.com/shoes/"
    },
    {
      "@type": "ListItem",
      "position": 3,
      "name": "Trail running shoe",
      "item": "https://example.com/shoes/trail/"
    }
  ]
}
</script>

What structured data is

Structured data tells search engines what a page is about: that it's a recipe, what its rating is, who wrote it. They no longer have to guess from the text. JSON-LD is the format Google recommends: one <script type="application/ld+json"> block of data. With valid markup, a page becomes eligible for rich results such as review stars, recipe cards, event lists and breadcrumbs; the table above shows which still exist.

Required vs recommended fields

Fields marked * are required, and the box under the form lists any you've left empty. Mostly they're what Google requires for the rich result. A few types ask for more than Google does (it lists no required fields for articles, for example), because the markup is of little use without them. Unmarked fields are recommended: not mandatory, but they make the result richer. Advanced fields hold optional extra detail. Some of Google's rules can't be checked field by field, such as "an offer or a rating"; the note above the form points them out.

Questions about schema markup

JSON-LD vs Microdata: which should I use?

JSON-LD. Google reads all three formats (JSON-LD, Microdata and RDFa) but recommends JSON-LD, because it's the easiest to add and maintain and the least prone to mistakes. It's one separate block, while Microdata spreads attributes such as itemprop through your HTML. Everything this tool writes is JSON-LD.

Where does JSON-LD go: head or body?

Either. Google reads JSON-LD in the <head> and in the <body>, and also when JavaScript or a widget in your CMS adds it to the page. The head is the usual place. For a CMS field that adds the script tag itself, turn off the <script> wrapper option above and copy the bare JSON. One exception: WebSite markup, which sets your site name, belongs on the home page only.

Can a page have more than one JSON-LD block?

Yes. Use one block per thing on the page: a product page might carry a Product block and a BreadcrumbList block. Google's structured data guidelines say that marking up every item that applies gives it a fuller picture of the page. Things that belong together go inside one block instead, like the author inside an Article. Only describe what visitors can see on the page.

Does schema markup improve rankings?

Not directly, as far as Google has said. Its documentation presents structured data as a way to understand a page and to qualify for rich results, and when it retired several rich results in 2025 it said the change "won't affect how pages are ranked". What markup can change is how your result looks, and so how many people click it. In Google's case studies, Rotten Tomatoes measured a 25% higher click-through rate on pages with structured data, and Nestlé an 82% higher one on pages shown as rich results.

Why isn't my rich result showing?

Valid markup makes a page eligible, but Google doesn't guarantee a rich result, even when the Rich Results Test passes. The usual reasons: the rich result has been retired (see the table: FAQ and HowTo are the common ones); a required field is missing; the markup describes something visitors can't see; the reviews are a business reviewing itself; the page is blocked by robots.txt or noindex; or Google hasn't recrawled the page yet. URL Inspection in Search Console shows what Google last saw.

How do I test schema markup?

With two free tools that answer different questions. Google's Rich Results Test shows which Google rich results a page or a code snippet can get. The Schema Markup Validator checks any schema.org markup against the vocabulary, including types Google doesn't use. After you publish, Search Console's rich result reports and URL Inspection show what Google found on the live page.

Is FAQ schema still worth adding?

Not for Google. From August 2023 it showed FAQ rich results only for well-known government and health sites, and on 7 May 2026 it stopped showing them for every site. The markup is still valid schema.org, and Google has said that structured data it doesn't use "does not cause problems for Search", so there's no need to remove FAQ markup you already have. Just don't add it expecting a rich result. The generator keeps FAQ Page, labelled, in case something outside Google that you use reads it.

Related tools

Sources & references