NewsArticle Schema

What NewsArticle schema is

NewsArticle is a type in the schema.org vocabulary. It is a more specific version of the general Article type, purpose-built for journalism: news reports, press coverage, breaking stories. You add it as a block of JSON-LD in the page and it hands Google a clean, machine-readable summary of the story: the headline, who published it, who wrote it, when it went live, when it was last updated, and the lead image.

This check flags news pages that are missing that markup. Without it Google still crawls and reads your article, but it has to guess at the structure from your HTML. With it, you remove the guesswork and become eligible for news-specific search features that plain articles never see.

Why it matters for news publishers

The whole point of NewsArticle is eligibility. Google's Top Stories carousel, the dedicated News tab, and the news rich result treatments all draw from content Google understands to be timely journalism. Structured data is one of the clearest signals you can send that a page belongs in that pool. It is not a magic ranking lever, but it is a gate: a well-marked story can be considered for placements a bare page cannot.

Freshness is the other half. News is a game of minutes. NewsArticle carries explicit datePublished and dateModified fields, so Google reads the exact timestamp rather than inferring it. For a breaking story that gets updated four times in an hour, an accurate dateModified is what tells Google the piece is live and current, not stale.

There is a subtype worth knowing about. Schema.org also defines LiveBlogPosting for running live coverage and ReportageNewsArticle for original, on-the-ground reporting. For most publishers plain NewsArticle is the right default, but if you run live blogs, mark those specifically.

The properties that matter

Google's structured data documentation splits NewsArticle fields into required and recommended. Get the required ones right first, then fill in the recommended ones because they materially improve how your result renders.

What the markup looks like

Use JSON-LD in a script tag. It sits in the page separate from your visible HTML, which makes it easy to template and easy to maintain. A minimal, valid block reads like this:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "NewsArticle",
  "headline": "City council approves new transit budget",
  "image": ["https://example.com/story-16x9.jpg"],
  "datePublished": "2026-07-01T08:15:00-04:00",
  "dateModified": "2026-07-01T09:40:00-04:00",
  "author": [{"@type": "Person", "name": "Jane Reporter", "url": "https://example.com/staff/jane"}],
  "publisher": {
    "@type": "Organization",
    "name": "Example News",
    "logo": {"@type": "ImageObject", "url": "https://example.com/logo.png"}
  }
}
</script>

The single most common mistake I see is markup that disagrees with the page. If your JSON-LD says the author is Jane and the byline on the page says Sam, or the timestamp in the schema does not match the visible publish date, you are sending Google a contradiction. Keep the structured data in lockstep with what a human actually sees.

How to detect and validate

To find pages missing the markup, crawl the site with Screaming Frog and check its Structured Data tab, which reports which URLs carry which schema types. Sitebulb does the same in its structured data hint set. For spot checks, Google's Rich Results Test and the schema.org validator both parse a single URL and list errors and warnings. Search Console has an Enhancements report and a URL Inspection tool that show how Google itself read your structured data in the field, which is the version that actually counts.

Work through warnings, not just errors. An error blocks eligibility outright; a warning means a recommended field is missing, and filling those is usually where the real display upside lives.

What good looks like

Every news URL carries valid NewsArticle JSON-LD. The Rich Results Test returns zero errors. Author, publisher, and both dates are present, accurate, and identical to the visible page. Search Console shows the pages as valid with no outstanding issues, and your eligible stories start surfacing in Top Stories and the News tab.

FAQ