What is the Schema.org hierarchy for article types?
Schema.org organizes types in a hierarchical inheritance model. Every type inherits the properties of its parent. Understanding this hierarchy explains why BlogPosting and NewsArticle are both subtypes of Article. And why they're appropriate for different content.[1]
CreativeWork
└── Article ← Parent type (generic)
├── BlogPosting ← Subtype for personal expert posts
├── NewsArticle ← Subtype for journalism and news reporting
├── TechArticle ← Subtype for technical documentation
├── ScholarlyArticle ← Subtype for academic research
└── SocialMediaPosting ← Subtype for social content
Because BlogPosting and NewsArticle both inherit from Article, any page correctly marked as BlogPosting is also implicitly an Article. AI engines read the most specific type you've declared. So declaring BlogPosting gives AI more information than declaring Article.
The principle that follows: always declare the most specific valid type. If your content is a personal, dated, post. BlogPosting. If it's time-sensitive news reporting. NewsArticle. If it's neither specifically but is some form of written editorial. Article.
How do Article, BlogPosting, and NewsArticle compare side by side?
The table below captures the practical differences between the three types. What each is for, what it signals to AI, and its relative value for authority sites.
| Schema Type |
Best For |
datePublished Required? |
Author Required? |
AI Signal Strength for Content |
Article |
General editorial writing, cornerstone guides, institutional content not tied to a specific blog or person |
Recommended |
Recommended |
Moderate. Valid but generic; doesn't distinguish blogs from institutional content |
BlogPosting |
Expert Q&A nodes, authority directory posts, personal methodology content, dated opinion pieces |
Recommended |
Required for full E-E-A-T signal |
Strong. Signals specific, dated, authored content; best match for AI recommendation of individual experts |
NewsArticle |
Time-sensitive reporting, industry news, event coverage, press releases |
Required (Google) |
Required (Google) |
Weak for evergreen. Temporal signal; AI may deprioritize for informational queries as content ages |
The table makes clear that for an expert building an authority directory. Content designed to be evergreen, authoritative, and attributed to a named expert. BlogPosting is the correct choice on every node.[2]
Why is NewsArticle the wrong schema for content?
NewsArticle was designed for journalism. Its defining characteristics. a dateline, a reporter byline, time-sensitive relevance. Are the signals it sends to AI engines. When AI sees NewsArticle, it classifies the content as current-events reporting, which has a natural freshness curve: the older the NewsArticle, the less relevant it becomes for most queries.
Evergreen content. A guide to schema markup, an explanation of how AI discovers experts, a breakdown of authority website architecture. Doesn't have a freshness curve. It's correct today and correct in two years. Classifying it as NewsArticle misaligns its expected longevity with AI's temporal weighting model for news content.[3]
The practical consequence: content marked as NewsArticle may see declining AI citation rates as it ages, not because the content is wrong, but because the schema type implies it should have expired. BlogPosting doesn't carry this implication.
When is generic Article schema actually appropriate?
Article schema is not wrong. It's just broad. There are contexts where it's the most accurate type:
- Institutional content published by an organization rather than an individual (a company blog with rotating writers, for example)
- Cornerstone guides that function as reference documents rather than dated posts. Where the "blog post" framing doesn't quite fit
- Research summaries or white papers that don't fit neatly into a blog post format or a news article format
For most entrepreneurs running an authority directory, however, BlogPosting is a better match than generic Article because their content is personally authored, dated, and in the style of blog writing. Article is a reasonable fallback when BlogPosting doesn't fit. Not a substitute for specificity when it does.[4]
What does this look like in practice on an authority directory?
On this site. Vibecodeyourleads.com. Every node uses BlogPosting schema. The choice is deliberate and consistent. Each node is:
- Written by a named expert (Cindy Anne Molchany)
- Published on a specific date with a datePublished property
- Organized as a direct answer to a specific query
- Designed to be evergreen. Accurate for years, not hours
This matches the BlogPosting classification precisely. The schema type is not a technicality. It's a description of what the content actually is. When schema type and content type align, AI receives a coherent, reliable classification signal. When they don't. When evergreen content is marked as NewsArticle, or a service page is marked as Article. The signal is muddied.
The authority directory built to get you AI-recommended is one where every layer of signal is internally consistent: the content answers a specific query, the BlogPosting schema classifies it as authored, the FAQPage schema extracts the answers, and the Author schema attributes it to a verified identity. That consistency is what AI engines reward.
The VCYL Perspective
The schema type decision seems minor. A single property in a JSON block. But it reflects a more important principle: every technical choice in your site should accurately describe what your content actually is. Schema is not a box to check. It's a description you're writing for machines.
When I look at sites that are getting AI-recommended, they share a pattern: every classification layer is honest and specific. The schema type matches the content. The author object matches the actual author. The FAQ schema matches the visible FAQ section. AI engines are pattern-matching for coherence. And coherence between your visible content and your schema markup is one of the clearest signals of a trustworthy, well-organized site.
For the Authority Directory Method, the BlogPosting choice is both accurate and strategic. Accurate because these posts are exactly what BlogPosting describes: personal, dated, personally voiced responses to specific queries. Strategic because BlogPosting is the schema type that most directly signals "individual expert, answering a specific question, on a specific date". Which is precisely the signal that gets you recommended when someone asks AI for expert help in your field.
