What schema markup do AI search engines use?

AI search engines primarily read Organization (entity verification), Product/Service (commercial queries), FAQPage (Q&A citations), Article (content authority), and BreadcrumbList (site structure). JSON-LD is the required format — Microdata and RDFa are not reliably parsed by AI engines.

What is the difference between JSON-LD, Microdata, and RDFa?

JSON-LD is a JavaScript notation injected in a tag, completely separate from your HTML. Microdata and RDFa are embedded within HTML attributes. AI engines and Google strongly prefer JSON-LD because it is cleanly separated from markup, easier to validate, and can be added without modifying page templates.

How many schema types should I deploy?

At minimum: Organization (homepage), Product or Service (offering pages), FAQPage (any page with Q&A content), and Article (blog/content pages). Each additional relevant schema type adds another set of facts that AI engines can read.

Can I use schema markup generators or do I need custom code?

Schema generators work for basic Organization and Product schemas. For AEO-oriented markup, you need custom schemas with sameAs entity verification, semantic triple content, and cross-page entity linking. The ADV Strategy Pro Search-to-Sale Landing Page ($697, exactly 1 page) is deployed with structured data (JSON-LD). The $197 Search Opportunity Action Plan gives structured data recommendations only and does not install schema.

Schema Markup for AI Search: The Complete JSON-LD Guide for 2026

By ADV Strategy Pro · AEO Research Team · Last updated: March 17, 2026

JSON-LD schema markup is the machine-readable layer that AI search engines parse to understand your website. Google AI Overviews, Perplexity, and ChatGPT Search use structured data to verify entities, extract facts, and select citation sources. Without JSON-LD, your site gives the AI answer layer less machine-readable information, even if it ranks well in organic search.

The 6 Essential Schema Types for AI Citation

OrganizationDeploy on: Homepage

Establishes your entity in Knowledge Graph. Required for sameAs verification. Without it, AI engines can't confirm your business exists.

{ "@type": "Organization", "name": "Your Company", "url": "https://...", "sameAs": ["https://linkedin.com/company/..."], "knowsAbout": ["AEO", "structured data"] }

Product / ServiceDeploy on: Offering pages

Answers commercial queries: 'How much does X cost?', 'Where to buy X?'. AI engines extract price, availability, and description directly from this schema.

{ "@type": "Service", "name": "Your Service", "provider": { "@type": "Organization" }, "offers": { "price": "...", "priceCurrency": "USD" } }

FAQPageDeploy on: Any page with Q&A content

Marks up question and answer pairs so AI engines can read them directly. A page that answers questions without FAQ schema gives engines less structured data to work with.

{ "@type": "FAQPage", "mainEntity": [{ "@type": "Question", "name": "...", "acceptedAnswer": { "@type": "Answer", "text": "..." } }] }

ArticleDeploy on: Blog posts, guides, content pages

Signals content authority with headline, author, publisher, datePublished, and dateModified. Fresh dateModified values tell AI engines your content is maintained.

{ "@type": "Article", "headline": "...", "author": { "@type": "Organization" }, "dateModified": "2026-03-17" }

BreadcrumbListDeploy on: Every page

Maps your site hierarchy for AI engines. Helps them understand page relationships and navigate your content graph. Simple to implement, adds structural context to every page.

{ "@type": "BreadcrumbList", "itemListElement": [{ "@type": "ListItem", "position": 1, "name": "Home" }] }

LocalBusinessDeploy on: Location pages (if applicable)

Critical for local queries: 'best [service] near me'. Includes address, geo coordinates, opening hours, and service area. AI engines use this for local citations.

{ "@type": "LocalBusiness", "name": "...", "address": { "@type": "PostalAddress" }, "geo": { "latitude": "...", "longitude": "..." } }

Why JSON-LD (Not Microdata or RDFa)

Three formats exist for structured data: JSON-LD, Microdata, and RDFa. For AI search optimization, JSON-LD is the only practical choice:

JSON-LD

Required

Separate from HTML in a <script> tag. Google recommended. All AI engines parse it. Easy to add without touching templates.

Microdata

Avoid

Embedded in HTML attributes. Fragile — breaks when templates change. Not reliably parsed by AI engines. Google supports but doesn't prefer.

RDFa

Avoid

Similar to Microdata — embedded in HTML. More complex syntax. Low adoption. Not used by any major AI engine as a primary parsing target.

Common Schema Mistakes

Missing sameAs on Organization

Without links to LinkedIn, Google Business Profile, etc., your entity can't be verified

No FAQPage schema

Q&A content without FAQ schema means AI engines have to infer the question and answer pairs from page text

Stale dateModified

Article schema with a dateModified from 2023 signals abandoned content to AI engines

Missing price in Product/Service

Commercial queries need price data. 'Contact us for pricing' in schema = no citation for price queries

Where Structured Data Fits in Our Offers

The Search-to-Sale Landing Page is exactly 1 page deployed with structured data (JSON-LD), SSL and global CDN, with a delivery target of 72 hours after approved brief and required assets.

The Search Opportunity Action Plan is a diagnostic that includes structured data recommendations, with a delivery target of 48 hours after receipt of the onboarding questionnaire and competitor URLs. It does not implement or install schema.

Open the Free Readiness Guide JSON-LD Deep Dive