Choosing the wrong schema type does not trigger an error. Your page still loads, your structured data still validates, and nothing obviously breaks. The problem is subtler: you miss the rich results you qualified for, signal the wrong content type to search crawlers, and leave AI systems with an imprecise picture of what your page actually is. Article, BlogPosting, and NewsArticle are three distinct schema.org types that serve different content formats, unlock different Google features, and carry different signals for AI citation systems. Understanding which applies to your content is one of the most underrated decisions in structured data strategy.

How Schema.org Defines These Three Types

Schema.org organizes these types in a strict hierarchy. Article is the parent class. BlogPosting and NewsArticle both inherit from Article, meaning they share all of Article's properties while adding their own specialized context.

This hierarchy matters because it determines what Google expects, what it can render as a rich result, and how AI systems interpret the content category. Applying a child type like NewsArticle to evergreen how-to content is technically valid schema.org markup, but it misrepresents the nature of the content to every system that reads it.

Article Schema
The base schema.org type for any written content, including how-to guides, explainers, opinion pieces, and long-form evergreen content that does not fit a more specific subtype.
BlogPosting Schema
A schema.org subtype of Article used for blog posts and informal written content published in reverse-chronological format, typically associated with a single author's or brand's blog.
NewsArticle Schema
A schema.org subtype of Article used for journalistic reporting on current events, press coverage, or time-sensitive news content published by editorial organizations.

The Core Differences: A Direct Comparison

The three types overlap significantly, but the distinctions matter across three dimensions: intended content format, Google rich result eligibility, and AI extraction signals.

Dimension Article BlogPosting NewsArticle
Schema.org position Parent class Child of Article Child of Article
Primary use case Evergreen reference content, guides, explainers Blog posts, opinion pieces, informal editorial Breaking news, current events, press coverage
Inherits Article properties N/A (is Article) Yes Yes
Google Top Stories eligibility No No Yes (primary path)
Google Discover rich result Yes Yes Yes
Publisher eligibility Any content publisher Blogs, brands, media News organizations (Google News approval helps)
Timeliness expectation None Optional Required
Recommended dateModified Yes Yes Critical
AI signal: content category Generic article Personal or brand perspective Journalistic, time-sensitive
Risk of misuse Low Low to medium High if applied to evergreen content

When to Use Article Schema

Article is the safest and most broadly applicable choice for most content teams. Apply it to any written content that is neither a blog post nor news reporting: product explainers, pillar guides, comparison articles, how-to tutorials, industry overviews, whitepapers, and FAQ pages.

Google explicitly lists Article as appropriate for "news, sports, or blog content" in its documentation, which creates some confusion. In practice, using Article as a fallback for content that does not clearly fit BlogPosting or NewsArticle is always defensible and frequently optimal.

For SaaS companies, agencies, and ecommerce brands, Article is the right schema for cornerstone content. It signals that the page is a substantive, category-level resource rather than a timestamped post or a news report. The schema types that most directly affect SEO and GEO include Article as a primary driver of content classification for AI systems, not just search crawlers.

When Article Schema Is the Right Default

Apply Article schema when:

  • The content is evergreen and not tied to a publication date
  • The page serves an informational or educational purpose
  • The content does not belong to a blog feed or news section
  • The topic is broad enough to be a pillar or reference document
  • You are unsure which subtype fits and want a safe, semantically accurate choice

When to Use BlogPosting Schema

BlogPosting signals that the content is a blog post: authored, relatively informal, published as part of a blog feed, and typically representing a single perspective. It is the appropriate type for brand blogs, founder journals, opinion content, and thought leadership posts that live under a /blog/ path.

The distinction from Article is not about length or quality. A 3,000-word analysis published on a company blog is still a BlogPosting. The distinction is about publishing context and content format. Blog posts are expected to have a clear author, a publication date, and an informal or perspective-driven tone.

When BlogPosting Schema Is the Right Choice

Apply BlogPosting schema when:

  • The content is published in a blog format with a visible date and author
  • The post represents an opinion, perspective, or editorial voice
  • The content lives under a blog section of the site
  • The page is part of a reverse-chronological content feed
  • The brand is a company blog rather than a news organization

One practical note for agencies managing structured data across multiple client sites: the schema markup management approach across client portfolios consistently shows that BlogPosting is over-applied to evergreen pillar content. If a page is a reference document that will be updated and maintained over time, Article is more accurate than BlogPosting, even if it lives on the blog.

When to Use NewsArticle Schema

