Schema Markup for Beginners: A Practical Guide to JSON-LD

By ·

Schema markup, also called structured data, is a small block of code that describes your page in a format machines understand without guessing: this page is an article written by this person on this date; this is a product with this price; this is a local business open at these hours. Search engines use it to understand content and, for some types, to show richer results such as breadcrumbs, review stars, recipe details or event dates.

If the word "code" puts you off, do not worry. This guide explains the idea in plain language, shows you exactly what the code looks like, and walks you through generating, adding and testing it without writing it by hand.

What schema markup is

Schema.org is a shared vocabulary, created by the major search engines, for describing things on the web: people, organizations, articles, products, events, recipes and hundreds more. Each type has properties. A Product can have a name, image, brand and offers; an Event can have a startDate and location.

Structured data is that vocabulary written into your page. Google's introduction to structured data explains that Google uses it to understand page content and to enable special search result features.

JSON-LD, Microdata and RDFa

There are three formats for writing structured data:

  • JSON-LD: a separate block of code inside a <script type="application/ld+json"> tag. It does not touch your visible HTML.
  • Microdata: attributes such as itemprop added to existing HTML elements.
  • RDFa: similar attributes, more common in some publishing systems.

Google supports all three, but recommends JSON-LD because it is the easiest to add and maintain. Everything in this guide uses JSON-LD.

What it can and cannot do

What it can do

  • Help search engines understand what a page is about and how its parts relate.
  • Make a page eligible for rich results. Google's search gallery lists the features it currently supports and the markup each one needs.
  • Tell Google your preferred site name, logo and organization details.

What it cannot do

  • It does not guarantee a rich result. Google decides whether to show one based on many factors.
  • It is not a shortcut to higher rankings. It helps understanding; it does not replace good content.
  • It cannot describe content that is not on the page. Google's structured data policies require markup to represent the visible content, and misleading markup can lead to a manual action that removes rich results.

Features change over time

Google adjusts which rich results it shows. For example, in 2023 Google limited FAQ rich results to well-known, authoritative government and health websites and retired How-to rich results. FAQPage markup is still valid schema and harmless to keep, but most sites should not expect FAQ dropdowns in search. Always check the current search gallery before investing time in a type.

The most useful types for small sites

TypeUse it onWhy
Article / BlogPostingBlog posts, news, guidesClarifies headline, author, dates and images
BreadcrumbListAny page in a hierarchyCan show a breadcrumb trail instead of a raw URL
OrganizationHomepage or about pageLogo, name, contact details and official profiles
LocalBusinessA physical business's main pageAddress, hours, phone, location
ProductProduct pagesPrice, availability, reviews
EventEvent pagesDate, venue or online location, tickets
RecipeRecipesCooking time, ingredients, ratings

Anatomy of a JSON-LD block

Here is a simple Article example:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "How to Repot a Snake Plant Without Killing It",
  "image": "https://www.example.com/images/snake-plant.jpg",
  "datePublished": "2026-11-20T09:00:00+01:00",
  "dateModified": "2026-11-20T09:00:00+01:00",
  "author": {
    "@type": "Person",
    "name": "Ada Okafor",
    "url": "https://www.example.com/p/about.html"
  }
}
</script>
  • @context says the vocabulary is schema.org.
  • @type says what the thing is.
  • The other lines are properties. Nested objects, like author, have their own @type.
  • Dates use the ISO 8601 format, ideally with a time zone.

Google's Article documentation lists the recommended properties. Add the ones you can fill accurately.

A BreadcrumbList example

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    { "@type": "ListItem", "position": 1, "name": "Guides", "item": "https://www.example.com/guides/" },
    { "@type": "ListItem", "position": 2, "name": "Houseplants", "item": "https://www.example.com/guides/houseplants/" },
    { "@type": "ListItem", "position": 3, "name": "Repotting a Snake Plant" }
  ]
}
</script>

The last item can omit the URL because it is the current page. See Google's breadcrumb documentation for details.

Step by step: generate, add and test

  1. Pick the type that matches what the page really is. One page can have more than one type, such as Article plus BreadcrumbList.
  2. Open the schema markup generator and choose the type: Article, FAQ, LocalBusiness, Organization, Product, Event or Breadcrumbs.
  3. Fill in the fields using exactly what appears on the page. If the page does not show a price, do not add one.
  4. Copy the JSON-LD.
  5. Add it to the page. It can go in the <head> or the <body>. In a Blogger post, switch to HTML view and paste it at the end of the post. On WordPress, many SEO plugins add common types automatically, or you can use a custom HTML block.
  6. Test it with Google's Rich Results Test, which shows which rich results the page is eligible for, plus errors and warnings. For general schema validation beyond Google's features, use the Schema Markup Validator at validator.schema.org.
  7. Monitor the Enhancements section of Search Console, which reports valid items and errors across your site over time.

Common mistakes

  • Duplicate markup. Many themes and plugins already add Article or BlogPosting markup. Paste your page into the on-page SEO checker to see what structured data exists before adding more.
  • Marking up invisible content, such as reviews that do not appear on the page.
  • Self-serving reviews. Google does not show review stars for reviews a business writes about itself on its own LocalBusiness or Organization markup.
  • Broken JSON. A missing comma or a curly quote copied from a word processor breaks the whole block. Use a generator and test every time.
  • Forgetting to update. If the price, hours or event date changes, the markup must change too.

FAQ

Does schema markup improve rankings?

It is not a direct ranking boost. It helps search engines understand the page and can make it eligible for richer results, which can make your listing more useful to searchers.

Do Blogger blogs need schema markup?

Many Blogger themes already include basic BlogPosting markup for posts. Check your page first. Add BreadcrumbList or Organization markup if your theme lacks it, and add specialist types such as Recipe only on pages that are truly that type.

How long until rich results appear?

Google needs to recrawl the page first, and even valid markup does not guarantee a rich result. You can request indexing with the URL Inspection tool in Search Console to speed up the recrawl.

Conclusion

Schema markup sounds technical, but the idea is simple: describe the page honestly in a format machines understand. Start with Article and Breadcrumb markup on your posts and Organization markup on your homepage, generate it with a tool, test every page and keep it in sync with what visitors see. Combine it with a solid on-page SEO checklist and your pages will be as clear to search engines as they are to readers.

Want keyword ideas for your own topic? Use the free keyword research tool → or browse all free SEO tools.

Comments