How-To March 2026

Schema.org Guide: How to Implement Structured Data Correctly

Structured data is the most direct way to tell AI crawlers what your website is, what it offers and why it is trustworthy. This guide shows step by step how to implement Schema.org with JSON-LD — from your first markup to the most important types for every kind of website.

What is Schema.org?

Schema.org is a shared vocabulary for structured data on the web, created in 2011 by Google, Microsoft, Yahoo and Yandex. It defines a collection of types and properties — from "Person" to "Product" to "FAQPage" — that website operators can use to embed machine-readable descriptions of their content in HTML.

The goal is simple: search engines and AI systems should understand the context of a page, not just the text. Without structured data, a crawler must guess from the body text whether "Apple" means the technology company or the fruit, who the author of an article is and whether a rating describes the product or the shop. With Schema.org, this is unambiguously defined.

Particularly relevant for AI visibility: ChatGPT, Claude and Perplexity use structured data to classify content faster and more reliably. A page with correct Schema.org markup is more likely to be rated as a trustworthy source and cited.

Why JSON-LD is the best format

Schema.org markup can be embedded in three formats: JSON-LD, Microdata and RDFa. Google recommends JSON-LD — and for good reason:

Separation of concerns: JSON-LD is embedded as a separate script block in the <head> or <body> and does not mix with HTML content. This makes it easier to maintain.
Easy to update: Changes to the markup do not require adjustments to the visible HTML.
Clearly readable: JSON-LD is easily readable by humans and simply parseable by machines.
Full Google support: All Schema.org features Google supports work with JSON-LD.

The basic structure of JSON-LD

A JSON-LD block is embedded as a <script> tag with type "application/ld+json" in the <head> or <body> of the page. Here is the minimal basic structure:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "WebPage",
  "name": "Page name",
  "url": "https://example.com/page/"
}
</script>

Every JSON-LD object has at least two required fields: @context (always "https://schema.org") and @type (the Schema.org type). All other fields are type-specific.

The most important Schema.org types

Organization

Basic information about the company or operator. Essential for every website.

WebPage / WebApplication

Describes a single page or web app. Ideal for subpages and tools.

Article

For blog posts, guides and editorial content. Improves citability.

FAQPage

For question-and-answer content. Particularly effective for AI visibility.

BreadcrumbList

Shows site structure. Helps crawlers understand hierarchy.

Product

For e-commerce products with price, reviews and availability.

LocalBusiness

For local businesses with address, opening hours and phone number.

Person

For author profiles and personal websites. Strengthens E-E-A-T signals.

Organization — essential for every website

The Organization type should be present on every website — ideally on the homepage. It defines who is behind the website and builds trust with AI systems.

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "My Company",
  "url": "https://example.com",
  "logo": "https://example.com/logo.png",
  "description": "Short description of the company",
  "contactPoint": {
    "@type": "ContactPoint",
    "email": "[email protected]",
    "contactType": "customer service"
  },
  "sameAs": [
    "https://twitter.com/mycompany",
    "https://linkedin.com/company/mycompany"
  ]
}

WebPage and WebApplication

{
  "@context": "https://schema.org",
  "@type": "WebApplication",
  "name": "Tool name",
  "url": "https://example.com/tools/my-tool/",
  "applicationCategory": "DeveloperApplication",
  "operatingSystem": "Web",
  "offers": {
    "@type": "Offer",
    "price": "0",
    "priceCurrency": "USD"
  }
}

Article — for blogs and guides

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Article title",
  "description": "Short article description",
  "url": "https://example.com/blog/article/",
  "datePublished": "2026-03-01",
  "dateModified": "2026-03-15",
  "author": {
    "@type": "Person",
    "name": "Jane Doe",
    "url": "https://example.com/author/jane/"
  },
  "publisher": {
    "@type": "Organization",
    "name": "My Company",
    "url": "https://example.com"
  },
  "inLanguage": "en-US"
}

FAQPage — particularly effective for AI

Tip: FAQPage markup is not just for dedicated FAQ pages. Add 3–5 common questions with answers at the end of every guide or blog post and mark them with FAQPage markup. This significantly increases the chance of being cited in AI answers.

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is Schema.org?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Schema.org is a vocabulary for structured data created by Google, Microsoft, Yahoo and Yandex. It allows website operators to embed machine-readable descriptions of their content in HTML."
      }
    }
  ]
}

{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    {
      "@type": "ListItem",
      "position": 1,
      "name": "Home",
      "item": "https://example.com/"
    },
    {
      "@type": "ListItem",
      "position": 2,
      "name": "Guides",
      "item": "https://example.com/guides/"
    },
    {
      "@type": "ListItem",
      "position": 3,
      "name": "Schema.org Guide",
      "item": "https://example.com/guides/schema-org/"
    }
  ]
}

Avoiding common mistakes

Incorrect JSON format: Missing commas, unclosed brackets or missing quotes invalidate the entire markup. JSON is error-intolerant — a single syntax error disables the complete markup.
Forgetting @context: Without "@context": "https://schema.org" the markup is not recognised as Schema.org by crawlers.
Content and markup don't match: The content stated in the markup must actually be visible on the page. Schema.org that claims content not on the page is treated as spam by Google.
Incorrect URL formats: URLs must be complete (with https://) and point to actually existing pages.

Important: Schema.org markup that describes content not found on the page ("cloaking") is treated as spam by Google and can lead to penalties. Markup and visible content must match.

Testing and validating Schema.org

Google Rich Results Test (search.google.com/test/rich-results) — Shows whether Google recognises the markup and whether rich snippets are possible.
Schema.org Validator (validator.schema.org) — Validates the markup against the official Schema.org specification.
Google Search Console — Shows after deployment which structured data Google found on your website and whether errors exist.

Quick implementation checklist

Implement Organization markup on the homepage
WebPage or WebApplication for all important subpages
Article markup for all blog posts and guides
FAQPage markup for pages with questions and answers
BreadcrumbList for deeper page levels
Check JSON for syntax errors with an online validator
Validate with Google Rich Results Test
Check for errors in Search Console after deployment

How good is your Schema.org markup?

AI-Ready Check analyses your structured data and shows you concretely what is missing — free, in 30 seconds.

Test for free now →

Frequently Asked Questions about Schema.org

Do I have to implement all Schema.org types?+

No — start with the most important types for your website. Organization and WebPage are useful for every website. Article is important if you publish blog posts or guides. FAQPage is always worthwhile if you have questions and answers on your page. Start small and expand gradually.

Does Schema.org directly improve my Google ranking?+

Schema.org is not a direct ranking factor for Google — at least not explicitly. However it enables rich snippets in search results which can significantly improve click-through rates. It also helps Google understand content better, which can indirectly improve relevance for certain queries.

Can I implement Schema.org without a CMS or plugin?+

Yes — JSON-LD is pure HTML and can be directly embedded into any page. No plugin or CMS required. You simply add a <script type="application/ld+json"> block to the <head> of your HTML file.

How many JSON-LD blocks can a page have?+

There is no official upper limit. A page can have multiple separate <script type="application/ld+json"> blocks — for example one for Organization, one for WebPage and one for FAQPage. This is completely valid and even recommended to improve readability.

How long does it take for Schema.org to become visible in Google?+

After implementing Schema.org it typically takes a few days for Google to re-crawl the page and recognise the markup. In Google Search Console under "Enhancements" you can then see which structured data was found. Rich snippets can only appear once Google has rated the markup as valid and relevant — this can take several weeks.