NewsArticle is the type with the most specific eligibility requirements and the highest risk of misapplication. It signals to Google that the content is journalistic reporting on current events, and it is the primary schema path to Google Top Stories, which is one of the most prominent rich result formats in search.

Google's own documentation states that NewsArticle is intended for "news content" and that Top Stories eligibility is tied to meeting Google News content policies. A SaaS blog that applies NewsArticle to a product announcement is not automatically disqualified from anything, but the schema type misrepresents the content category and offers no rich result advantage over Article.

Misusing NewsArticle on evergreen content can create a more subtle problem: it signals to AI systems that the content is time-sensitive, which may cause those systems to treat it as potentially outdated rather than as a stable reference. The relationship between schema markup and AI search behavior shows that content type signals influence how AI systems weight freshness versus authority, making accurate type selection a GEO consideration, not just an SEO one.

When NewsArticle Schema Is the Right Choice

Apply NewsArticle schema when:

  • The content is reporting on a current event or breaking news
  • The publishing organization functions as a news outlet
  • The content has a clear publication date and will not be updated significantly
  • The goal includes Top Stories eligibility and the site meets Google News standards
  • The content is written in a journalistic style with sourcing and factual reporting conventions

What NewsArticle Schema Does Not Help With

Do not apply NewsArticle to:

  • Product announcements, even if framed as news
  • Company blog posts covering industry trends
  • Opinion columns and thought leadership from brand blogs
  • Evergreen guides that will be updated over time
  • Press releases republished on a company site

Does Google Actually Treat These Types Differently?

Yes, but with important nuance. Google's documentation acknowledges that all three types can surface in Google Discover and standard web search rich results. The meaningful differentiation happens in two places.

First, Top Stories is the most visible Google rich result category for news content, appearing prominently in Google Search on mobile. NewsArticle schema is the primary structured data path to Top Stories eligibility. Neither Article nor BlogPosting opens that path.

Second, Google has stated in various contexts that it does not always enforce strict distinctions between Article and BlogPosting. The search engine often treats them interchangeably for ranking and rich result purposes. This is why some practitioners default to Article for all editorial content rather than maintaining a distinction. The practical risk of using Article where BlogPosting might be more precise is low. The practical risk of using NewsArticle where it does not apply is higher, because it creates a false freshness signal.

A useful way to think about the decision: Article and BlogPosting compete for the same rich results and Google treats them with similar weight. NewsArticle opens a distinct category of rich results reserved for editorial news organizations, and applying it outside that context provides no benefit while potentially distorting content category signals. The broader question of whether schema markup measurably improves SEO rankings depends heavily on whether the correct type is used for the correct content.

Schema Type Selection for Common Content Formats

Different teams and business types publish content in different formats. The right schema type depends on matching the type to the actual content format, not the business category.

Content Format Recommended Schema Type Rationale
Evergreen how-to guide Article Not time-sensitive; reference document
Long-form pillar page Article Broad reference; not a blog post format
Company blog post (opinion) BlogPosting Authored, perspective-driven, dated
Company blog post (tutorial) Article or BlogPosting Either is defensible; Article preferred if evergreen
Product announcement BlogPosting Company news, not journalistic reporting
Breaking news coverage NewsArticle Journalistic, time-sensitive
Industry trend analysis Article or BlogPosting Depends on publishing context
Press release BlogPosting or Article Not a news article in the journalistic sense
FAQ page Article + FAQPage Add FAQPage schema alongside
Comparison article Article Reference format; not a blog post
Case study Article Research and evidence; not a post format
Opinion column (media site) NewsArticle or Article Depends on publisher type

The GEO Dimension: How Schema Type Affects AI Citation

Schema markup is not just a search signal. AI systems that crawl the web for training data and retrieval use structured data to classify content and assess its authority level. Accurate schema type selection sends a cleaner signal to these systems about how to treat the content when constructing answers.

A page marked as NewsArticle on a topic where the query is evergreen tells AI systems the information may be time-stamped and potentially superseded. A page marked as Article on the same topic signals that the content is a stable reference. For AI systems weighing whether to cite a source for a definitional or explanatory query, that classification distinction influences the selection. The signals that tell AI systems your brand is authoritative include structured data accuracy as a contributing factor alongside entity consistency and topical depth.

AuthorityStack.ai's free schema generator scans any URL and generates the appropriate JSON-LD markup, including recommending the correct Article subtype based on the page's content structure. This is particularly useful for content teams managing large article libraries where schema type decisions were made inconsistently across dozens or hundreds of pages.

The broader point is that schema type selection is a GEO decision as much as an SEO decision. Getting it right requires understanding what each type signals, not just what each type validates against.

