Schema Markup for AI Search: Which Types Help in 2026

Schema markup went through a hype cycle. For years it was sold as the route to stars, FAQ dropdowns and how-to carousels in Google. Then Google removed HowTo rich results in 2023, restricted FAQ rich results the same year, and stopped showing them entirely on 7 May 2026. A lot of sites concluded schema no longer mattered.

That conclusion went too far. Structured data still makes pages eligible for the rich results that remain (products, reviews, breadcrumbs, organisation details, events, recipes and more), and it gives AI systems clean facts about who you are and what each page is. This guide covers which types are worth adding in 2026 and how. It sits under the AI search readiness checker guide.

What schema markup does for AI search

Language models and search systems can read prose. What they can't do reliably is resolve ambiguity: whether "Mercury" is the planet, the element or your bank; whether "$29" is a monthly price or a one-off; whether the page was updated last week or in 2019. Structured data answers those questions directly.

For AI answers specifically, schema helps in three ways:

• Entity clarity. Organization markup with name, logo, url and sameAs links to official profiles ties your site to one entity, which matters when an AI is deciding whether you are the source it thinks you are.
• Fact extraction. Product price and availability, Article dateModified and author, LocalBusiness address and openingHours are exactly the facts AI answers quote.
• Page type. Knowing a page is a product, a how-to article or a local business listing helps a system decide whether it answers the question at all.

Schema also travels further than Google. The same JSON-LD that Google reads is available to any crawler that fetches your HTML, including AI search crawlers that don't execute JavaScript, as long as it is in the server-rendered page rather than injected by a tag manager.

What schema does not do is make a page rank or get cited on its own. Google's guidance for AI features says normal SEO best practices apply, and that there is no special markup required to appear in them. Schema is a clarity layer on top of good content, not a substitute for it.

How to add schema markup for AI search in 6 steps

1. List your page types (homepage, article, product, category, location, tool) and pick one main schema type for each.
2. Add Organization and WebSite JSON-LD to the homepage with your official name, logo, URL and sameAs profile links.
3. Add the main type to each page template, filling values from the same data the page displays.
4. Add BreadcrumbList to every page below the top level, matching the visible breadcrumb trail.
5. Connect the blocks with @id references, so an article's publisher points to the homepage's Organization rather than redefining it.
6. Validate each template in Google's Rich Results Test and the Schema.org validator, then re-check after any template change.

Which schema types help in 2026

Two cautions from the table. Review markup about your own business on your own site (self-serving reviews) is not eligible for review stars in Google, and adding it anyway risks a manual action. And FAQPage markup is now purely descriptive: keep it if the questions and answers are genuinely on the page, but don't add FAQ sections just for markup.

Copy-paste JSON-LD examples

These are minimal, valid starting points. Replace every value with your own, and make sure each one matches what the page shows.

Organization and WebSite (homepage):

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Organization",
      "@id": "https://www.example.com/#org",
      "name": "Example Ltd",
      "url": "https://www.example.com/",
      "logo": "https://www.example.com/logo.png",
      "sameAs": [
        "https://www.linkedin.com/company/example",
        "https://x.com/example"
      ]
    },
    {
      "@type": "WebSite",
      "@id": "https://www.example.com/#website",
      "name": "Example",
      "url": "https://www.example.com/",
      "publisher": { "@id": "https://www.example.com/#org" }
    }
  ]
}
</script>

Article (content page):

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "How to Choose a Trail Running Shoe",
  "datePublished": "2026-03-02",
  "dateModified": "2026-10-14",
  "author": { "@type": "Person", "name": "Sam Rivera" },
  "publisher": { "@id": "https://www.example.com/#org" }
}
</script>

Product with offer (product page):

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Ridge Trail Shoe",
  "image": "https://www.example.com/img/ridge.jpg",
  "brand": { "@type": "Brand", "name": "Example" },
  "offers": {
    "@type": "Offer",
    "price": "129.00",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock"
  }
}
</script>

Connecting schema across pages with @id

Most sites add schema page by page, and each page ends up redefining the organisation: a slightly different name on the blog, a different logo URL on product pages, no sameAs anywhere except the homepage. To a machine reading the markup, that looks like several organisations.

The fix is to define each entity once and refer to it everywhere else with an @id, a URL-shaped identifier that doesn't have to resolve to a page. The pattern:

• The homepage defines the Organization with "@id": "https://www.example.com/#org" and the full set of properties.
• Every Article, Product and WebPage block uses "publisher": { "@id": "https://www.example.com/#org" } instead of repeating the name and logo.
• Author pages define each Person with their own @id, and articles point to it in author.
• A page's WebPage block points to the WebSite with isPartOf and to its breadcrumb with breadcrumb.

Search engines and other parsers then see one organisation, one set of authors, and pages that belong to them. It also makes maintenance easier: change the logo once on the homepage and every page's publisher reference stays correct.

Seotific's own pages are built this way: one Organization and WebSite definition, and every guide's WebPage, BreadcrumbList and FAQPage blocks linked to it by @id. View the source of this page to see the full graph.

Common schema mistakes that hurt more than help

Markup that doesn't match the page. Wrong: Product markup showing a price of $99 on a page that displays $129, because the markup is cached. Right: generate the JSON-LD from the same data as the visible price. Mismatches break Google's structured data guidelines and can cost rich result eligibility.

Several conflicting blocks. Wrong: the theme outputs one Product block and a reviews app outputs another with a different name and rating. Right: one source per type, with the others disabled.

Self-serving reviews. Wrong: AggregateRating on your own LocalBusiness or Organization from testimonials you collected. Right: review markup only for products, or for things you review as a third party.

Marking up invisible content. Wrong: FAQPage JSON-LD with ten questions that appear nowhere on the page. Right: mark up only questions and answers a visitor can read.

Wrong type for the business. Wrong: LocalBusiness on a SaaS company with no premises. Right: Organization for online businesses, LocalBusiness only for places customers visit or areas you serve in person.

Tools for schema markup

Google's Rich Results Test shows which rich results a page is eligible for and flags missing required properties. The Schema.org validator checks any schema.org markup, including types Google doesn't use. Search Console's enhancement reports list errors across the whole site once markup is live.

Seotific lists every schema type on an audited page, validates required properties for the rich result types Google supports, and checks the homepage for Organization details. The schema generator writes valid JSON-LD for common types from a few fields. To see the types on any page quickly, the AI crawler access checker lists them alongside crawler access, and how to get cited by ChatGPT covers the content side of AI visibility.

Frequently asked questions