Schema Markup Guide: Every Type That Matters for SEO in 2026

Schema markup is one of the highest-ROI technical SEO investments in 2026, for two reasons that have converged: rich results in traditional Google Search increase click-through rates measurably, and AI search systems use structured data to extract, attribute, and cite content. This guide covers every schema type that matters — which ones earn rich results, how to implement each correctly, and which types AI systems specifically extract for generative answers.

Schema Markup Fundamentals

Schema.org is a collaborative vocabulary for structured data maintained by Google, Bing, Yahoo, and Yandex. It provides a standardized set of types (Person, Organization, Article, Product, Event) and properties (name, description, author, price) that machines understand consistently across platforms.

JSON-LD: The Correct Implementation Format

Three formats exist for schema markup: JSON-LD, Microdata, and RDFa. JSON-LD is Google’s recommended format and best practice for all implementations:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Your Article Title",
  "author": {
    "@type": "Person",
    "name": "Author Name"
  }
}
</script>

JSON-LD separates schema from HTML, making it easy to add, modify, and validate without touching content markup. It can be injected into the page via CMS plugins, tag managers, or template code.

The @graph Pattern

Modern schema best practice uses the @graph array to define multiple types on one page as linked entities:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Article",
      "@id": "https://example.com/page/#article"
    },
    {
      "@type": "Person",
      "@id": "https://example.com/author/name/#person",
      "name": "Author Name"
    },
    {
      "@type": "Organization",
      "@id": "https://example.com/#organization",
      "name": "Publisher Name"
    }
  ]
}
</script>

The @id URIs allow these entities to reference each other, creating a linked knowledge graph that search engines and AI systems parse more accurately than disconnected schema blocks.

Schema Types That Matter: Complete Guide

Article Schema

Use for: Blog posts, news articles, guides, tutorials — any long-form content page

Rich result: Not a standalone rich result, but required for Google Discover, Top Stories carousel, and AI citation attribution

Required properties: headline, image, author (with name), publisher (with name and logo), datePublished

Strongly recommended: dateModified, description, mainEntityOfPage, wordCount, url

Use NewsArticle subtype for time-sensitive news content (required for Top Stories eligibility). Use BlogPosting for blog content. Article is appropriate for evergreen guides.

FAQPage Schema

Use for: Pages with explicit question-and-answer content

Rich result: Previously generated expandable FAQ dropdowns in SERPs. Google reduced FAQ rich result display in 2023 for most sites, but FAQ schema is still heavily used by Google AI Overviews and other AI systems for extracting Q&A content.

{
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is [Topic]?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Complete answer text here..."
      }
    }
  ]
}

Best practices: 3–7 questions per page, answers should be complete standalone answers (not “see above”), questions should match actual user search queries.

HowTo Schema

Use for: Step-by-step instructional content

Rich result: Can generate step-by-step rich results for eligible queries, and is heavily extracted by AI systems for “how to” query responses.

{
  "@type": "HowTo",
  "name": "How to [Task]",
  "step": [
    {
      "@type": "HowToStep",
      "name": "Step 1 Name",
      "text": "Detailed step instructions",
      "image": "https://example.com/step1-image.jpg"
    }
  ],
  "totalTime": "PT30M"
}

Use ISO 8601 duration format for totalTime (PT30M = 30 minutes). Include images for each step where available — Google may render them in visual rich results.

Product Schema

Use for: E-commerce product pages

Rich result: Product rich results showing price, availability, and star ratings — high-impact for e-commerce CTR

Required for rich results: name, image

Required for price/availability: offers (with price, priceCurrency, availability)

Required for review snippet: aggregateRating (with ratingValue, reviewCount)

2026 note: Google has expanded product rich results to include merchant listings (free product listings in Shopping tab) — properly implemented Product schema enables free inventory display.

LocalBusiness Schema

Use for: Any business with a physical location or service area

Rich result: Knowledge panel data, local search display

Key properties: name, address (PostalAddress), telephone, openingHoursSpecification, geo (GeoCoordinates), url, image, priceRange, aggregateRating

Important subtypes: Use the most specific subtype available — Restaurant, MedicalBusiness, LegalService, AutoDealer, etc. Google uses subtype to determine category in local search.

GEO relevance: LocalBusiness schema is critical for local GEO — AI systems use it to extract business information for local query responses (“best dentist near me,” “Italian restaurants in [city]”).

Event Schema

Use for: Events, webinars, conferences, classes

Rich result: Event rich results in Google Search and Google Events

Required: name, startDate, location (or eventAttendanceMode for virtual)

Strongly recommended: endDate, description, image, organizer, offers (for ticketed events)

For virtual events: set eventAttendanceMode to “https://schema.org/OnlineEventAttendanceMode” and provide eventStatus appropriately.

JobPosting Schema

Use for: Job listing pages

Rich result: Job rich results in Google Search and Google for Jobs — significantly increases application volume for employers with proper implementation

