What is schema markup?

A plain-English guide to structured data, JSON-LD, and what it actually does for your pages.

Schema markup is code you add to a web page so search engines can read it without guessing. A page might say "Open 9 to 5" and "4.8 stars," and a person understands that instantly. A search engine sees a string of characters and has to infer what they mean. Schema markup removes the inference. It labels the parts of your page in a vocabulary that Google, Bing, and other systems already agree on.

That vocabulary comes from Schema.org, a shared project started in 2011 by Google, Bing, Yahoo, and Yandex. It defines types (like Recipe, Product, LocalBusiness) and properties for each type (a Recipe has cookTime, recipeIngredient, and so on). When you mark up a page, you are tagging your content with those agreed-upon labels.

Structured data vs. schema markup

People use the two terms interchangeably, and that is mostly fine, but there is a small distinction worth knowing. Structured data is the concept: any organized, machine-readable description of your content. Schema markup is the specific implementation using the Schema.org vocabulary. Think of structured data as the idea and schema markup as the way almost everyone does it in practice.

What schema markup looks like

Google supports three formats: JSON-LD, Microdata, and RDFa. They all work, but Google recommends JSON-LD, and it is what most people use today. The reason is practical. JSON-LD sits in its own script block instead of being woven into your visible HTML, so it is easier to add, easier to read, and far less likely to break when you redesign the page. Google states plainly in its structured data documentation that JSON-LD is the format it recommends for most sites.

Here is what a small LocalBusiness example looks like in JSON-LD:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "name": "Brightwater Dental",
  "telephone": "(813) 555-0142",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "412 Harbor View Blvd",
    "addressLocality": "Tampa",
    "addressRegion": "FL"
  }
}
</script>

Two lines do the heavy lifting. The @context tells the parser you are using the Schema.org vocabulary, and @type says what the thing is. Everything after that is a property of that type. You do not have to write this by hand. A Local Business schema generator fills in the fields and hands you the finished block.

Does schema markup help SEO?

This is where it pays to be precise, because there is a lot of loose talk on the subject. Schema markup is not a direct ranking factor. Google has said this repeatedly. As the Search Central documentation describes it, Google uses structured data to understand the content of a page and to enable richer features, not to push a page up the rankings on its own.

So why bother? Two reasons that actually hold up. First, eligibility for rich results. Structured data is what makes a page eligible for enhancements like recipe cards, FAQ dropdowns, product details, and event listings. Eligible is not the same as guaranteed, Google decides when to show them, but without the markup you are not in the running at all. Those richer listings take up more space and tend to earn more clicks, even when your position does not change.

Second, clarity. When a search engine can read your page without guessing, it is more likely to match you to the right queries. That benefit is quieter than a star rating, but it is real, and it compounds across a large site.

What you should be skeptical of is any claim that adding schema will lift your rankings by itself. It will not. Treat it as a way to be understood correctly and to qualify for features, not as a growth hack.

The schema types most sites actually use

Schema.org defines hundreds of types, but you will only ever touch a handful. The common ones:

• Organization and LocalBusiness describe your business as an entity, including name, logo, address, and contact details.
• Article and BlogPosting mark up editorial content with an author, publish date, and headline.
• Product carries price, availability, and brand for e-commerce pages.
• FAQPage marks up question-and-answer content that is visible on the page.
• BreadcrumbList describes where a page sits in your site's navigation.
• Person, Event, Recipe, and VideoObject cover the obvious cases their names suggest.

One rule that saves trouble: only mark up what is actually on the page. Google's structured data guidelines are explicit that the markup must describe content visible to the user. Marking up an FAQ that does not appear on the page, or a rating no real reviewer gave, is the kind of thing that gets pages disqualified from rich results, and in some cases triggers a manual action.

How to add schema markup to your site

The path depends on how your site is built.

1. Generate the JSON-LD. Use a generator for the type you need, fill in the fields, and copy the output. That avoids the most common errors, which are syntax slips and missing required properties.
2. Paste it into the page. Drop the script block into the <head> of the relevant page. On WordPress, a free plugin like WPCode adds header code without touching theme files, and SEO plugins such as Yoast and Rank Math accept custom JSON-LD. On a static site, paste it straight into the HTML.
3. Test it. Run the page through the Rich Results Test to check Google eligibility, and the Schema.org Validator for syntax. Fix anything they flag.
4. Confirm in Search Console. After the page is live, the Enhancements reports and URL Inspection tool in Google Search Console show whether Google has read your structured data and whether it found errors.

A note on AI search

You will see claims that schema markup is now essential for showing up in AI answers. Be measured here. The honest position, and the one Google's own guidance supports, is that the companies behind tools like ChatGPT and Google's AI Mode have not published clear evidence that they read Schema.org markup the way traditional search does. What we do know is that structured data helps conventional search engines interpret pages, and several AI systems lean on those same search indexes. So the indirect case is reasonable, but anyone promising guaranteed AI citations from schema alone is getting ahead of the evidence.

The short version

Schema markup is a small, structured description of your page written in a vocabulary search engines understand. It will not rank your page for you, but it makes your content legible, qualifies you for richer search listings, and removes ambiguity about what your pages are. For most sites it is a modest amount of work for a durable benefit, and a schema generator takes the tedious part off your plate.