How to Use Structured Data and Schema for AI Search Visibility
Use structured data for AI search the way you would for classic search. Mark up what each page genuinely contains, such as your organisation, products, articles, authors, locations and tools, in JSON-LD. Match every value to the visible page and keep it current. Structured data helps search engines understand entities and facts. Microsoft has said schema helps its language models understand content, while Google says no special schema is needed for its AI features. It supports visibility; it does not create it. Clear content and third-party evidence still decide whether AI answers use and recommend you.
What does structured data actually do for AI search?
Structured data labels facts in a standard vocabulary, schema.org, so machines do not have to infer them from layout: this is the product name, this is its price, this is the author, this is the publication date. That helps in three ways:
- Understanding: systems can identify entities and their properties reliably.
- Consistency: the same facts are stated in a form that can be checked against other sources.
- Eligibility: in Google, correct markup makes pages eligible for certain rich results and shopping features.
What it does not do: guarantee inclusion in AI answers, compensate for thin content, or replace independent evidence. Google's guidance on AI features says there is no special schema.org structured data you need to add, and that structured data should match the visible text.
What does Bing say about schema's role in AI search?
Microsoft has been more positive than Google on this point. At the SMX Munich conference in March 2025, Fabrice Canel of Microsoft Bing confirmed that schema markup helps Microsoft's large language models, including those behind Copilot, understand content, as reported by Search Engine Land. So for Bing and Copilot, accurate markup is a reasonable part of making content understandable. It remains one input among many, alongside the content itself, crawlability and Bing's own index.
Which schema types help AI extract information: FAQPage, HowTo or Organization?
They do different jobs:
| Type | What it describes | Practical value for AI search |
|---|---|---|
| Organization | Your company's identity, logo, profiles, identifiers | Helps engines identify and disambiguate your business |
| FAQPage | A list of questions and answers written by you | Makes Q&A structure explicit; Google stopped showing FAQ rich results in May 2026 |
| HowTo | Step-by-step instructions | Google deprecated How-to rich results; the visible steps matter more than the markup |
Of the three, Organization markup usually has the clearest lasting value, because identity confusion is a common cause of wrong AI answers. See how to add Organization schema so AI can identify your business.
Which schema types should most websites use?
There is no universal list of ten; use the types that match your content. By site type:
| Site type | Priority schema types |
|---|---|
| Any business | Organization, BreadcrumbList, WebSite |
| Local business | LocalBusiness (with opening hours and address), Organization |
| Ecommerce | Product with Offer (merchant listing), Organization with return and shipping policies, BreadcrumbList |
| Software | SoftwareApplication or WebApplication, Organization |
| Publisher or blog | Article or BlogPosting, Person for authors, Organization |
| Events | Event |
| Video content | VideoObject |
| Data publisher | Dataset |
| Recipes | Recipe |
Add Review and AggregateRating only where genuine reviews are shown on the page. Treat FAQPage as optional. Product markup is covered in more depth in how to use Product JSON-LD so AI can understand your products.
How do schema types map to the questions buyers ask?
It helps to think from the question backwards. For each common buyer question, the answer should be on the page in plain text, and markup can reinforce the key facts:
| Buyer question | Where the answer should be | Supporting markup |
|---|---|---|
| "Who is [business] and where are they?" | About page, contact page | Organization, LocalBusiness |
| "What are their opening hours?" | Location page | LocalBusiness openingHoursSpecification |
| "How much does [product] cost, and is it in stock?" | Product page | Product with Offer |
| "What are the delivery and returns terms?" | Delivery and returns pages | Shipping details and return policy under Organization |
| "Who wrote this, and when?" | Article byline and dates | Article with author, datePublished, dateModified |
| "Is there a free tool for [task]?" | Tool page with explanation | WebApplication |
| "Where can I get the data behind [statistic]?" | Data page with findings | Dataset |
If a question has no clear answer on the page, adding markup will not help. Write the answer first, then mark it up. Working through this table for your own top ten buyer questions is often the quickest way to see where both content and markup are missing.
Does HowTo schema help AI cite step-by-step instructions?
Not in any way that has been shown. Google deprecated How-to rich results in 2023, so the markup no longer earns a visual result in Google Search. What does help AI cite instructions is the visible content: a numbered list of steps, each starting with an action, with the tools, time and warnings stated plainly. That format is easy to extract with or without markup. If your platform adds HowTo markup automatically and it is accurate, it does no harm; it is not worth a special project.
Does QAPage schema improve AI search visibility?
QAPage is intended for pages built around one question with answers submitted by users, such as forum threads and community Q&A sites. It is not meant for a business's own FAQ pages. On community sites where it fits, it describes the question, the answers and which answer is accepted. There is no evidence that adding it improves AI visibility for other kinds of site, and using it on the wrong page type misdescribes the content.
Does Article schema help AI assess an article's author and publication date?
It states them explicitly: author with a name and profile URL, datePublished and dateModified, headline and image. Google recommends including author details and dates in article markup. That supports clear attribution, but engines also read the visible byline and dates. Make sure both agree, link author names to real author pages, and update dateModified only when the content genuinely changes. Changing dates without real updates misleads readers and systems alike.
Is JSON-LD better than Microdata for Google and AI search?
Both express the same schema.org facts. Google recommends JSON-LD because it is easier to add and maintain: it sits in one script block rather than being woven through the HTML. For AI search, what matters is that the facts are correct and match the page, not the syntax. Most sites should use JSON-LD, and avoid publishing the same entity twice in different formats with different values.
Does Dataset schema help Google and AI understand your data?
If you publish datasets, such as research data, statistics or downloadable tables, Dataset markup describes them: name, description, creator, licence, temporal and spatial coverage, and download links. Google uses it for Google Dataset Search. For AI answers, the more important step is publishing the key findings as readable text and tables on the page, so they can be quoted and attributed. Dataset markup then helps the underlying data be found and credited.
Does WebApplication schema help AI assistants cite free online tools?
WebApplication, a type of SoftwareApplication, can describe a free online tool such as a calculator or converter: its name, category, the fact that it runs in a browser, and a price of zero. That helps search engines classify the page as a tool. For AI assistants, the tool page also needs readable text explaining what the tool does, the method or formula behind it, and example results, because assistants cannot usually run the tool. See whether interactive quizzes and calculators help a website appear in AI answers.
Do @graph schema bundles outperform standalone schema?
@graph is a JSON-LD feature that puts several connected entities in one block, such as the organisation, the website, the web page and the article, linked by @id. For example:
{
"@context": "https://schema.org",
"@graph": [
{ "@type": "Organization", "@id": "https://www.example.com/#org", "name": "Example Ltd" },
{ "@type": "Article", "@id": "https://www.example.com/guide#article",
"headline": "How to choose a payroll provider",
"publisher": { "@id": "https://www.example.com/#org" } }
]
}
It keeps relationships explicit and tidy. But there is no public evidence that bundling in @graph makes AI answers more likely to recommend you than separate, correctly linked blocks. Choose whichever your platform maintains reliably; the connections and the accuracy matter, not the packaging.
What does a structured data audit look like?
Audit by template, not page by page:
- List your templates: home, about, product, category, article, location, tool pages.
- Record what each outputs: open the page source and list every JSON-LD block and its type. Themes and plugins often add blocks you did not know about.
- Check for duplicates and conflicts: two Organization blocks with different names or logos, or two Product blocks with different prices.
- Compare values with the visible page: name, price, availability, dates, authors, addresses.
- Check the links between entities: do articles point to the same organisation
@id, do products name the right brand? - Validate each template with the Schema Markup Validator and Google's Rich Results Test.
- Assign an owner for keeping markup in sync when prices, addresses or authors change.
Fixing a template fixes every page that uses it, which is why this approach is far quicker than reviewing pages individually.
What mistakes do sites make with schema for AI?
- Marking up content that is not on the page, such as hidden FAQs or facts only in the markup.
- Fake or self-serving ratings, including aggregate ratings with no visible reviews behind them.
- Stale values, such as last year's prices, old addresses or dates that do not match the page.
- Wrong types, such as QAPage on a business FAQ or Product on a service page.
sameAslinks to profiles you do not own, or to general pages.- Keyword-stuffed descriptions that read differently from the visible text.
Each of these can make your markup less trustworthy, which undermines the one thing it is for: stating facts clearly.
How can you tell whether schema changes made a difference?
Roll changes out by template and watch a few signals. Search Console's rich result and merchant listing reports show whether Google reads the markup without errors. For Microsoft, Bing Webmaster Tools' AI Performance report shows whether pages are cited in Copilot and Bing's AI answers over time. And for all engines, re-run the questions those pages should answer, before and after, and check citations and the accuracy of stated facts. If accuracy improves, for example correct prices and addresses in answers, the markup and the matching content are doing their job.
How should you prioritise schema work against other AI visibility work?
In most audits, structured data is a supporting fix rather than the main one. A sensible order:
- Crawler access and readable HTML, because markup cannot help a page that cannot be fetched.
- Clear, specific content that answers buyer questions.
- Consistent facts across your site, listings and profiles.
- Accurate Organization, LocalBusiness and Product markup, which reinforce identity and key facts.
- Other types that match your content.
If you are unsure whether a gap needs markup, copy or outreach, see how to decide whether an AI visibility gap needs schema, copy or digital PR.
What do people ask about schema and AI search?
Can wrong schema hurt AI visibility?
Markup that contradicts the page can confuse systems and, in Google, lead to rich results being ignored. Fix or remove inaccurate markup.
Do AI assistants read JSON-LD at all?
Some systems parse it, and Microsoft has said its models benefit from schema. Many AI answers still rely mainly on visible text, which is why markup should repeat what the page says rather than add to it.
How do I test my structured data?
Use the Schema Markup Validator for general schema.org checks and Google's Rich Results Test for Google-specific features, then compare values with the visible page.
Is schema worth it for a small business website?
Yes, for the basics: Organization or LocalBusiness with correct name, address, hours and profiles. Most platforms and SEO plugins make this quick.
Published by The Kovmere Team · updated Sep 28, 2026 · More resources