Technical
Structured Data for AI Search: What Actually Works in 2025
Search has fractured. Google Search still matters. ChatGPT search matters more than it did last year. Perplexity is a real source of qualified traffic. All three reward the same thing: machine-readable structure. Here is what is moving the needle for my sites this year.
Why Structured Data Matters Now
AI engines consume the web at scale and prefer clean signals. When your page has valid JSON-LD, the engine trusts its understanding of your content. When your page is soup, the engine guesses. Guesses get you missed or misrepresented.
The stakes are real. I have watched sites double their AI-referred traffic just by adding Article, BreadcrumbList, and Organization schema. The content did not change. The signals did.
The Schemas That Earn Their Keep
Article for blog posts, including author, datePublished, and dateModified. BreadcrumbList for navigation context. Organization for the site-level entity. FAQPage when the content is a question-and-answer. HowTo for tutorials with discrete steps.
I do not reach for exotic schemas. Five or six well-implemented types cover 95 percent of sites.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "Example Title",
"author": {"@type": "Person", "name": "Chadi Abi Fadel"},
"datePublished": "2025-08-20",
"dateModified": "2025-08-20",
"image": "https://example.com/cover.jpg",
"publisher": {
"@type": "Organization",
"name": "Example",
"logo": {"@type": "ImageObject", "url": "https://example.com/logo.png"}
}
}
</script>The Validation Discipline
Structured data that has errors is worse than no structured data. Engines that encounter invalid JSON-LD may distrust the entire page. I run every new template through Google's Rich Results Test before shipping. It takes 30 seconds and catches everything.
What I Stopped Doing
I stopped adding schema for every conceivable entity. I stopped nesting schemas four levels deep. I stopped marking up things that search engines already understand from the HTML. The good schemas are the few focused ones that match the page's actual purpose.
See the schema.org documentation for the full vocabulary. The half a dozen types above are enough for most content sites. Simple, validated, consistent beats clever every time.
RELATED READING
The Consulting Shift I Am Making In Year Two
After a year of writing and building, my consulting practice is changing shape. Shorter engagements. Sharper outcomes.
ReadThe Frontend Shift: Shipping Less JavaScript In Year Two
A year ago I reached for Next.js for everything. This year I often reach for nothing.
ReadThe Serverless Lesson I Would Write On A Sticky Note
After a year of shipping serverless projects, one rule explains most of the wins and all of the losses.
Read