Schema Markup Checklist for AI
Implement the essential structured data that helps AI engines understand and cite your content accurately.
About this checklist
This checklist covers the schema types that matter most for AI engine visibility — from foundational types like Article and Organization to high-impact types like FAQ, HowTo, and Product. Each item explains what the schema does, why AI engines value it, and common implementation mistakes.
Implementing structured data is one of the highest-ROI activities in AEO. Brands that add comprehensive JSON-LD markup consistently see higher citation rates within weeks, as AI engines can more confidently extract and attribute information from their pages.
Foundational Schema Types
- 1
Organization schema on your homepage
Establishes your brand entity with name, URL, logo, and social profiles for AI knowledge graphs.
- 2
WebSite schema with search action
Helps AI engines understand your site's purpose and structure at a high level.
- 3
BreadcrumbList on all pages
Shows AI engines your site hierarchy and the relationship between pages.
- 4
Article schema on blog posts and editorial content
Includes headline, author, datePublished, and dateModified for freshness signals.
- 5
WebPage schema with description and dateModified
Provides page-level metadata that AI engines use for indexing and recency evaluation.
High-Impact Schema for AI
- 1
FAQPage schema on pages with Q&A content
Directly maps to how AI engines construct responses — one of the highest-impact schema types.
- 2
HowTo schema on instructional content
Step-by-step markup helps AI engines structure procedural responses that cite your content.
- 3
Product schema on product and service pages
Enables AI engines to include your products in comparison and recommendation responses.
- 4
Review / AggregateRating on product pages
Social proof signals that AI engines use when recommending products and services.
- 5
SoftwareApplication schema for SaaS products
Provides pricing, features, and platform information for AI engine product recommendations.
Implementation Best Practices
- 1
Use JSON-LD format (not Microdata or RDFa)
JSON-LD is the preferred format for AI engines — it is easier to parse and less error-prone.
- 2
Place JSON-LD in the <head> section
While JSON-LD can appear anywhere in the HTML, the <head> ensures it is parsed before any rendering issues.
- 3
Include only one primary entity type per page
Avoid conflicting schema — one Article or one Product per page, not both.
- 4
Nest related types under the primary entity
Author inside Article, Offers inside Product — nesting shows relationships.
- 5
Keep markup aligned with visible page content
Schema that contradicts visible content is a spam signal and will hurt AI trust.
- 6
Include image URLs in schema where applicable
AI engines increasingly reference images — include them in your structured data.
Validation & Quality Checks
- 1
Run all pages through Schema.org validator
Check for syntax errors, missing required properties, and deprecated types.
- 2
Test with Google Rich Results Test
Validates that your markup meets Google's requirements and shows preview of rich results.
- 3
Verify no duplicate schema types on the same page
Multiple conflicting schema blocks can confuse AI engines about page purpose.
- 4
Check that dateModified updates when content changes
Stale dates signal to AI engines that content may be outdated.
- 5
Audit schema coverage across all page templates
Ensure every template type in your CMS has appropriate schema markup built in.
Schema Markup Checklist for AI FAQ
Explore more resources
Complete AEO Audit Checklist
A step-by-step audit to evaluate and improve your site's readiness for AI answer engines.
llms.txt Template and Guide
Create and optimise your llms.txt file to help AI engines understand your site's purpose and structure.
AI-Optimised Content Brief Template
Create content briefs that produce articles optimised for both human readers and AI engine citations.
Start with the pages and proof that AI can actually use
Run the free audit to see what blocks AI from citing your site. Use the trial when you need ongoing monitoring, attribution, prompt discovery, and team workflows after the first fixes are live.