NewsArticle

Minimal valid version

The smallest markup that still produces a valid NewsArticle entity. Use it as the floor. Reach for the advanced example above when you want search engines and AI agents to understand more about your content.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "NewsArticle",
  "headline": "Xoo Code Opens Flagship Retail Store in Downtown Dunmore",
  "image": "https://dunmoreherald.com/images/2026/xoo-code-store-16x9.jpg",
  "datePublished": "2026-03-15T08:00:00-05:00",
  "author": {
    "@type": "Person",
    "name": "Maria Torres"
  }
}
</script>

Google rich results this unlocks

Markup matching this example makes your page eligible for the following Google Search rich results. The primary target drives the required / recommended property classification in the advanced code block above.

• Article rich resultprimary

  Google docs

Common NewsArticle mistakes

Mistakes that pass validation but silently fail to earn rich results or mislead consumers walking the graph. Avoid these and your markup will be ahead of most sites in the wild.

1. 01

   Using Organization instead of NewsMediaOrganization

   Wrong

   "publisher": { "@type": "Organization", "name": "Dunmore Herald" }

   Right

   "publisher": { "@type": "NewsMediaOrganization", "name": "Dunmore Herald", "ethicsPolicy": "https://dunmoreherald.com/ethics" }

   Organization validates fine, but NewsMediaOrganization carries trust-signal properties (ethicsPolicy, masthead, verificationFactCheckingPolicy) that Google News reads when evaluating publisher eligibility. If you are a news publisher, always use the more specific type.

2. 02

   dateline as a date instead of a location

   Wrong

   "dateline": "2026-03-15"

   Right

   "dateline": "DUNMORE, Pa."

   Despite the name, dateline is a location string, not a date. It is the city-and-region slug that traditionally opens a wire story. The date is already captured by datePublished. Putting a date in dateline confuses aggregators and provides no useful signal.

3. 03

   Headline longer than 110 characters

   Wrong

   "headline": "Xoo Code Inc. Opens Its First-Ever Flagship Retail Store Selling XooTee Graphic Tees and Hosting Schema Markup Workshops in Downtown Dunmore, Pennsylvania"

   Right

   "headline": "Xoo Code Opens Flagship Retail Store in Downtown Dunmore"

   Google truncates article headlines at 110 characters and may suppress the rich result if the headline exceeds that limit. Keep headlines under 110 characters and use alternativeHeadline or description for the longer version.

4. 04

   Paywall content without isAccessibleForFree markup

   Wrong

   (paywalled article with no isAccessibleForFree property)

   Right

   "isAccessibleForFree": false,
   "hasPart": {
     "@type": "WebPageElement",
     "isAccessibleForFree": false,
     "cssSelector": ".article-body"
   }

   Google requires paywalled news articles to declare their access model. Without this markup, Google may remove the article from Google News or apply the wrong caching rules. Free articles should set isAccessibleForFree to true explicitly.

5. 05

   Missing speakable for Google News eligibility

   Wrong

   (NewsArticle without speakable property)

   Right

   "speakable": {
     "@type": "SpeakableSpecification",
     "cssSelector": [".article-headline", ".article-summary"]
   }

   speakable is not required for the article rich result, but Google uses it to select content for Assistant news briefings and voice search. If you want your news articles read aloud on smart speakers, add a SpeakableSpecification pointing to the headline and lead paragraph.

Schema properties in this example