?AEO Tool

Structured data for AI search: what helps, what does not

Short answer

Structured data is not required to appear in AI search: Google says there is no special schema.org markup for its AI features. It is still worth adding a few accurate types, chiefly Organization or LocalBusiness on the home page, plus Product, Article and BreadcrumbList where they fit, because they state your key facts unambiguously, connect your site to your official profiles, and make pages eligible for Google’s rich results.

What Google says about structured data and AI

In its 2026 guide to generative AI features in Search, Google is direct: structured data is not required for its AI features, and there is no special schema.org markup to add for them. The same fundamentals as normal Search apply.

That does not make markup useless. It has three real benefits:

Which types are worth adding

TypeWhereWhy
OrganizationHome pageOfficial name, logo, contact details and profiles
LocalBusiness (or a subtype such as Dentist, Restaurant, Store)Home or contact page, if customers visit you or you serve an areaAddress, opening hours, geo-coordinates, price range
WebSiteHome pageThe site name Google can show in results
BreadcrumbListEvery page below the home pageShows where a page sits in the site
Product with OfferProduct pagesPrice, availability, ratings; product rich results
Article or BlogPostingArticles and guidesHeadline, author, publication and update dates
PersonAbout or author pagesWho is behind the business and the content

Example: Organization

Put this on the home page, with your real values. The @id gives the organisation a fixed identifier that other markup on your site can point to.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "@id": "https://www.example.com/#organization",
  "name": "Example Interiors",
  "url": "https://www.example.com/",
  "logo": "https://www.example.com/logo.png",
  "email": "[email protected]",
  "telephone": "+91-98765-43210",
  "sameAs": [
    "https://www.linkedin.com/company/example-interiors",
    "https://www.instagram.com/exampleinteriors"
  ]
}
</script>

Example: LocalBusiness

If customers visit you, use the most specific LocalBusiness subtype that fits. Google requires name and address; opening hours, phone and geo-coordinates are recommended.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Dentist",
  "@id": "https://www.example.com/#organization",
  "name": "Smile Dental Clinic",
  "url": "https://www.example.com/",
  "telephone": "+91-22-1234-5678",
  "priceRange": "₹₹",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "12 Hill Road, Bandra West",
    "addressLocality": "Mumbai",
    "postalCode": "400050",
    "addressCountry": "IN"
  },
  "geo": { "@type": "GeoCoordinates", "latitude": 19.0544, "longitude": 72.8300 },
  "openingHoursSpecification": [{
    "@type": "OpeningHoursSpecification",
    "dayOfWeek": ["Monday","Tuesday","Wednesday","Thursday","Friday","Saturday"],
    "opens": "10:00", "closes": "19:00"
  }]
}
</script>

On other pages, such as a reviews page, do not repeat a partial copy of the business. Refer to it instead: {"@id": "https://www.example.com/#organization"}.

Common mistakes

Where structured data fits in AEO

Think of markup as finishing work. If AI crawlers cannot reach your site, or your pages do not answer the questions customers ask, markup changes nothing. Fix access and content first (see What is AEO?), then add accurate markup for the types above.

Questions

Does schema markup make ChatGPT recommend me?

Not on its own. No AI company has said structured data is a ranking factor for its answers, and Google says none is needed for its AI features. Markup helps machines read your facts correctly; whether you are recommended depends mostly on access, useful content and what other sites say about you.

Is FAQ schema still worth adding?

Google stopped showing FAQ rich results in May 2026, so it no longer changes how your pages look in Google. Google says it may still use the markup to understand pages, and other systems may read it. Keep it where it matches a real, visible FAQ; do not add FAQ sections only for the markup.

JSON-LD, microdata or RDFa?

JSON-LD. Google recommends it, it sits in one script block instead of being mixed into your HTML, and it is the easiest to maintain.

Can markup describe things that are not on the page?

No. Structured data must match what visitors can see. Markup that claims ratings, prices or details not shown on the page breaks Google’s guidelines and can lead to a manual action.