Implementation: What the JSON-LD Looks Like

The structural difference between the three types in JSON-LD is minimal: one property changes. The properties that matter most for search and AI extraction remain the same across all three types.

Article Schema (JSON-LD)

{
 "@context": "https://schema.org",
 "@type": "Article",
 "headline": "Your Article Title",
 "author": {
 "@type": "Person",
 "name": "Author Name"
 },
 "publisher": {
 "@type": "Organization",
 "name": "Organization Name",
 "logo": {
 "@type": "ImageObject",
 "url": "https://example.com/logo.png"
 }
 },
 "datePublished": "2025-01-01",
 "dateModified": "2025-06-01",
 "description": "A clear one-sentence description of the article.",
 "image": "https://example.com/image.jpg"
}

BlogPosting Schema (JSON-LD)

{
 "@context": "https://schema.org",
 "@type": "BlogPosting",
 "headline": "Your Blog Post Title",
 "author": {
 "@type": "Person",
 "name": "Author Name"
 },
 "publisher": {
 "@type": "Organization",
 "name": "Organization Name"
 },
 "datePublished": "2025-06-01",
 "dateModified": "2025-06-01",
 "description": "A one-sentence description of the post.",
 "image": "https://example.com/image.jpg"
}

NewsArticle Schema (JSON-LD)

{
 "@context": "https://schema.org",
 "@type": "NewsArticle",
 "headline": "Your News Headline",
 "author": {
 "@type": "Person",
 "name": "Reporter Name"
 },
 "publisher": {
 "@type": "Organization",
 "name": "News Organization Name",
 "logo": {
 "@type": "ImageObject",
 "url": "https://example.com/logo.png"
 }
 },
 "datePublished": "2025-06-15T10:00:00+00:00",
 "dateModified": "2025-06-15T10:00:00+00:00",
 "description": "A factual summary of what the article reports.",
 "image": "https://example.com/news-image.jpg"
}

The key practical difference is that NewsArticle benefits from precise ISO 8601 timestamps with timezone offsets, because freshness is a ranking signal for Top Stories. For Article and BlogPosting, the date format is less critical, though including dateModified is good practice across all three types. If you are adding schema to pages at scale, the process of generating JSON-LD schema markup automatically is more practical than building each block by hand.

After implementing any of these types, validating your schema markup and resolving structured data errors is a necessary next step. Google's Rich Results Test and Schema.org's validator both process all three types and surface property-level issues that affect rich result eligibility.

Common Mistakes Content Teams Make

Applying NewsArticle to Company Blog Content

The most frequent misapplication is using NewsArticle on brand blog posts, particularly product announcements, that are framed as company news. These posts are not journalistic reporting, and the schema type signals a content category they do not belong to. BlogPosting is correct for these posts; NewsArticle provides no benefit and introduces a misleading freshness signal.

Using BlogPosting on Pillar Pages

Content teams that route all blog content through BlogPosting schema create a different problem: their most authoritative evergreen content gets classified as casual blog posts. A 4,000-word definitive guide to a technical topic deserves Article schema, not BlogPosting, even if it lives under /blog/. The publishing path does not determine the schema type. The content format and intent do.

Omitting dateModified on Updated Content

All three types benefit from an accurate dateModified property, and NewsArticle essentially requires it for Top Stories. Many implementations set datePublished correctly and leave dateModified at the same value permanently. When content is refreshed, updating dateModified signals to both search crawlers and AI systems that the information is current. This is particularly important for incorrect schema markup practices that risk penalties, where stale dates on frequently updated content can create inconsistencies that flag as misleading structured data.

Stacking Multiple Article Types on One Page

Some implementations apply both Article and BlogPosting to the same page, either in the same JSON-LD block or across multiple blocks. Schema.org does not prohibit this, but it is redundant and potentially confusing. Pick the most specific applicable type and use it once.

Clear Recommendations by Use Case

Use Case Recommended Type Notes
SaaS knowledge base article Article Evergreen reference; not a blog post
Agency pillar guide Article Broad topic coverage; reference format
Ecommerce buying guide Article Product comparison; stable reference
Local business service page Article Informational, not news or blog
Founder's personal blog BlogPosting Authored perspective; dated content
Brand content marketing blog BlogPosting Most posts; unless clearly evergreen pillar
Evergreen tutorial on company blog Article Content format overrides publishing path
Trade publication news report NewsArticle Journalistic, time-sensitive
Press release on company site BlogPosting Company announcement, not journalism
Industry roundup on news site NewsArticle If site has editorial news function

FAQ

What Is the Difference Between Article and BlogPosting in Schema.org?

