Schema markup has been around for over a decade, and most of the original hype about it was overblown. Rich snippets, instant rankings, and guaranteed visibility never materialized the way marketers hoped. But in 2026, a subset of schema types has become genuinely important — not for traditional search rankings, but for AI product visibility. This post covers which types matter, which don’t, and how to implement the ones that feed AI search.

What schema does for AI products

Schema markup is structured data embedded in your HTML that tells machines what your content means. When Google’s crawler finds Organization schema on your site, it learns your company name, founding date, logo, and social profiles in a machine-readable format.

This structured data feeds Google’s Knowledge Graph, which in turn feeds Google AI Overviews. It also helps other AI products understand entity relationships when they crawl your pages.

The key word is “feeds.” Schema doesn’t rank you. It helps AI products understand you. The difference matters.

The schema types that matter

Organization schema

The most important schema type for companies. Include:

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Acme Corp",
  "url": "https://acmecorp.com",
  "logo": "https://acmecorp.com/logo.png",
  "foundingDate": "2022-03-15",
  "founders": [{
    "@type": "Person",
    "name": "Jane Chen"
  }],
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "123 Market St",
    "addressLocality": "San Francisco",
    "addressRegion": "CA",
    "postalCode": "94105",
    "addressCountry": "US"
  },
  "sameAs": [
    "https://linkedin.com/company/acmecorp",
    "https://twitter.com/acmecorp",
    "https://www.crunchbase.com/organization/acme-corp",
    "https://www.wikidata.org/wiki/Q123456"
  ]
}

Every field matters. The sameAs array is critical — it tells AI products which profiles across the web belong to the same entity. This is how knowledge graphs connect your LinkedIn, Crunchbase, Wikidata, and website into one unified entity.

Person schema

For founders, executives, and public figures. Include on bio pages and about pages:

{
  "@context": "https://schema.org",
  "@type": "Person",
  "name": "Jane Chen",
  "jobTitle": "CEO",
  "worksFor": {
    "@type": "Organization",
    "name": "Acme Corp"
  },
  "alumniOf": "Stanford University",
  "sameAs": [
    "https://linkedin.com/in/janechen",
    "https://twitter.com/janechen"
  ]
}

Person schema builds individual entity signals alongside the company entity. AI products reference individual people when answering questions about company leadership.

Product schema

For each product or service you offer:

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Acme Compliance Platform",
  "description": "AI-powered compliance automation for mid-market construction companies",
  "brand": {
    "@type": "Organization",
    "name": "Acme Corp"
  },
  "offers": {
    "@type": "Offer",
    "price": "499",
    "priceCurrency": "USD",
    "priceValidUntil": "2027-01-01"
  }
}

Product schema with real pricing helps AI products answer “how much does X cost” queries accurately.

FAQ schema

For any page with a FAQ section:

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [{
    "@type": "Question",
    "name": "How much does Acme cost?",
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "Acme starts at $499/month for teams up to 25 users."
    }
  }]
}

FAQ schema gets extracted by Google AI Overviews and helps other AI products identify question-answer pairs on your pages.

Article and NewsArticle schema

For blog posts and press releases:

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Article Title",
  "author": {
    "@type": "Person",
    "name": "Jane Chen"
  },
  "datePublished": "2026-05-04",
  "dateModified": "2026-05-04",
  "publisher": {
    "@type": "Organization",
    "name": "Acme Corp"
  }
}

Article schema with named authors and publication dates helps AI products assess content freshness and authorship.

LocalBusiness schema

For companies with physical locations. Extends Organization with location-specific data:

{
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "name": "Acme Corp",
  "telephone": "+1-415-555-0100",
  "openingHoursSpecification": [{
    "@type": "OpeningHoursSpecification",
    "dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
    "opens": "09:00",
    "closes": "17:00"
  }]
}

LocalBusiness schema feeds Google’s local knowledge panel and helps AI products answer location-based queries.

Schema types that don’t matter much anymore

Helps Google display breadcrumbs in search results but doesn’t influence AI product answers.

Event schema

Useful for Google’s event listings but minimal impact on AI product visibility unless you’re an event company.

Recipe schema

Matters for recipe sites. Irrelevant for everyone else.

Review schema (self-hosted)

Review markup on your own site for your own products is ignored or discounted. Third-party review sites carry the review signals.

Video schema

Helps with Google’s video carousel but doesn’t feed AI product answers in a meaningful way for most companies.

Implementation

JSON-LD format

Always use JSON-LD (JavaScript Object Notation for Linked Data). It’s Google’s preferred format, it goes in the <head> or <body> of your HTML, and it’s the easiest to implement and maintain.

Where to place it

Validation

Use Google’s Rich Results Test (search.google.com/test/rich-results) to validate your schema. Fix any errors before deploying.

CMS plugins

Most CMS platforms have schema plugins:

If you’re on a custom-built site, add the JSON-LD blocks directly to your templates.

Common schema mistakes

Incomplete Organization schema

Adding only name and URL but skipping founders, sameAs, address, and foundingDate. Every missing field is a missed signal.

Listing a LinkedIn URL that goes to the wrong company or an old Twitter handle. Every sameAs link should be verified and current.

Schema on the wrong pages

Organization schema on every page is redundant. Put it on the homepage and about page. Product schema goes on product pages, not blog posts.

Marking up things that don’t exist on the page

Schema should describe content that’s actually visible on the page. Adding Product schema with pricing to a page that doesn’t show pricing violates Google’s guidelines and can trigger manual actions.

Stale schema

Schema with outdated pricing, old job titles, or previous addresses creates inconsistency signals. Update schema when facts change.

Over-engineering

Adding 20 schema types to every page doesn’t help. Focus on the five or six types that matter for your entity and content.

The schema audit checklist

Run this audit quarterly:

  1. Does your homepage have complete Organization schema?
  2. Do all sameAs links resolve to the correct profiles?
  3. Do bio pages have Person schema for key individuals?
  4. Do product pages have Product schema with current pricing?
  5. Do FAQ sections have FAQ schema?
  6. Do blog posts have Article schema with named authors?
  7. Does everything validate in Google’s Rich Results Test?
  8. Is the information in schema consistent with the information on the page?

Fix anything that fails.

The bottom line

Schema markup in 2026 matters for AI search because it helps knowledge graphs understand your entity, your products, and your people. Focus on Organization, Person, Product, FAQ, and Article schema. Implement them in JSON-LD, validate them, keep them current, and make sure the sameAs links connect all your properties. Skip the schema types that don’t feed AI products. The work takes a few hours to set up and a few minutes per quarter to maintain. For the entity signals it contributes, that’s a strong return.