JSON-LD Schema Markup: The Complete 2026 Guide

Q: Where should I put JSON-LD in my HTML?

JSON-LD can be placed in either the head or body of your HTML document. Google recommends placing it in the head for best practice, but it works from anywhere in the document. The key is using the correct script type: .

Q: How do I test my schema markup?

Use Google's Rich Results Test (search.google.com/test/rich-results) to verify your markup is valid and eligible for rich snippets. Schema.org's Validator (validator.schema.org) checks syntax against the full Schema.org vocabulary. Google Search Console's Enhancements report shows real-world data on how your markup performs.

In 2026, structured data has gone from a "nice to have" SEO enhancement to an essential component of every well-optimized website. With AI search engines like SearchGPT, Perplexity, and Google's AI Overviews increasingly relying on structured data to understand, summarize, and cite web content, implementing JSON-LD schema markup is no longer optional for sites that want to remain visible in search.

JSON-LD (JavaScript Object Notation for Linked Data) is the format Google explicitly recommends for structured data. Unlike older formats like Microdata and RDFa that require inline HTML attributes, JSON-LD lives in a clean <script> block that's completely separate from your page's visual content. This makes it dramatically easier to implement, maintain, and debug — and it's why JSON-LD has become the de facto standard for schema markup.

This guide will take you from zero to expert on JSON-LD implementation. We'll cover the most impactful schema types for SEO, show complete code examples for each, explain how Google validates and renders structured data, and reveal the new "agent-ready" schema patterns that help AI search engines like SearchGPT and Perplexity understand and cite your content.

Generate JSON-LD Schema Instantly

Skip the manual coding. Our Schema Pro Architect generates valid, tested JSON-LD with visual snippet previews.

Open Schema Pro Architect →

Why JSON-LD Over Microdata and RDFa?

Before JSON-LD became the standard, website owners had two main options for structured data: Microdata and RDFa. Both formats work by adding attributes directly to existing HTML elements. While they're technically still supported, JSON-LD has emerged as the clear winner for several compelling reasons that all relate to developer experience and maintainability.

Feature	JSON-LD	Microdata	RDFa
Google Recommended?	Yes (preferred)	Supported	Supported
Implementation	Separate script block	Inline HTML attributes	Inline HTML attributes
Affects HTML structure?	No	Yes	Yes
Easy to debug?	Very easy (JSON format)	Hard (scattered across HTML)	Hard (scattered across HTML)
Dynamic generation?	Natural (JS can inject)	Requires DOM manipulation	Requires DOM manipulation
CMS compatibility	Works everywhere	Theme-dependent	Theme-dependent
AI search readability	Excellent (clean JSON)	Moderate	Moderate

The biggest advantage of JSON-LD is its separation of concerns. Your structured data is completely independent of your HTML markup, CSS styling, and visual layout. This means you can add, modify, or remove schema markup without any risk of breaking your page's design or functionality. It also means front-end developers and SEO teams can work independently — SEOs can update schema without touching production HTML templates.

The JSON-LD Structure Explained

Every JSON-LD implementation follows the same basic structure. Understanding these foundational elements is essential before diving into specific schema types. Let's break down the anatomy of a JSON-LD block:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "DominateTools",
  "url": "https://dominatetools.com",
  "logo": "https://dominatetools.com/logo.png",
  "sameAs": [
    "https://twitter.com/dominatetools",
    "https://github.com/dominatetools"
  ]
}
</script>

@context: This always points to https://schema.org, the vocabulary that defines all available entity types and properties. This tells search engines which dictionary to use when interpreting your data.

@type: Specifies the schema type — the kind of entity you're describing. Schema.org defines hundreds of types including Organization, Person, Product, Article, FAQPage, HowTo, LocalBusiness, and many more.

Properties: Each type has specific properties that describe attributes of the entity. An Organization has name, url, logo, and sameAs. A Product has name, price, brand, and offer. Using the correct properties for each type is essential for validation.

sameAs: This property is critical for entity-based SEO in 2026. It tells search engines and AI systems which external profiles, social media accounts, and knowledge base entries represent the same entity. This helps build your "entity graph" — the web of connections that AI search engines use to verify and contextualize your brand.

Schema Types That Win Rich Snippets

Not all schema types generate visible rich snippets in Google search results. Google only displays enhanced search features for specific schema types that it has explicitly documented support for. Here are the schema types most likely to generate valuable rich results in 2026:

Schema Type	Rich Result	Estimated CTR Boost	Difficulty
`FAQPage`	Expandable Q&A dropdowns	+15-25%	Easy
`HowTo`	Step-by-step instructions with images	+20-30%	Medium
`Product`	Price, availability, star ratings	+25-35%	Medium
`Review / AggregateRating`	Star ratings below title	+20-30%	Easy
`LocalBusiness`	Map pack, hours, reviews	+30-50%	Medium
`Article / NewsArticle`	Top Stories carousel, bylines	+10-20%	Easy
`Event`	Date, location, ticket availability	+15-25%	Easy
`Recipe`	Cooking time, calories, images	+25-40%	Medium
`VideoObject`	Video thumbnail, duration	+20-30%	Easy

Complete Examples: The Top 4 Schema Types

FAQPage Schema

FAQPage schema generates expandable question-and-answer dropdowns directly in search results. This is one of the highest-impact, easiest-to-implement schema types because it takes up significant SERP real estate and directly answers user queries. Use our Schema Pro Architect to generate FAQ schema with a point-and-click wizard.

{
  "@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 the page content. It helps search engines understand page content and display rich snippets in search results."
      }
    },
    {
      "@type": "Question",
      "name": "Does schema markup improve SEO?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Schema markup is not a direct ranking factor, but it enables rich snippets that increase click-through rates by 15-30%, which indirectly improves SEO performance."
      }
    }
  ]
}

HowTo Schema

HowTo schema generates step-by-step instruction cards in search results. Each step can include text, images, and estimated time. This is ideal for tutorial content, DIY guides, recipes, and any instructional content.

{
  "@context": "https://schema.org",
  "@type": "HowTo",
  "name": "How to Add Schema Markup to Your Website",
  "description": "A step-by-step guide to implementing JSON-LD structured data.",
  "totalTime": "PT15M",
  "step": [
    {
      "@type": "HowToStep",
      "position": 1,
      "name": "Choose your schema type",
      "text": "Determine which schema type matches your content. Use FAQPage for Q&A, HowTo for tutorials, LocalBusiness for physical stores."
    },
    {
      "@type": "HowToStep",
      "position": 2,
      "name": "Generate the JSON-LD code",
      "text": "Use a schema generator tool to create valid JSON-LD markup. Fill in all required properties for your chosen type."
    },
    {
      "@type": "HowToStep",
      "position": 3,
      "name": "Add the code to your page",
      "text": "Place the JSON-LD script block in the head or body section of your HTML page."
    },
    {
      "@type": "HowToStep",
      "position": 4,
      "name": "Validate with Google's Rich Results Test",
      "text": "Use the Rich Results Test to verify your markup is valid and eligible for rich snippets."
    }
  ]
}

LocalBusiness Schema

LocalBusiness schema is essential for any brick-and-mortar business. It powers the Google Map Pack, shows business hours, displays reviews, and provides contact information. Including geo coordinates ensures accurate map placement.

{
  "@context": "https://schema.org",
  "@type": "Restaurant",
  "name": "The Golden Fork",
  "image": "https://example.com/photos/restaurant.jpg",
  "url": "https://example.com",
  "telephone": "+1-555-123-4567",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "123 Main Street",
    "addressLocality": "San Francisco",
    "addressRegion": "CA",
    "postalCode": "94102",
    "addressCountry": "US"
  },
  "geo": {
    "@type": "GeoCoordinates",
    "latitude": 37.7749,
    "longitude": -122.4194
  },
  "openingHoursSpecification": [
    {
      "@type": "OpeningHoursSpecification",
      "dayOfWeek": ["Monday","Tuesday","Wednesday","Thursday","Friday"],
      "opens": "11:00",
      "closes": "22:00"
    }
  ],
  "priceRange": "$$",
  "servesCuisine": "Italian"
}

Organization Schema

Organization schema establishes your brand's identity in Google's Knowledge Graph. It connects your website to your social profiles, Wikipedia entries, and other authoritative sources through the sameAs property. This is the foundation of entity-based SEO for 2026.

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "DominateTools",
  "url": "https://dominatetools.com",
  "logo": "https://dominatetools.com/favicon.png",
  "description": "Free, privacy-first web tools for developers and creators.",
  "sameAs": [
    "https://twitter.com/dominatetools",
    "https://github.com/dominatetools",
    "https://www.linkedin.com/company/dominatetools"
  ],
  "contactPoint": {
    "@type": "ContactPoint",
    "contactType": "customer support",
    "email": "support@dominatetools.com"
  }
}

