Schema markup (structured data) gives machines explicit information about a page's subject, author, publisher, and content type. It should describe what a reader can actually see; it does not guarantee that an AI search product will cite the page.
Why Schema Matters for AI
Schema markup gives search and retrieval systems structured signals that can:
- Clarify content type — Is this an article, a FAQ, a how-to guide, or a product page?
- Identify authors — Who wrote this content and what are their credentials?
- Surface key facts — What are the steps, questions, or key data points?
- Signal freshness — When was this published and last updated?
Without schema, machines must infer more of this information from the page text and HTML structure.
JSON-LD: The Recommended Format
JSON-LD (JavaScript Object Notation for Linked Data) is often the simplest format to generate and maintain. It is:
- Supported and documented by major search platforms
- Easier to implement and maintain
- Placed in a <script> tag without adding schema annotations throughout the visible markup
- Separate from the visible markup while still required to match it
Essential Schema Types
Article Schema
Use on blog posts, news articles, and long-form content:
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "Your Article Title",
"description": "A concise summary of the article",
"author": {
"@type": "Person",
"name": "Author Name",
"url": "https://yoursite.com/about/author"
},
"publisher": {
"@type": "Organization",
"name": "Your Organization"
},
"datePublished": "YYYY-MM-DD",
"dateModified": "YYYY-MM-DD"
}
FAQPage Schema
Use on FAQ pages and pages with question-answer content:
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What is AEO?",
"acceptedAnswer": {
"@type": "Answer",
"text": "AEO (AI Engine Optimization) is the practice of optimizing your website for AI search engines."
}
}
]
}
Tip: Use FAQPage only when the visible page meets the schema type's requirements. Do not add it solely in pursuit of an AI citation.
HowTo Schema
Use on tutorial and step-by-step content:
{
"@context": "https://schema.org",
"@type": "HowTo",
"name": "How to Implement Schema Markup",
"description": "Step-by-step guide to adding JSON-LD schema",
"step": [
{
"@type": "HowToStep",
"name": "Choose your schema type",
"text": "Identify the most appropriate schema type for your content."
},
{
"@type": "HowToStep",
"name": "Generate the JSON-LD",
"text": "Create the structured data using the examples in this guide."
},
{
"@type": "HowToStep",
"name": "Add to your page",
"text": "Place the script tag in your page's head section."
}
]
}
Organization Schema
Use on your homepage:
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Your Organization",
"url": "https://yoursite.com",
"description": "What your organization does",
"sameAs": [
"https://twitter.com/yourorg",
"https://linkedin.com/company/yourorg"
]
}
Implementation Steps
- Audit existing schema — Check what schema you already have using Google's Rich Results Test
- Map content to schema types — Decide which schema type fits each page template
- Add schema to templates — Implement in your CMS template or page layout
- Validate — Use the Schema.org Validator to check for errors
- Monitor — Track AI citation rates before and after implementation
Common Mistakes
- Missing
dateModified— AI systems use this for freshness signals. Always include it. - Generic descriptions — Use specific, content-relevant descriptions, not your site tagline.
- No author information — Readers cannot verify who is responsible for the content.
- Wrong schema type — Don't use Article schema on a product page or vice versa.
- Duplicate schema — Having multiple conflicting schema blocks confuses AI systems.
Choose Schema by Page Meaning
Use the most specific schema type that truthfully matches the visible page:
| Schema Type | Use it for | Verify |
|---|---|---|
| FAQPage | Eligible visible question-and-answer content | Questions and answers appear on the page |
| HowTo | A genuine process with ordered steps | Required step properties are present |
| Article | Editorial articles and guides | Headline, author, publisher, and dates match the page |
| Organization | A named organization | Identity and URLs are accurate |
Validation
After implementing schema, validate with:
- Google Rich Results Test
- Schema.org Validator
- The AEO NIUEXA — run a scan to check your Structural score
Key takeaway: Correct schema reduces ambiguity. Start with the page types you can represent accurately, validate the output, and keep it synchronized with visible content.
Related Guides
- Content to go with your schema: See How to Write Citation-Ready Content for AI Search for the content layer of optimization
- Full audit checklist: Schema is check #4 in our 15-point AI-readiness audit
- Platform-specific guidance: Review the current crawler and publishing guidance in our ChatGPT and Perplexity guides