Schema Markup for AI Search: What to Add and Where

When an AI assistant reads your website, it has to work out what your business is, what you sell, where you operate and which page answers which question. Usually it guesses from the text. Structured data removes some of that guessing.

This guide explains how to use schema markup for AI search: what it is, what the platforms have said about it, which types to add on which pages, a working JSON-LD example and how to test it. It is part of our complete AI SEO guide, where structured data is step four of the framework.

What schema markup is

Schema markup is a standard vocabulary, maintained at schema.org, for describing things on a web page in a format machines can read. Instead of a crawler inferring that "Greater Noida" is your location and "₹15,000" is a price, the markup states it explicitly.

The recommended format is JSON-LD: a small block of code inside a <script type="application/ld+json"> tag, usually in the page head. It does not change how the page looks to visitors.

Does schema markup help AI search?

It is worth being precise here, because the platforms have said different things.

Google says structured data is not required to appear in its generative AI features, and that there is no special schema.org markup to add for AI Overviews or AI Mode. Its May 2026 guidance for site owners puts the focus on helpful content, crawlability and good page experience. Google still uses structured data for rich results in regular search.

Microsoft puts more weight on it. At SMX Munich in March 2025, Fabrice Canel of the Bing team said schema markup helps Microsoft's large language models understand content. Bing's index also powers the web answers in Copilot.

Our view from client work: schema does not guarantee a citation, and no markup will rescue a weak page. What it does is remove ambiguity. It states your business name, services, products, prices, locations and official profiles in one consistent, machine readable place. That consistency supports everything else in AI SEO, especially entity SEO, and it costs very little to add.

Which schema types to add, page by page

You do not need every type. Start with the homepage, then your highest value service or product pages, then content.

Organization schema: your entity anchor

Organization schema on the homepage is the single most useful block, because it tells machines who you are and links your website to your official profiles elsewhere. Those sameAs links help systems connect your site, your Google Business Profile, LinkedIn page and other profiles into one entity.

Here is a working example using @graph to combine Organization and Service markup:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Organization",
      "@id": "https://example.com/#organization",
      "name": "Example Events Co",
      "url": "https://example.com/",
      "logo": "https://example.com/images/logo.png",
      "description": "Drone light shows for weddings, product launches and corporate events across India.",
      "telephone": "+91 00000 00000",
      "sameAs": [
        "https://www.linkedin.com/company/example-events-co",
        "https://www.instagram.com/exampleeventsco",
        "https://www.youtube.com/@exampleeventsco"
      ]
    },
    {
      "@type": "Service",
      "name": "Wedding drone light shows",
      "serviceType": "Drone light show",
      "provider": { "@id": "https://example.com/#organization" },
      "areaServed": { "@type": "Country", "name": "India" },
      "url": "https://example.com/wedding-drone-shows"
    }
  ]
}
</script>

The @id lets other blocks on other pages refer back to the same organisation, so every service and article points to one consistent entity.

Service, Product and LocalBusiness markup

Service markup should describe what you actually sell, using the same name as the page heading. Include areaServed for the cities, states or countries you cover, and an offers block or price range if you publish pricing.

Product markup matters most for online stores. Include price, currency, availability, brand and real images. Keep it in sync with the visible page: a price in the markup that differs from the price on the page is a problem for both Google and buyers. Most Shopify themes output basic Product schema; check that it includes everything above and is not duplicated by an app.

LocalBusiness markup suits businesses with a physical location or a defined service area. Use the most specific subtype available, such as Dentist or RealEstateAgent, and match the name, address and phone number exactly to your Google Business Profile.

Article, Person and BreadcrumbList for content

For guides and blog posts, BlogPosting or Article markup states the headline, author, publisher and dates. Person markup on an author page, with sameAs links to the author's professional profiles, connects content to a real expert. BreadcrumbList shows where each page sits in the site structure.

These types help machines understand who wrote what, when, and how your content fits together, which supports the topical structure described in our on page SEO checklist.

FAQPage after the end of FAQ rich results

Google limited FAQ rich results to a small set of government and health websites in 2023, and stopped showing them in Search altogether in May 2026. So do not add FAQPage markup expecting extra space in Google results.

FAQPage is still valid schema.org vocabulary, and a visible FAQ built from real customer questions remains one of the most useful sections for buyers and for assistants, because each answer is a self contained passage. If you have a visible FAQ, marking it up is a low cost way to label it clearly. Never mark up questions that are not shown on the page. Our guide on how to write content AI assistants quote covers how to write the answers themselves.

Common schema mistakes

• Markup that does not match the page. Prices, names, ratings or FAQs in the code that visitors cannot see.
• Fake or self serving reviews. Google does not show star ratings from reviews a business publishes about itself on LocalBusiness and Organization pages, and invented reviews break its guidelines.
• Duplicate blocks. A theme, an SEO plugin and an app all outputting their own Organization or Product markup with conflicting details.
• Missing sameAs links, which weakens the connection between your site and your profiles.
• Schema added only by JavaScript. Google can render JavaScript, but many AI crawlers do not run it. Where possible, put JSON-LD in the HTML the server sends.
• Set and forget. Prices, services and addresses change. Markup that is a year out of date sends wrong facts to every system that reads it.

How to test and validate

1. Schema Markup Validator at validator.schema.org checks any schema.org markup for errors.
2. Google's Rich Results Test shows which Google rich result types a page is eligible for.
3. Search Console reports errors for supported types such as Product, Breadcrumb and Article.
4. View source on the live page and search for application/ld+json to confirm the markup is in the HTML.

Run these after any theme change, plugin update or site migration. Schema is often lost silently during redesigns, which is one reason it appears in our technical SEO checklist.

On a real account

For a smart TV brand on Shopify, we added product and FAQ schema alongside restructured collection and product pages and answer ready copy. Comparing August 2026 with February 2026 in GA4, organic search users grew from 172 to 3,286 a month. Schema was one part of that work, not the whole of it, which is how it should be treated. See the Shopify SEO case study, or explore our ecommerce development work.

Get your structured data checked

We review schema as part of every free SEO and AI visibility audit: what is present, what is missing, what conflicts and what each priority page needs. You can also see what our AI SEO services include.