Structured data is a standardized vocabulary you add to your HTML so machines can interpret what a page is about—not just parse its words. In 2026, its role has expanded well beyond blue-link rich results: Google's AI Overviews, the Knowledge Graph, and third-party assistants all lean on structured data to build reliable entity relationships. Getting it right is one of the highest-leverage technical SEO tasks available.

Schema.org A collaborative vocabulary (backed by Google, Microsoft, Yahoo, and Yandex) of types and properties—like Product, Article, LocalBusiness, and FAQPage—used to describe entities on the web in a machine-readable way.

Three Formats—and Why JSON-LD Wins

Schema.org markup can be expressed as Microdata, RDFa, or JSON-LD. Google explicitly recommends JSON-LD because it lives in a single <script> block separate from your visible HTML, which makes it easier to generate, template, and maintain. Microdata and RDFa interleave attributes throughout your markup and are far more error-prone.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "name": "Example Ottawa Bakery",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "123 Bank St",
    "addressLocality": "Ottawa",
    "addressRegion": "ON",
    "postalCode": "K1P 5N2",
    "addressCountry": "CA"
  },
  "telephone": "+1-613-555-0100",
  "openingHours": "Mo-Sa 07:00-18:00"
}
</script>

Structured Data That Earns Rich Results

Not all schema produces a visual enhancement in search. These are the types with documented rich-result support that most sites should prioritize.

Schema TypeRich ResultBest For
Product + Offer + ReviewPrice, availability, star ratingsE-commerce product pages
RecipeCook time, ratings, image carouselFood and recipe content
EventDate, venue, ticket linkConcerts, webinars, local events
FAQPageExpandable Q&A (limited eligibility)Genuine FAQ content
BreadcrumbListBreadcrumb navigation trailMost site sections
LocalBusinessKnowledge panel, hours, mapBrick-and-mortar businesses
Google restricted FAQ rich results in 2023 to authoritative government and health sites for most queries. Keep FAQPage schema for the entity clarity it provides, but do not expect the expandable UI on a typical commercial page.

Building an Entity Graph with @id

Advanced structured data is not a pile of disconnected snippets—it is a connected graph. Assign each entity a stable @id (a URI) and reference it across pages so Google understands that the Organization publishing your articles is the same one behind your LocalBusiness listing. This entity consistency is exactly what AI search systems reward, a theme we develop in our [technical SEO guide](/technical-seo-guide/).

  • Use sameAs to link your Organization to authoritative profiles (LinkedIn, Wikidata, your Google Business Profile).
  • Nest author and publisher as referenced Person/Organization entities, not bare strings.
  • Reuse a single @id for your Organization across every page's markup.

Validation and Common Pitfalls

  1. Validate syntax and eligibility with Google's Rich Results Test for a live or pasted URL.
  2. Check general Schema.org conformance with the Schema Markup Validator (validator.schema.org).
  3. Monitor the Rich Results and Enhancement reports in Google Search Console for warnings at scale.
  4. Re-test after every template change—a single broken JSON-LD comma can invalidate the whole block.
Should you add structured data everywhere?
  • Improves eligibility for rich results and click-through rate
  • Strengthens entity understanding for AI Overviews and assistants
  • Low risk when it accurately reflects visible page content
  • Marking up content not visible to users can trigger a manual action
  • Poorly maintained JSON-LD templates drift out of sync with the page
  • Some types (like FAQ) no longer reliably render, so ROI varies
Structured data must match what a human sees on the page. Never inject Review or Offer schema for prices or ratings that do not appear in the visible content—Google treats this as spam and can penalize the entire property.

Does structured data directly improve rankings?

It is not a direct ranking factor, but it improves how search engines understand your content and can earn rich results that lift click-through rate—an indirect but real benefit.

Can I add JSON-LD if my site is JavaScript-rendered?

Yes, but ensure it is present in the rendered DOM Googlebot sees. Client-side injected schema can be missed if rendering fails—see our JavaScript SEO guide for reliable patterns.

How much schema is too much?

There is no penalty for volume as long as every entity accurately describes visible content and the relationships are truthful. Focus on accuracy over quantity.

  • Use JSON-LD—Google recommends it and it is easiest to maintain.
  • Prioritize schema types with documented rich-result support.
  • Connect entities with stable @id references to build a coherent graph.
  • Always validate and keep markup consistent with visible content.

Structured data only helps if crawlers reach and render your markup. Pair this work with sound [crawl budget optimization](/crawl-budget-optimization/) and confirm your JSON-LD survives rendering by reviewing our [JavaScript SEO guide](/javascript-seo-rendering/).