Schema Markup for AI Search: Which Types Matter in 2026

Schema markup for AI search is one of the most discussed SEO topics of 2026. Brands want to know which structured data types help Google, AI Overviews and AI assistants understand their pages, and which ones are no longer worth the effort.

This guide covers the six types most businesses ask about: Organization, Product, FAQ, Article, LocalBusiness and BreadcrumbList. It includes Google’s current rules on FAQ rich results, what Google says about AI features, and a JSON-LD example you can adapt.

Does schema markup help with AI search?

Google’s guidance on AI features and your website (last updated December 2025) is direct: there are no additional requirements to appear in AI Overviews or AI Mode, and there is no special schema.org structured data you need to add. Its best practices include making sure structured data matches the visible content on the page.

So schema is not a shortcut into AI answers. Its value is clarity. Structured data tells search systems, in a standard format, that a page is a product with a specific price, an article by a named author, or a business at a specific address. That reduces ambiguity about your brand and offers, which supports both classic search results and AI-generated summaries that draw on the same index.

What are Google’s current rules on FAQ rich results?

FAQ rich results have been phased out in stages:

• August 2023: Google announced in its Search Central blog that FAQ rich results would be limited to well-known, authoritative government and health websites.
• 8 May 2026: Google’s documentation updates log added a deprecation notice stating the feature would no longer appear in Google Search starting 7 May 2026.
• 15 June 2026: Google removed the FAQ rich result documentation, noting the feature is no longer shown in Google Search results.

What this means for you: FAQPage markup will not produce expandable FAQ results in Google. Leaving existing markup on your pages does no harm, and the visible FAQ content itself is still useful for readers and for any system that reads the page text. Do not add FAQPage markup expecting a Google rich result.

Which schema types matter most in 2026?

How should you use Organization schema?

Google’s Organization documentation says the markup helps Google understand your organisation’s administrative details and can influence elements such as the logo shown in search results and knowledge panels. There are no required properties.

Add it to your home page or About page. Useful properties include name, url, logo, address, contactPoint, sameAs (links to your official social profiles) and legalName. Ecommerce brands can use the OnlineStore subtype and add hasMerchantReturnPolicy and hasShippingService.

How should ecommerce brands use Product schema?

Google’s Product documentation separates two uses. Merchant listings are for pages where customers can buy the product. Product snippets suit pages where people cannot buy directly, such as review articles.

For a D2C store, focus on merchant listing details: name, image, price, currency, availability, brand and SKU, plus ratings, shipping and return policy where they apply. Most Shopify themes output basic Product markup, but it is often incomplete. Check it before assuming it is correct.

What about Article schema for blogs?

Google supports Article, NewsArticle and BlogPosting, with no required properties. Recommended properties are headline, image, datePublished, dateModified and author, including the author’s name and a profile URL.

Google’s guidance asks you to list every author shown on the page, use Person for people and Organization for companies, and keep author.name to the name only, without job titles. Accurate dates and authors help readers and search systems judge how current and credible a piece is.

When should you use LocalBusiness schema?

Use LocalBusiness if customers visit you in person, such as a retail store, clinic or office. Google’s LocalBusiness documentation lists name and address as required, and recommends telephone, url, openingHoursSpecification, geo and priceRange.

Use the most specific subtype available, such as Store or Restaurant, and create a separate page with its own markup for each location. Keep the details identical to your Google Business Profile.

Why add BreadcrumbList schema?

BreadcrumbList shows where a page sits in your site structure, for example Home, Sunglasses, Aviator Classic. Google’s documentation requires at least two ListItem entries, each with a position and name, and an item URL for all but the last entry. It is quick to add and makes your site hierarchy explicit.

What does a JSON-LD example look like?

Google’s introduction to structured data recommends JSON-LD in most cases, because the markup sits separately from the visible HTML. Here is a simplified example for a product page that combines OnlineStore, BreadcrumbList and Product in one block:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "OnlineStore",
      "@id": "https://www.example.com/#organization",
      "name": "Example Eyewear",
      "url": "https://www.example.com/",
      "logo": "https://www.example.com/logo.png",
      "sameAs": [
        "https://www.instagram.com/exampleeyewear",
        "https://www.linkedin.com/company/exampleeyewear"
      ]
    },
    {
      "@type": "BreadcrumbList",
      "itemListElement": [
        {"@type": "ListItem", "position": 1, "name": "Sunglasses", "item": "https://www.example.com/collections/sunglasses"},
        {"@type": "ListItem", "position": 2, "name": "Aviator Classic"}
      ]
    },
    {
      "@type": "Product",
      "name": "Aviator Classic Sunglasses",
      "image": "https://www.example.com/images/aviator-classic.jpg",
      "description": "Metal aviator sunglasses with polarised lenses.",
      "sku": "AV-001",
      "brand": {"@type": "Brand", "name": "Example Eyewear"},
      "offers": {
        "@type": "Offer",
        "price": "2499.00",
        "priceCurrency": "INR",
        "availability": "https://schema.org/InStock",
        "url": "https://www.example.com/products/aviator-classic"
      }
    }
  ]
}
</script>

Replace every value with your real data, and only include details that also appear on the page. For example, if the price on the page is ₹2,499, the markup must say the same.

What schema mistakes should you avoid?

Most structured data problems come from templates and apps, not from the schema itself. Watch for these common issues:

• Markup that does not match the page: prices, stock status or ratings in the code that differ from what users see.
• Duplicate markup: a theme and an SEO app both adding Product or Organization blocks, sometimes with conflicting values.
• Incomplete objects: Google notes that fewer but complete and accurate properties are better than many badly formed ones.
• Broken markup after updates: theme changes or app removals can silently break structured data, so monitor Search Console after every release.

Schema markup checklist for 2026

1. Add Organization or OnlineStore markup to your home page, with logo and official social profiles in sameAs.
2. Add complete Product markup to every product page, including price, currency, availability, brand and SKU.
3. Add Article or BlogPosting markup with headline, dates and a named author to every blog post.
4. Add LocalBusiness markup to each store or office page, matching your Google Business Profile.
5. Add BreadcrumbList markup to category, product and article pages.
6. Keep existing FAQPage markup if it is already there, but do not expect a Google rich result.
7. Use JSON-LD and make sure every value matches what users see.
8. Test pages with Google’s Rich Results Test before publishing, and monitor Search Console reports after launch.

How Squarebase can help

Squarebase audits and implements structured data as part of technical SEO for Shopify and WordPress sites, and checks it against Google’s current rules. Explore our search engine optimisation services or talk to the team about a schema audit.

Frequently asked questions

Sources

• Google Search Central: AI features and your website
• Google Search Central: Latest documentation updates
• Google Search Central Blog: Changes to HowTo and FAQ rich results
• Google Search Central: Introduction to structured data
• Google Search Central: Organization structured data
• Google Search Central: Product structured data
• Google Search Central: LocalBusiness structured data
• Google Search Central: Article structured data