Schema Markup Guide: JSON-LD Explained for Beginners

Schema markup is a small block of code that tells search engines exactly what a page is about: an article with an author and a date, a local business with opening hours, a product with a price. Search engines can often work this out from your text, but schema markup removes the guesswork. This guide explains structured data in plain English, shows you how a JSON-LD block is put together, and walks you through adding and testing your first one.

This guide is part of our complete website SEO audit guide, which walks through every step of auditing a small site.

What schema markup actually is

Schema markup is structured data written using the shared vocabulary published at schema.org. That vocabulary was created jointly by the major search engines so that everyone describes things the same way. It defines hundreds of types (Article, Organization, Product, Event, Recipe, LocalBusiness and so on) and, for each type, a list of properties (headline, author, datePublished, address, price…).

When you add schema markup to a page, you are not changing what visitors see. You are adding a machine-readable summary alongside the visible content. A person reads “Published 4 September by the Editorial Team”; a search engine reads "datePublished": "2026-09-04" and "author": {"@type": "Organization", "name": "Editorial Team"}. Same facts, but in a format that cannot be misread.

Three things structured data is not:

• Not a ranking shortcut. Structured data helps search engines understand and present your page; it does not make a weak page rank.
• Not a guarantee of rich results. Google decides whether to show stars, breadcrumbs or other enhancements. Valid markup makes a page eligible, nothing more.
• Not a place for hidden claims. Everything in your markup must match what users can see on the page.

Why JSON-LD is the format to use

There are three ways to write schema markup: Microdata, RDFa and JSON-LD. Microdata and RDFa weave attributes into your existing HTML tags, which means the markup breaks whenever someone edits the layout. JSON-LD sits in its own <script> tag, completely separate from the visible HTML.

Google’s introduction to structured data recommends JSON-LD where your setup allows it, and almost every WordPress SEO plugin outputs it. Unless you inherit an old theme full of Microdata, use JSON-LD.

Anatomy of a JSON-LD schema markup block

Here is a complete, minimal block for a blog post:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "headline": "Schema Markup Guide: JSON-LD Explained for Beginners",
  "datePublished": "2026-09-04T09:00:00+00:00",
  "dateModified": "2026-09-04T09:00:00+00:00",
  "author": {
    "@type": "Organization",
    "name": "Editorial Team"
  },
  "image": "https://example.com/images/schema-guide.webp"
}
</script>

Reading it line by line:

• @context tells the parser which vocabulary you are using. For SEO it is always https://schema.org.
• @type names the thing being described. Types are case-sensitive: BlogPosting works, blogposting does not.
• Properties such as headline and datePublished hold the values. Dates use ISO 8601 format.
• Nested objects, like the author, have their own @type and properties inside curly braces.

JSON is strict. Keys and text values need straight double quotes, items are separated by commas, and there must be no comma after the last item in an object. Most broken JSON-LD comes down to one of those three rules.

As your markup grows you will also see @graph and @id in plugin output. A @graph is simply a list that holds several objects in one block, such as an Organization, a WebSite and an Article. An @id is a unique label (usually a URL with a fragment like #organization) that lets one object refer to another, so the Article can point to the Organization as its publisher without repeating every detail. You do not need either for your first hand-written block, but recognising them makes plugin output much easier to read.

Which schema types suit your pages

You do not need dozens of types. Most small sites are well served by four or five, matched to page templates:

Be realistic about rich results. Google has narrowed or retired several enhancements over the years. FAQ rich results, for example, are now limited to well-known government and health sites, and HowTo rich results have been removed. The markup is still valid and still describes your content, but check Google’s Search Gallery before you invest time in a type purely for a visual enhancement. For copy-ready code, see our Article, FAQ and Breadcrumb JSON-LD examples.

How to add schema markup to your site

There are three common routes. Pick the one that matches how your site is built.

1. Through your SEO plugin

On WordPress, plugins such as Rank Math or Yoast generate Article, Organization, WebSite and BreadcrumbList markup automatically. Your job is to fill in the settings correctly: organisation name, logo, social profiles and default schema type for posts. This covers the basics for most blogs.

2. Hand-written JSON-LD in the page head

For types a plugin does not cover, paste a JSON-LD block into the page’s head section or into a custom HTML area. Keep a master copy of each block in a text file so you can update it later.

3. Generated by your theme or CMS templates

Developers can output JSON-LD from page templates, pulling values like the title and date straight from the database. This keeps markup in sync with content automatically, which is the most reliable option on larger sites.

Whichever route you choose, follow these steps:

1. List your main page templates and match each to one schema type.
2. Check what your theme and plugins already output, so you do not create duplicates.
3. Add or configure markup for one template first.
4. Test a live URL from that template (see the next section).
5. Roll out to the remaining templates once the first one validates cleanly.

How to check your schema markup works

Never assume markup is correct because a plugin says it is enabled. Test it:

• Google’s Rich Results Test shows which rich result types a URL is eligible for and lists errors and warnings for those types.
• The Schema Markup Validator (validator.schema.org) checks your markup against the full schema.org vocabulary, including types Google does not use for rich results.
• Search Console enhancement reports track valid and invalid items across your whole site over time.

For quick spot checks while browsing, the free LiteScroll SEO Inspector Chrome extension lets you review the schema markup on any page you visit, alongside its metadata and heading structure. That makes it easy to compare your pages with a competitor’s or confirm that a plugin change actually reached the live page.

If a test flags problems, our guide to testing and fixing schema markup errors walks through the most common messages and their fixes.

Common beginner mistakes

• Marking up invisible content. Reviews, prices or FAQs that appear only in the code break Google’s guidelines.
• Duplicate blocks. A theme and a plugin both outputting Article markup can send conflicting signals. Keep one source.
• Wrong type for the page. A category page is not a Product, and a service page is not an Article.
• Stale values. Hand-written blocks keep old prices or dates long after the page changes.
• Relative URLs. Use full absolute URLs for url, image and logo values.

Structured data also works best on pages that are already well structured. A clear title, a single descriptive heading and a strong meta description matter more than any snippet of code; our guide to page titles and meta descriptions covers that groundwork.

To check which schema types a live page already outputs before you edit anything, use the LiteScroll SEO Inspector Chrome extension, then validate the markup with a dedicated testing tool.

Next steps

• Pick your three most important page templates and choose one schema type for each.
• Check what your SEO plugin already outputs before adding anything by hand.
• Test one live URL per template in the Rich Results Test and the Schema Markup Validator.
• Spot-check pages as you browse with the LiteScroll SEO Inspector.
• Re-test after theme or plugin updates, because that is when markup most often breaks.

For more practical, lightweight SEO guides and tools, visit LiteScroll.com.