Does structured data help AI search?

What does Google officially say about structured data and AI features?

Two lines on Google’s AI features page (Search Central, viewed 2026-11-04) concern structured data. One lists, among basic search best practices, making sure structured data matches the visible text on the page. The other says there is no special schema.org structured data you need to add. In other words, Google does not make structured data a condition for appearing in AI Overviews or AI Mode.

We also read the OpenAI and Perplexity crawler documentation (2026-11-04). Neither page mentions structured data, schema.org or JSON-LD; they cover crawler names, robots.txt and IP lists. So “add schema and ChatGPT will cite you” has no official support. We found no reliable controlled experiment, so we do not claim it helps and we do not claim it does not.

Should you add it anyway?

Yes, for a practical reason: structured data writes “who you are, what the product is called, what it costs” as fields a machine can read directly instead of guessing from body text, and Google Search rich results and knowledge panels read it too. That is a clear benefit for search. Whether it helps AI citations has no official answer, but a machine reading you clearly beats one guessing. It ranks behind these:

• Crawlers can get in (robots.txt and CDN allow them)
• Body text is written directly in the HTML
• You appear in the pages AI cites

How to check all three is in the AI visibility audit checklist; to confirm crawlers can get in first, use the AI crawler check.

Which types still matter?

Google’s 2023-08-08 blog post says FAQ rich results are shown only for well-known government and health sites and no longer regularly for others; existing FAQPage markup does not need to be removed proactively. HowTo was first limited to desktop with no mobile display, and a September update the same year said it no longer appears on desktop either. Neither markup breaks a page; it just no longer earns the expanded look in search results.

What does structured data look like on real sites?

A kagentx evaluation reads the JSON-LD on the homepage and two inner pages. The results for the two public cases on the day of evaluation:

Both sites have JSON-LD, and both are missing sameAs on Organization. MochiStamp has one more gap: the body has an FAQ but no FAQPage markup. This is how they looked on evaluation day, not after any fix; given the status above, adding FAQPage matters little for rich results, so sameAs is the better first fix.

What does a minimal working JSON-LD look like?

1. 1. Put this in the head of your homepage

   Organization plus SoftwareApplication in one block via @graph, with the SoftwareApplication’s publisher pointing back to the Organization. Replace example.com and every field with your own:

   <script type="application/ld+json">
   {
     "@context": "https://schema.org",
     "@graph": [
       {
         "@type": "Organization",
         "@id": "https://example.com/#org",
         "name": "Example Co",
         "url": "https://example.com/",
         "logo": "https://example.com/logo-512.png",
         "sameAs": [
           "https://x.com/example",
           "https://github.com/example"
         ]
       },
       {
         "@type": "SoftwareApplication",
         "name": "Example App",
         "url": "https://example.com/",
         "description": "One sentence: what it does and who it is for.",
         "applicationCategory": "BusinessApplication",
         "operatingSystem": "Web",
         "publisher": { "@id": "https://example.com/#org" },
         "offers": {
           "@type": "Offer",
           "price": "19.00",
           "priceCurrency": "USD"
         }
       }
     ]
   }
   </script>

   Every field must match something visible on the page. The price shown is 19.00 USD; replace it with the price on your page. Without real reviews, do not add aggregateRating.

2. 2. Check it with Google’s Rich Results Test

   Paste your homepage URL and look for errors. Note: for a software app rich result Google requires a rating or review, which this snippet leaves out, so it will not produce one; the markup itself is still valid and the Organization part is read as usual.

3. 3. Confirm it is in the raw HTML

   Run this in a terminal. An output above 0 means the markup is in the server-rendered HTML, so crawlers can read it without running scripts:

   curl -s https://your-site.com/ | grep -c "application/ld+json"

4. 4. Update it whenever the price or name changes

   Google’s guidance is that structured data should match the visible text on the page. Whenever you change the price or product name, change both places.

FAQ

Sources

• Google Search Central · AI features and your website （checked 2026-11-04）
• Google Search Central · Changes to HowTo and FAQ rich results （Published 2023-08-08, updated 2023-09-14; viewed 2026-11-04）
• Google Search Central · Structured data markup that Google Search supports （checked 2026-11-04）
• Google Search Central · Software App (SoftwareApplication) structured data （checked 2026-11-04）
• Google Search Central · Organization structured data （checked 2026-11-04）
• OpenAI · Overview of OpenAI Crawlers （checked 2026-11-04）
• Perplexity · Perplexity Crawlers （checked 2026-11-04）
• kagentx evaluations: the data on the case study pages; each example gives its date.