Structured data and AI Overviews

There is no AIPage schema type. There is no LLMOptimized property. There is no "AI Overview metadata" extension. Google has been explicit on this. If a vendor is selling you "AI schema markup," ask them which @type it uses, then check Google's structured data gallery. It will be a normal type with a new name attached for the invoice.

That said, here is what schema does do that intersects with AI Overviews:

1. It earns rich-result eligibility. Product cards, recipe cards, video previews, organization knowledge panels. AI Overviews can include these elements when the underlying content has the right schema. So VideoObject indirectly helps your video appear inside an AI Overview answer.
2. It helps entity recognition. Organization schema with sameAs linking to your Wikidata, Wikipedia, and social profiles helps Google identify your brand consistently.
3. It can disambiguate. Article schema with author, datePublished, and dateModified makes it unambiguous who wrote the page and when. The author_signal check in our tool looks at exactly this.

What it does not do:

• Boost ranking specifically for AI Overviews.
• Make a page appear in AI Overviews that would not otherwise.
• Substitute for actual content quality.

The other rule that catches teams out

"Making sure your structured data matches the visible text on the page." Source: Google AI features in Search

Schema must match what is visible. If your Product schema says the price is $49 but the visible page says $99, Google may issue a manual action ("hidden or mismatched structured data"). Worse, the model might cite the wrong number.

Our AI Overview Checker runs a specific check for this: it pulls the name, headline, and description fields from your JSON-LD and grep-checks them against the visible page text. Mismatches fail the check.

What to actually implement

Implement schema for what your content is, not for AI Overviews specifically. The highest-leverage types when the content matches:

Example: Article schema done correctly

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Why we waived the inspection: a look inside the sewer line",
  "author": {
    "@type": "Person",
    "name": "Herman Schutte",
    "url": "https://example.com/authors/herman-schutte"
  },
  "datePublished": "2026-05-12",
  "dateModified": "2026-05-18",
  "image": "https://example.com/images/sewer-scope.jpg",
  "publisher": {
    "@type": "Organization",
    "name": "Example",
    "logo": {
      "@type": "ImageObject",
      "url": "https://example.com/logo.png"
    }
  }
}
</script>

Three things make this work for AI Overviews:

• headline matches the visible <h1> (no mismatch flag)
• author is a real Person with a URL (passes the author signal check)
• dateModified reflects a real update (passes freshness checks)

Verify

Google's Rich Results Test shows which rich results your page is eligible for. If your Article schema is valid but Article rich results are not shown as eligible, look at the warnings: usually a missing required field.

Our AI Overview Checker flags both invalid JSON-LD (parse errors, which Google silently ignores) and mismatched JSON-LD (where the JSON does not match the visible text). Both are common causes of schema being silently discarded.

• Adding schema fields that do not match visible content. The classic case: a Product schema lists priceRange $10-$50 while the visible page only shows a single $99 price. Google may issue a manual action.
• Invalid JSON-LD. A trailing comma, an unescaped quote in description. The block parses to nothing. Google silently ignores it.
• Using FAQPage schema for content that is not actually FAQ. Rich result eligibility for FAQs has been narrowed. Most pages no longer qualify even with valid schema.
• Forgetting @context. Without "@context": "https://schema.org", the block is not interpreted as schema.org markup at all.
• Wrapping multiple separate items in one @graph array but giving them no @ids. Google has trouble linking the entities together.