Schema markup and AI answers: what actually helps (and what's myth)

Sooner or later someone files a ticket: "Add schema so we show up in ChatGPT." It sounds reasonable. Structured data is machine-readable, AI is a machine, so more markup must mean more AI visibility.

It's not that simple. Here's what the documentation actually says, what's worth shipping on a SaaS site, and which claims to push back on.

Google's guide to AI features (AI Overviews and AI Mode) is blunt: there's no special schema.org markup you need to add to appear in them, and no special AI files either. A page has to be indexed and eligible to show with a snippet. That's the bar.

The same guide does list structured data among the usual best practices, with one condition: it should match what's visible on the page. Google's general structured-data policies say the same thing in stronger terms: don't mark up content readers can't see, and the markup must be "a true representation of the page content."

Two more points from those policies that matter here:

As for ChatGPT, Perplexity and Gemini outside Search: none of them, as far as I can find, publicly documents using schema.org markup to decide what to cite. That doesn't prove they ignore it. It means any "schema gets you cited by ChatGPT" claim is a guess.

Because structured data is still useful for what it was designed for:

Think of it as hygiene, not a growth hack.

Tells search engines who you are and links your official profiles together.

<script type= "application/ld+json" > { " @context ": " https://schema.org ", " @type ": " Organization ", " name ": " Acme Invoices ", " url ": " https://acme.example ", " logo ": " https://acme.example/logo.png ", " sameAs ": [ " https://www.linkedin.com/company/acme-invoices ", " https://www.youtube.com/@acmeinvoices " ] } </script> Enter fullscreen mode Exit fullscreen mode Only list profiles you actually own and keep up to date.

This is the type that can earn a software rich result in Google. Its documentation (checked October 2026) requires name, offers.price, and either aggregateRating or review. It recommends applicationCategory and operatingSystem.

<script type= "application/ld+json" > { " @context ": " https://schema.org ", " @type ": " SoftwareApplication ", " name ": " Acme Invoices ", " applicationCategory ": " BusinessApplication ", " operatingSystem ": " Web ", " offers ": { " @type ": " Offer ", " price ": " 19.00 ", " priceCurrency ": " EUR " } } </script> Enter fullscreen mode Exit fullscreen mode Notice what's missing: aggregateRating. Without real ratings this markup won't qualify for the rich result, and that's fine. Don't invent a rating to unlock it. Google's review snippet guidelines apply, ratings must be visible on the page, and breaking the guidelines can get your structured data ignored through a manual action. If you do show genuine reviews on the page, add aggregateRating that matches them exactly.

The markup is still worth having for clear entity facts, as long as the price matches the pricing table.

Low effort, and it states your site's structure explicitly instead of leaving it to be guessed from URLs.

Author, date published, date modified. Keep dateModified honest: bumping it without changing the content is a well-known trick that helps nobody.

If the goal really is "show up in AI answers," three checks will tell you more than any amount of markup:

For the first check, we have a free AI crawler checker at Presence Scout that shows what your robots.txt allows and what your server actually returns to seven AI and search crawlers: https://presencescout.com/tools/ai-crawler-checker

Ship the schema, keep it truthful, and don't expect it to do a job it was never documented to do.

I'm Ankit, and I work on marketing at Presence Scout, which tracks how brands appear in AI answers and Google results. Sources: Google Search Central ("AI features and your website", "General structured data guidelines", "Software app structured data", Search Central changelog), read 21 October 2026.