Structured Data for SEO: A Practical JSON-LD Guide

You have probably heard that structured data is important for SEO. You may have also seen advice telling you to add 15 different schema types to every page. Most of that advice is wrong, or at least misleading.

Here is the truth: structured data does not directly improve your rankings. What it does is make your pages eligible for rich results, those enhanced search listings with star ratings, FAQ dropdowns, recipe cards, and product prices. Rich results get significantly higher click-through rates than standard blue links. That extra visibility is the real payoff.

This guide covers which schema types actually matter, how to implement them with JSON-LD, and which ones you can safely skip. If you are working through an on-page SEO checklist, structured data should be one of your final steps, not your first.

What Is Structured Data (and Why Should You Care)?

Structured data is a standardized format that tells search engines what your content is about. Instead of making Google guess that a page is a recipe, a product review, or an FAQ, you explicitly label it using vocabulary from Schema.org.

Think of it this way. Google can read your page and understand that it contains text about a product. But structured data tells Google the exact price, availability, rating, and review count in a machine-readable format. That precision is what unlocks rich results.

The key benefits:

• Rich results eligibility. Stars, prices, FAQs, how-to steps, and event details can appear directly in search results.
• Higher click-through rates. Pages with rich results typically see 20-30% higher CTR than plain listings.
• Better AI understanding. AI search engines like ChatGPT and Perplexity parse structured data to understand page content. This ties directly into GEO optimization and making your content AI-readable.
• Knowledge Graph inclusion. Proper Organization and Person schemas can feed into Google's Knowledge Graph.

JSON-LD vs. Microdata vs. RDFa: Pick One

There are three formats for adding structured data to a page. You only need one, and the answer is almost always JSON-LD.

JSON-LD (JavaScript Object Notation for Linked Data) is Google's recommended format. It lives in a <script> tag, separate from your HTML content. This means you can add, edit, or remove it without touching your page markup.

Microdata uses HTML attributes (itemscope, itemprop) embedded directly in your content markup. It works, but it is harder to maintain because the schema is mixed into your HTML.

RDFa is similar to Microdata but uses different attributes. It is more common in government and academic sites. For most websites, it is overkill.

Use JSON-LD. Google says so explicitly in their structured data documentation. It is easier to implement, easier to debug, and does not create coupling between your schema and your HTML structure. Every example in this guide uses JSON-LD.

The 5 Schema Types That Actually Trigger Rich Results

Schema.org lists hundreds of types. Most of them will not earn you a rich result in Google. Here are the five that consistently trigger visible changes in search results.

1. Article / BlogPosting

This is the foundation for any content site. Article schema helps Google understand your content's headline, author, publish date, and images. It is eligible for the Top Stories carousel and article-specific rich results.

JSON-LD: Article
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Your Article Title Here",
  "description": "A brief summary of the article.",
  "datePublished": "2026-04-18",
  "dateModified": "2026-04-18",
  "author": {
    "@type": "Person",
    "name": "Jane Smith",
    "url": "https://example.com/about/jane"
  },
  "publisher": {
    "@type": "Organization",
    "name": "Your Company",
    "logo": {
      "@type": "ImageObject",
      "url": "https://example.com/logo.png"
    }
  },
  "image": "https://example.com/article-image.jpg",
  "mainEntityOfPage": {
    "@type": "WebPage",
    "@id": "https://example.com/your-article"
  }
}
</script>

This schema is relevant to your meta tags setup because many of the same fields (title, description, image) should match between your meta tags and your structured data.

2. FAQPage

FAQ schema triggers expandable question-and-answer pairs directly in search results. Each question and answer appears below your listing, taking up more space on the SERP. For a full walkthrough, see our FAQ schema guide.

JSON-LD: FAQPage
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is structured data?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Structured data is a standardized format for providing information about a page and classifying its content."
      }
    },
    {
      "@type": "Question",
      "name": "Does structured data help SEO?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Structured data enables rich results which improve click-through rates, indirectly benefiting SEO."
      }
    }
  ]
}
</script>

3. Product

Product schema shows price, availability, and star ratings in search results. If you sell anything online, this is non-negotiable. Google can display your product price, stock status, and aggregate review score directly in search.

JSON-LD: Product
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Wireless Noise-Cancelling Headphones",
  "description": "Premium wireless headphones with active noise cancellation.",
  "image": "https://example.com/headphones.jpg",
  "brand": {
    "@type": "Brand",
    "name": "AudioTech"
  },
  "offers": {
    "@type": "Offer",
    "price": "149.99",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock",
    "url": "https://example.com/headphones"
  },
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "4.5",
    "reviewCount": "238"
  }
}
</script>

4. LocalBusiness

For any business with a physical location, LocalBusiness schema feeds directly into Google's local pack (the map results). It provides your address, hours, phone number, and service area in a format Google can use immediately.

JSON-LD: LocalBusiness
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "name": "Downtown Coffee Roasters",
  "image": "https://example.com/shop.jpg",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "123 Main Street",
    "addressLocality": "Portland",
    "addressRegion": "OR",
    "postalCode": "97201",
    "addressCountry": "US"
  },
  "telephone": "+1-503-555-0123",
  "openingHoursSpecification": [
    {
      "@type": "OpeningHoursSpecification",
      "dayOfWeek": ["Monday","Tuesday","Wednesday","Thursday","Friday"],
      "opens": "06:00",
      "closes": "18:00"
    },
    {
      "@type": "OpeningHoursSpecification",
      "dayOfWeek": ["Saturday","Sunday"],
      "opens": "07:00",
      "closes": "16:00"
    }
  ],
  "url": "https://example.com",
  "priceRange": "$$"
}
</script>

5. HowTo

HowTo schema breaks your instructions into numbered steps that Google can display as a rich snippet. This works well for tutorial and guide content where users want to see the steps before clicking.

