Schema Markup Explained (With Examples)

What schema markup is

Schema markup is a small block of structured data, usually written in JSON-LD, that you add to a page to describe its content in a language machines understand. It labels things explicitly: this is an Organization, this is its phone number, this is an FAQ, this is a product with this price.

People read your page and infer meaning. Search engines and AI models prefer to be told directly. Schema tells them.

Why it matters, more than ever

Two reasons. First, schema powers rich results, the star ratings, FAQ dropdowns, and other enhancements that make your listing stand out. Second, and increasingly important, it helps AI answer engines understand and cite your content accurately, because it removes ambiguity about what your page actually says.

The types most sites need

You do not need every schema type. A handful cover most cases.

• Organization or LocalBusiness: who you are, where, and how to reach you.
• WebSite and WebPage: basic site and page identity.
• FAQPage: your questions and answers, eligible for rich results.
• Article: for blog posts and guides.
• Product, Service, and Review where relevant.

A copy-paste example

Here is a minimal Organization block. It goes in the head of your page.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Your Business",
  "url": "https://example.com/",
  "logo": "https://example.com/logo.png",
  "email": "[email protected]"
}
</script>

How to add it

Paste the JSON-LD into the head of the relevant page, one block per entity, with values that match what is actually on the page. On most platforms you can add it through a header snippet or a plugin. Keep it accurate; mismatched schema does more harm than good.

How to test it

Use Google Rich Results Test and the Schema.org validator to confirm your markup is valid and eligible for enhancements. Fix any errors before you ship, then re-test after changes.

Schema mistakes to avoid

Schema is high-leverage, but only when it is accurate. The common failures all come back to one rule: the markup must match reality.

• Marking up content that is not actually on the page, which search engines treat as a violation.
• Using the wrong type, such as tagging a blog post as a Product.
• Leaving validation errors in place, so the markup is ignored.
• Over-marking every element instead of focusing on what matters.

A practical tip: pair FAQPage schema with your Article markup on guide-style pages. It makes you eligible for FAQ rich results and gives AI answer engines clean question-and-answer pairs to quote directly. Keep everything honest and validated, and schema is pure upside.

If you are not sure where to begin, start with the two types almost every site benefits from: an Organization or LocalBusiness block sitewide, and FAQPage markup on any page that answers common questions. Get those validated and live, confirm them in the Rich Results Test, and you will have captured most of the value before touching anything more advanced. Schema rewards a small amount of careful work far more than a large amount of sloppy work.

One last point worth stressing: schema is not a substitute for good content, it is a way to make good content legible to machines. If the underlying page is thin or unclear, perfect markup will not save it. Get the content right first, describe it accurately with schema, validate it, and you give both search engines and AI answer engines every reason to understand and surface your page.