Reference guide · technical-seo · Published 2026-08-16 · 3 min read

NewsArticle rather than Article structured data

NewsArticle versus Article structured data, when each applies, the required and recommended properties, and rich result eligibility.

Two types in one family

In schema.org, NewsArticle is a subtype of Article. A NewsArticle inherits the article type's properties and adds its own, chiefly dateline and printColumn, and it signals to Google that the page is a current news story rather than an evergreen article. Both sit inside the broader structured data system alongside BreadcrumbList and Article-based rich results.

The practical question is which one the page actually is, because Google's eligibility differs between the two.

What each rich result requires

Google treats Article and NewsArticle with different eligibility bars. The honest summary:

SignalArticleNewsArticle
Required propertyThe headline and image requirements apply to bothSame baseline, plus it should be a news story
Publishing contextGeneral article, blog post, reportA news story reported and published on your site
Editorial standardBroadly applicableRequires Google News editorial criteria
Eligibility outcomeTop Stories / Article rich results under specific rulesNews surfaces, may feed Google News

The shared requirement is that Google checks both the structured data and the visible page, and it will ignore markup it considers misapplied. Google's own guidance is explicit: the newsarticle type is for reporting on timely news events. A how-to blog post is an Article, and calling it a NewsArticle does not make it eligible for news surfaces.

The properties that carry the difference

For any Article-style page, base markup starts the same way, with headline, image, author, datePublished, and dateModified. The NewsArticle layer adds the reporting-specific fields:

{
  "@context": "https://schema.org",
  "@type": "NewsArticle",
  "headline": "Independent coffee shops report quieter June",
  "datePublished": "2026-08-10T08:00:00Z",
  "dateModified": "2026-08-11T14:30:00Z",
  "author": [{ "@type": "Person", "name": "Amina Yusuf" }],
  "dateline": "Leeds",
  "printColumn": "Local business"
}

dateline names the place the report was filed, and printColumn names the section, two properties that only make sense for a news report. If you cannot fill those honestly, the page is probably an Article, not a NewsArticle.

When to choose which

Choose by the truthful nature of the content, not by a desire for a richer result:

  1. Evergreen or general content: a guide, a report you will not update daily, a blog post. Use Article.
  2. A timely news story your outlet reported, with a dateline, an author, and a publication date. Use NewsArticle.
  3. A hybrid where a story is also a reference. Use Article plus a secondary NewsArticle only if genuinely maintained, and always keep JSON-LD nesting and the page markup consistent.

The trust signal matters more than the property name. Google sets a clear editorial bar for news surfaces, and site and entity markup should match reality so the structured data Google sees describes the page it already read. Marking an ordinary post as news does not help and can undermine the page's credibility signal.

Need a website built, fixed, optimised, migrated or replaced?

This technical resource is written by CSMBAC, a small design and development studio. If you would rather hand the problem to a professional, the website service page explains how we build enquiry-ready websites.

Explore website services