Schema Markup for AI Search Engines

The most significant development in structured data for 2026 is its role in powering AI search engines. SearchGPT, Perplexity, Google's AI Overviews, and other AI-powered search systems heavily rely on schema markup to understand content, determine relevance, and generate cited answers.

When an AI search engine encounters a page with well-implemented JSON-LD schema, it gains several advantages: it can immediately identify the entity type being described, it can extract specific facts and attributes (prices, hours, answers to questions), and it can verify the entity's authority through sameAs connections to external sources. Pages with comprehensive schema markup are significantly more likely to be cited in AI search answers than pages relying solely on unstructured HTML content.

To make your schema "agent-ready" for 2026's AI search landscape, focus on three key practices. First, use sameAs extensively to link your entity to authoritative external sources like Wikipedia, Wikidata, LinkedIn, and Crunchbase. Second, implement multiple complementary schema types on each page — for example, an Organization schema on your homepage combined with Article schema on blog posts and Product schema on product pages. Third, ensure all required and recommended properties are filled in completely. An incomplete schema is worse than no schema at all because it signals to AI systems that your data may be unreliable.

2026 Best Practice Use our Schema Pro Architect to generate "agent-ready" JSON-LD with built-in entity mapping and sameAs connections that help AI search engines understand and cite your content.

Validating and Testing Your Schema Markup

Implementing schema markup without validation is like deploying code without testing — you might get lucky, but you're more likely to have syntax errors, missing required properties, or deprecated types that prevent your rich snippets from appearing.

Google Rich Results Test: This is the definitive validation tool. Visit search.google.com/test/rich-results, enter your URL or paste your code, and the tool will show exactly which rich result types your page is eligible for and highlight any errors or warnings.

Schema.org Validator: Available at validator.schema.org, this tool validates your markup against the complete Schema.org vocabulary. It's stricter than Google's tool and useful for catching issues that might cause problems with other search engines or AI systems.

Google Search Console Enhancements: After your schema is live, Google Search Console's Enhancements report shows real-world data on how Google is processing your structured data. It reports valid items, items with warnings, and items with errors across your entire site, making it invaluable for monitoring at scale.

Build Schema Markup in Minutes

Our visual wizard generates validated JSON-LD with Google snippet previews. No coding required.

Open Schema Pro Architect →

Frequently Asked Questions

What is JSON-LD schema markup?

JSON-LD (JavaScript Object Notation for Linked Data) is Google's recommended format for implementing structured data. It's a <script> block added to your HTML that describes page content in a machine-readable format, enabling rich snippets like FAQ dropdowns, star ratings, recipe cards, and event details in search results.

Is JSON-LD better than Microdata or RDFa?

Yes, for most use cases. JSON-LD is Google's officially recommended format because it's completely separate from your HTML — you add it as a script block rather than inline attributes. This makes it easier to implement, maintain, debug, and doesn't risk breaking your page layout.

Does schema markup help SEO rankings?

Schema markup is not a direct ranking factor, but it significantly improves click-through rates by enabling rich snippets. Pages with FAQ dropdowns, star ratings, and how-to steps consistently show 15-35% higher CTR than plain blue links, which indirectly boosts SEO performance.

Where should I put JSON-LD in my HTML?

JSON-LD can be placed in either the <head> or <body> of your HTML document. Google recommends the <head> for best practice, but it works anywhere. The key is using the correct script type: <script type="application/ld+json">.

How do I test my schema markup?

Use Google's Rich Results Test at search.google.com/test/rich-results for the definitive check. Schema.org's Validator checks against the full vocabulary. After deployment, monitor Google Search Console's Enhancements report for real-world validation data across your site.

Related Resources

JSON Formatter Tool — Try it free on DominateTools
JSON to CSV Converter — Try it free on DominateTools
FAQ Schema for SEO — Win expandable Q&A rich snippets
Local Business Schema Guide — Dominate the Google Map Pack
Schema Markup for Rich Snippets — Which types generate visible results
How-To Schema Markup Guide — Create step-by-step rich results
Schema Pro Architect — Generate validated JSON-LD instantly