7 min read · AI Visibility · Last updated July 2026
Quick answer: Use
Articlefor authoritative guides, white papers, and expert content. UseBlogPostingfor opinion pieces, news commentary, and conversational blog content. UseNewsArticlefor time-sensitive news reporting. The choice matters for AI citation because schema type signals the content’s purpose and authority level to both Google and AI extraction systems.
Introduction
When you implement content schema, you choose a content type from the Schema.org hierarchy. The options are not interchangeable: each type signals different content authority, intent, and freshness requirements to AI systems and Google.
Getting the type wrong is not catastrophic — Article and BlogPosting render similar rich results — but it does affect how AI systems categorize your content and whether it is treated as authoritative reference material or informal commentary.
What you’ll learn:
– The Schema.org Article hierarchy and what each type means
– When to use Article vs. BlogPosting vs. NewsArticle
– The required and recommended properties for each type
– How schema type affects AI citation treatment
– Complete JSON-LD templates for each content type
Table of Contents
- The Schema.org Article Hierarchy
- Article Schema: When and How
- BlogPosting Schema: When and How
- NewsArticle and TechArticle: Specialized Types
- Required vs. Recommended Properties
- Schema Type and AI Citation Treatment
- Live Article Schema Generator
- Frequently Asked Questions
The Schema.org Article Hierarchy
Schema.org organizes content types in an inheritance hierarchy:
Thing
└── CreativeWork
└── Article
├── NewsArticle
├── TechArticle
├── BlogPosting
│ └── LiveBlogPosting
└── ScholarlyArticle
Article is the parent type. BlogPosting, NewsArticle, and TechArticle are subtypes that inherit all Article properties and add type-specific signals.
This hierarchy matters because: a BlogPosting is an Article (inherits all properties), but an Article is not necessarily a BlogPosting (does not carry the informal/blog connotation).
Article Schema: When and How
Use Article for:
– Comprehensive how-to guides and tutorials
– Expert opinion pieces with high E-E-A-T signals
– White papers and research reports
– Industry analysis and data-driven content
– Content that you want treated as authoritative reference material
Article JSON-LD template:
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "How to Implement JSON-LD Schema for AI Visibility in 2026",
"description": "Complete guide to implementing JSON-LD structured data to improve AI citation rates and search visibility.",
"image": "https://ignitednepal.com/images/json-ld-guide-hero.jpg",
"datePublished": "2026-07-10",
"dateModified": "2026-07-10",
"author": {
"@type": "Person",
"name": "Priya Sharma",
"url": "https://ignitednepal.com/team/priya-sharma/"
},
"publisher": {
"@type": "Organization",
"name": "Ignited Nepal",
"logo": {
"@type": "ImageObject",
"url": "https://ignitednepal.com/images/logo.png"
}
},
"mainEntityOfPage": {
"@type": "WebPage",
"@id": "https://ignitednepal.com/blog/json-ld-schema-guide/"
},
"wordCount": 2800,
"keywords": ["JSON-LD", "structured data", "schema markup", "AI visibility"]
}
BlogPosting Schema: When and How
Use BlogPosting for:
– Informal opinion pieces and commentary
– Personal perspective content (“My experience with…”)
– News roundups and link posts
– Behind-the-scenes or conversational content
– Any content primarily associated with a blog feed rather than reference documentation
BlogPosting JSON-LD template:
{
"@context": "https://schema.org",
"@type": "BlogPosting",
"headline": "3 Things I Learned Running an AI Visibility Audit for 50 Clients",
"description": "Personal observations from running AI citation audits across 50 client accounts in various industries.",
"datePublished": "2026-07-10",
"dateModified": "2026-07-10",
"author": {
"@type": "Person",
"name": "Niraj Subedi",
"url": "https://ignitednepal.com/team/niraj-subedi/"
},
"publisher": {
"@type": "Organization",
"name": "Ignited Nepal",
"url": "https://ignitednepal.com"
},
"mainEntityOfPage": {
"@type": "WebPage",
"@id": "https://ignitednepal.com/blog/ai-audit-learnings/"
}
}
NewsArticle and TechArticle: Specialized Types
NewsArticle — for time-sensitive reporting and journalism:
– Requires datePublished (critical for freshness signals)
– Google News eligibility requires NewsArticle schema
– Best for industry news, announcements, and event coverage
– AI systems treat NewsArticle as time-stamped information with reduced shelf life
TechArticle — for technical documentation and developer content:
– Signals highly technical content aimed at practitioner audiences
– Useful for API documentation, code tutorials, developer guides
– Adds proficiencyLevel property (Beginner, Intermediate, Expert)
– AI systems may apply this type when generating content for technical queries
Required vs. Recommended Properties
Required for Google rich results validation:
– headline
– image (for article rich results)
– datePublished
– author
Strongly recommended for AI visibility:
– dateModified (signals freshness)
– publisher (signals source authority)
– description (used in AI summary generation)
– wordCount (signals content depth)
– mainEntityOfPage (canonical URL association)
Optional but beneficial:
– keywords (topic association)
– articleSection (category context)
– inLanguage (for multilingual sites)
– isPartOf (links to article series or publication)
Schema Type and AI Citation Treatment
AI systems use schema type as a content classification signal:
Article: Treated as reference material. Higher citation weight for informational queries. AI systems may cite it with language like “According to [author]…” or “Based on research from…”
BlogPosting: Treated as commentary or perspective content. May be cited for opinion-based queries (“What do practitioners say about…”). Lower citation weight for factual reference queries.
NewsArticle: Treated as time-stamped reporting. Cited for recency-dependent queries. Subject to freshness decay — older NewsArticles lose citation preference faster than evergreen Articles.
Practical implication: If you write comprehensive how-to guides that you want to be treated as authoritative references, use Article. If your content is primarily opinion or personal experience, BlogPosting is more accurate and better aligns AI citation treatment with actual content character.
Live Article Schema Generator
Article Schema Generator
Fill in your content details to generate JSON-LD
Frequently Asked Questions
Q: Does Google require Article schema to show article rich results?
A: Google uses Article schema to understand content type for rich results, but article rich results (author, date) can appear without explicit schema on pages it can parse as articles. Schema makes the association explicit and reliable.
Q: Can I use both Article schema and FAQPage schema on the same page?
A: Yes. Multiple schema types on the same page are supported. A long-form article with an FAQ section can have both Article schema (for the overall content) and FAQPage schema (for the Q&A pairs). Nest them as separate JSON-LD blocks.
Q: Does the schema type affect Google ranking?
A: Not directly. Schema type affects rich result eligibility and content classification, not organic ranking position. However, accurate schema type and comprehensive schema properties can improve click-through rates through rich result display.
Conclusion
Choosing the right Article subtype is a small but meaningful optimization signal. Use Article for authoritative, reference-quality content; BlogPosting for opinion and conversational content; NewsArticle for time-sensitive reporting. Combine with all recommended properties — especially dateModified, author, and publisher — for maximum AI extraction benefit.
Get AI-Ready with Ignited Nepal
We implement complete schema markup strategies including Article, BlogPosting, FAQPage, and Organization schemas tailored to your content architecture.
→ Request an AI Visibility Audit
Written by the Ignited Nepal AI Visibility team. ignitednepal.com