Required: title, description, hiringOrganization (with name), jobLocation (or applicantLocationRequirements for remote), datePosted, validThrough, employmentType

High-impact optional: baseSalary (significantly increases click-through in Google for Jobs)

Recipe Schema

Use for: Recipe content

Rich result: Recipe rich results with image, time, and rating — very high CTR for food content

Required: name, image, author

For rich results: recipeIngredient, recipeInstructions (as HowToStep array), cookTime, prepTime, nutrition (NutritionInformation)

BreadcrumbList Schema

Use for: All pages with a navigational hierarchy

Rich result: Breadcrumb display in Google SERPs replacing or supplementing URL display

{
  "@type": "BreadcrumbList",
  "itemListElement": [
    {"@type": "ListItem", "position": 1, "name": "Home", "item": "https://example.com/"},
    {"@type": "ListItem", "position": 2, "name": "Category", "item": "https://example.com/category/"},
    {"@type": "ListItem", "position": 3, "name": "Page Title", "item": "https://example.com/category/page/"}
  ]
}

Implement on all pages — minimal effort, guaranteed display benefit.

Organization Schema

Use for: Homepage and about page

Rich result: Knowledge panel data, logo display in SERPs

Key properties: name, url, logo (with @type: ImageObject), sameAs (array of social profile URLs), contactPoint, foundingDate, description

GEO importance: Organization schema is the primary entity signal that AI systems use to understand your brand. The sameAs array — linking to Wikipedia, Wikidata, LinkedIn, Twitter/X, Crunchbase, and other authoritative profiles — is how AI systems connect your on-site schema to their knowledge graph.

Person Schema

Use for: Author pages, team pages, individual expert profiles

Rich result: Knowledge panel for notable individuals; author attribution in AI systems

Key properties: name, jobTitle, affiliation (linked to Organization), url, sameAs (social profiles, Wikipedia), knowsAbout (topics of expertise), description

Person schema on author pages combined with Article schema linking to the author is the primary E-E-A-T signal for AI citation. Named, credentialed authors with Person schema are cited at significantly higher rates than anonymous or minimally attributed content.

Review and AggregateRating Schema

Use for: Products, services, local businesses, software with user reviews

Rich result: Star ratings in SERPs — most clicked rich result type

Important compliance note: Google prohibits self-serving review markup (marking up first-party reviews as “reviews” schema on your own site). Only mark up third-party verified reviews. First-party review display requires specific implementation via third-party review platform widgets or Google’s guidelines for first-party review aggregation.

Software Application Schema

Use for: SaaS products, mobile apps, web applications

Rich result: App rich results with ratings, operating system, and category

Key properties: name, applicationCategory, operatingSystem, offers, aggregateRating, softwareVersion, featureList

Course Schema

Use for: Online courses, training programs

Rich result: Course rich results in Google Search

Required: name, description, provider (Organization)

For rich results: hasCourseInstance (with CourseInstance specifying courseMode, startDate, endDate, price)

VideoObject Schema

Use for: Pages with embedded video as primary content

Rich result: Video rich results with thumbnail, duration, upload date

Required: name, description, thumbnailUrl, uploadDate

For rich results: contentUrl or embedUrl, duration (ISO 8601)

Implementation Checklist

• ☐ Article/BlogPosting/NewsArticle on all content pages with complete author and publisher
• ☐ FAQPage on all guide content with 3+ Q&A pairs
• ☐ HowTo on all step-by-step instructional content
• ☐ BreadcrumbList on all pages
• ☐ Organization on homepage with sameAs linking to all authoritative profiles
• ☐ Person on all author pages with knowsAbout and sameAs
• ☐ Product + AggregateRating on all product pages
• ☐ LocalBusiness on location pages (most specific subtype)
• ☐ Test all schema in Google Rich Results Test
• ☐ Monitor Google Search Console Rich Results report for errors

Common Schema Mistakes to Fix

Missing required properties: Google will not generate rich results for schema missing required properties. Check the Rich Results Test for “missing required fields” warnings.

Schema contradicts page content: If your schema says a product is $29 and the page shows $49, this is a spam signal. Keep schema synchronized with visible content.

Using generic Article when BlogPosting or NewsArticle is more appropriate: Use the most specific type available — Google’s systems distinguish between types for different features.

Review schema on self-generated content: Marking up your own reviews as Review schema violates Google guidelines. Third-party or verified reviews only.

Outdated datePublished without updating dateModified: Always update dateModified when making substantial content changes — this freshness signal is used by AI retrieval systems.

Conclusion

Schema markup has never been more valuable than in 2026. Rich results maintain click-through rate advantage as traditional SERPs face pressure from AI-generated answers, and structured data is now a direct input to AI citation quality. The implementation investment is modest — adding JSON-LD to existing pages is hours of work for a developer — while the compounding benefits span years. Prioritize FAQPage, HowTo, Article with Person author attribution, and Organization sameAs for maximum SEO and GEO impact.