JSON-LD: HowTo
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "HowTo",
  "name": "How to Add JSON-LD to Your Website",
  "description": "Add structured data to any webpage using JSON-LD format.",
  "step": [
    {
      "@type": "HowToStep",
      "name": "Identify the content type",
      "text": "Determine which schema type matches your page content (Article, Product, FAQ, etc.)."
    },
    {
      "@type": "HowToStep",
      "name": "Write the JSON-LD block",
      "text": "Create a script tag with type application/ld+json and populate it with the required and recommended properties."
    },
    {
      "@type": "HowToStep",
      "name": "Test with Rich Results Test",
      "text": "Paste your URL into Google Rich Results Test to verify the markup is valid and eligible for rich results."
    },
    {
      "@type": "HowToStep",
      "name": "Deploy and monitor",
      "text": "Push the changes live and monitor the Enhancements section in Google Search Console for errors."
    }
  ]
}
</script>

Start Here: 3 Schemas That Cover 80% of Use Cases

If you are feeling overwhelmed by schema options, here is the short version. These three types cover the vast majority of websites:

1. Article (for content sites and blogs). Every blog post and article page should have Article or BlogPosting schema. It takes 5 minutes to set up and is the most widely supported rich result type.
2. FAQPage (for any page with Q&A content). If your page answers common questions, add FAQ schema. The expanded results take up significant SERP space. See the FAQ schema implementation guide for specifics.
3. LocalBusiness or Organization (for your homepage). Every business website should have Organization schema on the homepage at minimum. If you have physical locations, use LocalBusiness instead.

That is it. Get these three right before worrying about anything else. Product schema matters if you run an e-commerce site. HowTo matters if you publish tutorials. Everything else is situational.

How to Implement JSON-LD Step by Step

Implementation is simpler than most guides make it seem. Here is the process.

Step 1: Pick the right schema type

Match your page content to a schema type. A blog post gets Article. A product page gets Product. A contact page for a physical business gets LocalBusiness. Do not force a schema type that does not match the page content.

Step 2: Write the JSON-LD block

Create a <script type="application/ld+json"> tag and add it to either the <head> or the <body> of your page. Google processes both locations equally. The head is the conventional choice.

Fill in all required properties first (Google will ignore the schema if required fields are missing), then add recommended properties. The exact requirements vary by type. Check Google's structured data documentation for each type.

Step 3: Match your markup to your visible content

This is the rule most people break. The data in your structured data must match what is visible on the page. If your Article schema says the headline is "Best Coffee Makers 2026" but your actual H1 says "Top Coffee Machines," Google may ignore the markup or flag a mismatch. Keep them consistent.

Step 4: Use the @graph pattern for multiple schemas

When you need multiple schema types on one page (for example, Article + BreadcrumbList + FAQPage), wrap them in a single script tag using the @graph array instead of adding multiple separate script tags. Both approaches work, but @graph is cleaner.

JSON-LD: @graph pattern
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Article",
      "headline": "Your Title",
      "datePublished": "2026-04-18"
    },
    {
      "@type": "BreadcrumbList",
      "itemListElement": [
        {"@type": "ListItem", "position": 1, "name": "Home", "item": "https://example.com/"},
        {"@type": "ListItem", "position": 2, "name": "Blog", "item": "https://example.com/blog"}
      ]
    }
  ]
}
</script>

Testing and Validation

Always test your structured data before deploying. There are two tools you should use:

Google Rich Results Test (search.google.com/test/rich-results) is the primary tool. It tells you whether your markup is valid and, more importantly, whether it is eligible for rich results. A schema can be technically valid but not eligible for a rich result if it is missing recommended properties.

Schema Markup Validator (validator.schema.org) checks your markup against the full Schema.org specification. It is stricter than Google's tool and useful for catching issues that might affect non-Google search engines.

After deployment, monitor these two places in Google Search Console:

• Enhancements reports. These show valid, warning, and error counts for each detected schema type on your site.
• URL Inspection tool. Test individual URLs to see which rich results Google has detected.

A common workflow: validate with the Rich Results Test before deploying, then check Search Console weekly for the first month. After that, check it whenever you publish new content or change your templates.

OwnVector checks for structured data as part of its AI-powered SEO audit. It flags missing schemas, invalid markup, and opportunities for rich results you are not currently using.

Common Mistakes That Get Your Markup Ignored

Google will silently ignore your structured data if you make these errors. No warning, no penalty, just no rich results.

1. Marking up content that is not on the page. If your FAQ schema includes questions that are not visible on the page, Google will ignore it. This was a common trick that Google specifically cracked down on in 2023. Every piece of structured data must correspond to visible content.

2. Missing required properties. Each schema type has required fields. Article needs headline, author, datePublished, and image at minimum. Product needs name, offers, and either image or review. Missing any required field invalidates the entire schema.

3. Using the wrong schema type. Adding Product schema to a blog post, or Article schema to a product page. Google checks whether the schema type matches the actual page content. Mismatches get ignored.

4. Invalid JSON syntax. A single missing comma, unclosed bracket, or trailing comma will break the entire JSON-LD block. Always validate your JSON syntax separately from the schema validation.

5. Duplicate conflicting schemas. Having two Article schemas on the same page with different headlines confuses search engines. Use one schema per type per page, or use the @graph pattern if they represent the same entity.

6. Not updating dateModified. If you update an article but leave the dateModified field unchanged, Google may treat it as stale content. Keep this field current whenever you make significant edits.

Structured data works best as part of a broader technical SEO strategy. It pairs with clean meta tags, a well-organized site structure, and content that satisfies AI readiness standards. On its own, it is just metadata. Combined with solid fundamentals, it is the difference between a standard listing and one that captures attention.