Article is the parent schema.org type for written content, suitable for evergreen guides, explainers, and reference documents. BlogPosting is a subtype of Article specifically designed for blog posts: authored, dated, perspective-driven content published as part of a blog feed. The two share identical properties, but BlogPosting signals a more informal, personal publishing context. For content that functions as a stable reference document, Article is the more accurate choice regardless of where the page lives on the site.

Does Using NewsArticle Schema Make Any Page Eligible for Google Top Stories?

No. NewsArticle schema is a necessary but not sufficient condition for Top Stories eligibility. Google also requires that the content meet its news content policies, that the site follow its technical guidelines, and that the content be journalistic reporting on current events. A company blog post using NewsArticle schema does not become Top Stories-eligible. The content type and publishing organization must also qualify, and approval through Google News strengthens eligibility significantly.

Does Google Treat Article and BlogPosting as the Same Thing?

In practice, Google treats them very similarly for web search rich results and Discover eligibility. Both types can surface the same rich result formats, and Google has indicated it does not strictly differentiate between them in most ranking contexts. The distinction matters more for AI citation systems and semantic clarity than for immediate Google rich result differences. That said, using the more precise type is always the better practice, because it provides an accurate signal to every system that reads the markup.

Can I Use More Than One Article Schema Type on the Same Page?

Technically yes, but it is unnecessary and inadvisable. Applying both Article and BlogPosting to the same page adds no benefit and creates redundancy that can confuse crawlers. Select the single most accurate type for the content and implement it once in the page's JSON-LD.

Should I Use Article Schema on FAQ Pages?

A FAQ page benefits from both Article (or the applicable subtype) as the primary content type and FAQPage schema for the question-and-answer content itself. These two types serve different purposes: Article classifies the page as written content, while FAQPage enables the FAQ-specific rich results that display individual answers in Google Search. Using both together is the recommended approach.

Does Schema Type Affect How AI Systems Like ChatGPT and Perplexity Cite Content?

Yes, indirectly. AI systems use structured data as one of several signals to classify content and assess its reliability. A page correctly marked as Article signals a stable, authoritative reference. A page incorrectly marked as NewsArticle signals time-sensitive content, which may cause AI systems to treat it as potentially outdated when answering queries that call for evergreen information. Accurate schema type selection is a GEO consideration alongside being an SEO one, because both audiences use the same structured data to make classification decisions.

What Happens If I Use the Wrong Schema Type?

Google will not penalize a page simply for using BlogPosting where Article might be more precise. The risks are more about missed opportunity than active harm: using NewsArticle on non-news content provides no rich result benefit and introduces a misleading freshness signal, while using BlogPosting on pillar content may result in those pages being classified as informal posts rather than authoritative references. Neither constitutes a markup violation, but both represent a failure to use structured data to its full advantage.

How Do I Validate That My Article Schema Is Implemented Correctly?

Google's Rich Results Test (available at search.google.com/test/rich-results) accepts a URL or code snippet and shows which rich results the page is eligible for, along with property-level errors and warnings. Schema.org's own validator at validator.schema.org provides a more detailed view of how the markup is parsed. Both tools process Article, BlogPosting, and NewsArticle and will surface missing required properties or formatting issues that affect eligibility.

Final Verdict

The choice between Article, BlogPosting, and NewsArticle is simpler than it appears once the logic is clear:

  • Use Article for evergreen guides, pillar pages, comparison articles, how-to tutorials, explainers, and any written content that functions as a stable reference. It is the correct default for most SaaS, agency, ecommerce, and service business content.
  • Use BlogPosting for dated, authored blog posts that represent an opinion, perspective, or editorial voice published in a blog feed. It is appropriate for most brand blog content that is not a pillar guide or evergreen resource.
  • Use NewsArticle only for genuinely journalistic reporting on current events, published by an organization that functions as a news outlet. Do not apply it to product announcements, company blog posts, or evergreen industry analysis.

When in doubt between Article and BlogPosting, choose Article. When uncertain about NewsArticle, assume it does not apply unless the content is unambiguously journalistic. The cost of using Article where BlogPosting would be more precise is minimal. The cost of using NewsArticle where it does not belong is a distorted content classification signal that neither search engines nor AI systems can use accurately.

Accurate schema markup is foundational to both search visibility and AI citation. Use the AuthorityStack.ai schema generator to generate correct JSON-LD for any page instantly, then track how your structured content performs across ChatGPT, Claude, Gemini, and Perplexity with AuthorityStack.ai's AI visibility platform, and improve your AI visibility as your content library grows.